VeeamON 2024 | #BounceForwardThrowback (Win Custom Shoes!)
Top technical сommunity program
Run by users, for users
Start FREE on-demand training
Any can help to solve this error please?“2024/3/27 11:04:52 :: Unable to truncate SQL server transaction logs. Details: Failed to truncate SQL server transaction logs for instances: MSSQLSERVER. “It is from a backup job of a physical server.
Running VBR v12.0. Created a backup job. Ran the job and got an error so went back in and try to edit the job. I got the error below. First time, I encountered this error. The backup log just showed the same information. I have a similar job running in our “staging” VBR but not having any error. The backup job is a storage snapshot and does handle SQL transaction logging. I saw in the Veeam’s Forum the same error message but this was for a backup copy job. What do you think is happening here?
We have Kasten K10 on installed via operator on multiple clusters. All of the K10 instances seem to have excessive amounts of helm revision when viewed with helm history k10 Is this normal behavior? We seem to be getting ~200 revisions per hour.
hi veeam communityI researched air gap backup and came across a company called stonefly that I found interesting.I wanted to know if anyone has experience using this solutionhttps://stonefly.com/backup/dr365-for-veeam/Automated Air-Gapping: Enable/Disable physical or logical air-gapping directly from the Veeam data platform through seamless integration with StoneFly. In your opinion, what is the best solution for having an air gap?What solution do you use?
Hello again! Onto my second post for world backup day, this time looking at the moments leading up to a disaster. In this post we’re going to look at ways to proactively prevent failures. After all, the best backups are the (tested) ones that didn’t need to be used because everything is fine.Let’s kick this off with a trip down memory lane. During the days that all storage media was a traditional hard drive with spinning disks, it was typically pretty obvious when a hard drive was failing, we could hear issues such as failed bearings or the scratching of a needle as these were mechanical faults that were developing. However, when we look at flash storage, which doesn’t contain any mechanical parts, the lack of being able to hear problems developing can result in people taken by surprise when storage fails.Nearly 30 years ago, Compaq released S.M.A.R.T into the public domain, providing a standard of storage health for all vendors. S.M.A.R.T (Self-Monitoring, Analysis, and Reporting Tech
Hey Community -Sorry to be the bearer of unpleasant security news as of late, but better to be proactive rather than reactive, as they say, right? 🤷🏻♂️It appears the Agenda Ransomware group, which was first detected in 2022, has been ramping up infiltrations recently. It’s ransomware, Agenda (aka Qilin and Water Galura), infected the likes of healthcare, manufacturing, and educational entities 2years ago, but have since rewrote their ransomware to now target OS’s, and specifically geared towards the VMware hypervisor.This new variant was detected by TrendMicro , which they say “comes with a variety of new functionalities and stealth mechanisms, & sets its sights squarely on VMware vCenter and ESXi servers.”You can read more about this ransomware variant in the article below, as well as the TM link above:https://www.darkreading.com/cloud-security/agenda-ransomware-vmware-esxi-serversI’m not aware of any messaging by VMware as of yet about a potential patch/fix for this threat. If
It appears there has been a noticed exploit vulnerability in Linux Kernels v5.14 up to v6.6. The exploit seems to be a “privilege escalation from unprivileged user to root user. And, it should be noted that the exploit can read/write any physical memory on the device, but uses it to become root user. An important note is that the exploit requires nf_tables to be present, and unprivileged user namespaces. This can be checked with commands specified in the README.md file in the repo.”You can read more about this and the context/background of the exploit at the following link:https://pwning.tech/nftables/It is highly recommended to update your kernel as it seems this was patched in February. To check which kernel you have, simply type hostnamectl and check the Kernel heading:
Hi Community,i would like to give a suggestion for maybe a future release.When moving a backup to another repository, the job occupies all free task asap. Other jobs on that server will be delayed until the Move-Jop is finished.I suggest a dialog where one can limit the tasks the Move-Job is using, so the normal backup routine is not on full hold.What are your thoughts on this?
This KB came out years ago and was updated in January. Just a reminder to check all of your Veeam infrastructure, SQL hosts, and guest OS’s that have application aware and indexing enabled. I found a few servers that have been created in the last few years missing a few. I don’t know if I’ll see much a performance increase, but it can’t hurt 😀 Antivirus Exclusions for Veeam Backup & Replication KB ID: 1999 Product: Veeam Backup & Replication | 11 | 12 | 12.1 Veeam Cloud Connect | 11 | 12 Published: 2015-02-03 Last Modified: 2024-01-02 Purpose This article documents antivirus exclusions that may be created to reduce the impact that antivirus software has on the functionality of Veeam Backup & Replication. These antivirus exclusions may be applied to the Windows built-in antivirus or third-party antivirus software. Note: Antiviru
Backup Job Chains… If I keep seven (7) restore points and run an Active Full on Saturday (point #7) what happens to the six (6) files in the prior backup chain? Are they useless but don’t get deleted because we’re keeping seven (7) restore points? Backup Copy Jobs are different if not mistaken. If you keep seven (7) restore points and the seventh is a periodic full, the six prior restore points are deleted all at once?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.