VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
I wanted to create this in the hopes that in the future, someone who is experiencing this error will find this thread and see a solution. I randomly had a backup start throwing the below error:Failed to pre-process the job Error: One or more errors occurred. Unable to apply retention policy: failed to delete backup files Error: Full storage not foundThrough some Google searching, all I could really find was to run an Active Full and start a new backup chain. I tried this, but the error still persisted. At this point, I did the only other thing I knew to do, so I told Veeam to delete the restore points for that job from disk, and I then ran a new active full. I essentially started over with a fresh dataset. I was able to get a successful backup after this.In conclusion: if you ever run into this issue, try running a new active full. If this does not resolve your issue, go to your restore points (the Disk section in VBR), and tell Veeam to delete from disk all of those restore points fo
I seem to have a lot more issues with Hyper-V that I do VMware. I was curious what you all’s overall experience is? In particular, Veeam does not seem to like clusters and I see lots of issues with checkpoint creations that pop up.
What is Veeam’s plan to address the newly discovered Cuba Ransomware exploit? Is there a patch forthcoming soon? https://www.bleepingcomputer.com/news/security/cuba-ransomware-uses-veeam-exploit-against-critical-us-organizations/
If a backup copyjob shows one vm in the job in a warning status that says “Waiting for backup resources availability”; did that particular VM actually copy over or did it ultimately fail to copy over?
Has anyone ever seen a backup job fail with the error “Full storage not found”? I have no orphaned restore points, repository is good...everything looks perfectly fine. The repository is accessible and I can see the vbms and vbk files in it. I can’t find an answer for this. Full error is below: 1/23/2023 2:50:08 PM :: Failed to pre-process the job Error: One or more errors occurred. 1/23/2023 2:50:10 PM :: Unable to apply retention policy: failed to delete backup files Error: Full storage not found
If someone has been doing image based backups of 100+ workstations in Acronis, but is interested in moving to a VBR environment, how do we accommodate that scale of workstation backups? The only thing I know to do is throw the Windows agent on them and create an agent backup within VBR, but I am curious if there is a better solution.
If we have established backups for a server, and we add an additional disk to said server, will and should Veeam automatically recognize and start backing up the newly added disk?
I’ve randomly had two backups corrupt at one of my clients. Not sure why it happened, but they did. On one of them, I deleted from disk all of the restore points on the local datastore, and took a new full. I left the cloud data alone, and as we speak, the new restore points are peacefully transferring offsite, no issue. The second backup has been a different story… Because of the nature of the server, I decided to take a new full and leave the old data in place, just in case. The new full local backup was fine, but the offsite failed. I tried running an active full of the offsite, but same deal; the offsite failed. So now I am trying a new strategy. I took a look at the restore points and 99% were corrupted (I believe this was the offsites), so I decided to just wipe everything and start from scratch, because I think the corrupted restore points are causing issues with the new data going offsite. The offsite failures have been throwing an error I’ve never seen before. I’ll paste it be
Is there a way to test the encryption key on backups without having to run a restore? I ran into a situation recently where the encryption password did not work on restored data. I want to setup Enterprise Manager for everyone, but in the interim, I’d like to manually test each encryption key and reset it/run a new full backup if need be. Is there a way to recover an encryption key with Service Provider Console?
Hi, everyone! I have a weird error popping up in a replication job for one of my client’s and I need some insight. We have a replication job with a number of VMs that are replicating to a local repository. For some reason, the job has started failing and saying the job can’t continue because the replica has been found in an inaccessible state. I’ll paste an example below. I have tried rescanning the repositories and rescanning the managed servers, but no luck. Retry of Replication job finished with Failed. Job details: Failed to create processing task for VM Error: Found replica VM *** with connection state inaccessible. Cannot proceed furtherFailed to create processing task for VM *** Error: Found replica VM *** with connection state inaccessible. Cannot proceed furtherProcessing *** Error: The request could not be performed because of an I/O device error. Failed to write data to the file [\\.\***Drive]. Failed to download disk 'Device '\\.\***Drive''. Shared memory connection was clo
I just want to say how grateful I am for the Veeam culture and the way they operate as a company and their extensive involvement in the Veeam community. I have extensively also used a competing product and I feel largely ignored by them and I have deep seeded impression that the company’s engineers couldn’t care less about the customers’ ideas and concerns and believe they know better than the customer and just choose to ignore 99% of what is suggested to them, meanwhile they seem to have the development acumen and abilities of first year college students. Meanwhile, a company like Veeam, that is a giant and a powerhouse, goes out of its way to not only make an amazing product, but also is incredibly involved with their client community, includes them in the decision making process through the Veeam Legends and Vanguard programs, and goes out of their way to make sure their customers know they are heard and cared about. I have so much respect for @Gostev @Rick Vanover and the entire V
This may be a head in the clouds idea/thought, but I really wish there were way (and there may be and I just don’t know about it) to link Veeam to Active Directory and stored domain credentials automatically get updated whenever a needed password gets changed or updated due to rotation policies. No more ‘RPC server unavailable’ errors!
Have a new Veeam server for a client. Got everything setup and ready to go, but ended up needing to change the hostname for the server itself. No worries. I’ve done that many a time. Business as usual...except afterward, the Veeam Backup Service refused to start not matter what I did. Rebooted the server, tried manually starting it, ran Windows update, change to Auto Start without delay. Nothing worked. My gut was telling me the hostname change was the cause of this, but I just wasn’t sure.Then I found this magical article by our very own, MicoolPaul, and it was exactly what I needed. The hostname change was indeed the issue. Veeam was trying to connect to a SQL database using a hostname that no longer existed...because we changed it! I manually changed the hostname prefix for the SQL DB using the Veeam Configuration Data Connection Settings tool, and this seems to have done the trick! Thank you so much @MicoolPaul! You are wonderful!
Hi, team I need some advice. We have a client that we need to do a quarterly full backup for. We would like to run an active full to a USB attached drive that will be rotated out each quarter. Each USB drive will be designated for a specific quarter (i.e. USB Quarter 1, Quarter 2, etc). This job will only run once per quarter and we would like each run to be a full backup. What is the best way to accomplish this in VBR 11a?
Hi, everyone! We have a single VM that is over 65TB in size, that we are backing up. We have run into a snag. VMware maxes out at 65TB, so we are running out of space on this backup and we don’t know what route to go in terms of setup. Is SOBR the preferred backup infrastructure for a VM of this size?
Hi team, I have a new backup I am running that is failing at the first full. It fails and says that it cannot find a VMDK file that is located in an excluded disk. The error reads: “Processing servername Error: File 'X.vmdk' was not found. This disk is a USB attached storage device, but it was added to vmware as an iscsi drive so that we can exclude it in VBR. I have double checked the disk exclusions and confirmed that I have told the job to only back up the correct disks (the disks that aren’t this USB attached storage). I have also checked the checkbox to remove excluded disks from configuration. The file is present in vcenter. I checked. I can’t figure out what is going on and why this job is failing due to a file that should not even matter because I have excluded from the job, the disk the file is located on.
Had a server get updated to a new version of Windows Server. Is a new full backup necessary? Will Veeam run one automatically if it is?
If you setup a VBR agent based backup on a machine that has 3 volumes listed in the OS (one volume being the VBR backup repository), and you set the backup type to entire computer; VBR by default will backup all 3 volumes listed in the OS, including the backup repository volume, correct? For context, in this scenario, the Veeam repository volume points to a NAS setup via iscsi initiator.
I have an odd backup setup that I am trying to navigate. We have a VM (VMware) that is being backed up that has a volume listed in the OS as G: drive. This is actually a USB drive attached to the host server and is being fed into VMware via the xHCI USB driver. Veeam is backing up this volume, but is not listing it in the list of backed up drives if I try and create an exclusion. Is there another area to look or another way to exclude just this G: drive from the backup?
If I were to create a new copyjob to replace an old one, and I want it to only move over the very latest restore point and none of the previous restore points that are currently in the repository; can this be accomplished by taking a new active full on the source jobs and then running a sync now on the new copyjob and telling it copy over the latest? If not, can this only be accomplished by wiping out all current local and cloud and starting from scratch?
For those of you who have upgraded to 11a, how are you liking it so far? I upgraded all of my servers last week and so far I can 100% see a big difference in performance. I am happy with it so far. I also updated our Service Provider Console to v6.
Hi, all I made a simple script that will allow you to run the backup validator and receive a report. echocd C:\Program Files\Veeam\Backup and Replication\BackupVeeam.Backup.Validator.exe /backup:"BackupName" /report:"C:\VeeamReports"rem May have to specify name(s) of VMs being backed up in jobrem If there are multiple backup jobs, you must create a new line for each job --> Veeam.Backup.Validator.exe /backup:"BackupName" /report:"C:\VeeamReports"
Hi, all I am wanting to get some insight and pick you all’s brains on your best practices when it comes to copyjobs. Here’s the situation I am in:I have backups servers that have fairly complex backups schedules that range from hourly backups to daily, and even weekly backups. Lately I have been running into copyjob failures that say “the restore point is locked by another job”. This is happening when primary backup file healthchecks, merges, or defrags run. I created a topic about this, last week, and @Chris.Childerhose gave me some good insight. I guess I am at take 2, at this point, and I need you all’s input. The problem is, I have no idea how to schedule the copyjobs around these schedules...there just really isn’t a way, and consequently, i don’t know of a way to avoid these failures. They used to not happen. It’s only been recently that they have started cropping up. I am also working with support on this, but I would love you all’s input and get some insight into how you all ta
Hi, team I have a weird one for you. Have you ever seen a copyjob fail due to a normal backup running at the same time? I have been running into an issue where a copyjob is running and then a scheduled backup starts while the copyjob is running. When this happens, the copyjob will fail and throw the error: ”Source restore point is locked by another job ” My understanding is that this should not happen. I did notice that the last time it happened, there was an incremental to full backup file merge happening. I am not sure if that may be the cause in this case, but I do not believe that is always what’s happening when I see this error. The copyjob is set to Immediate with a 24x7 schedule. This server is running VBR v.11
I have a server I am running VBR 11 on. The option to rescan repositories has just outright disappeared. I have tried closing and re-opening VBR, but this did not resolve the issue. A server reboot has also not resolved the issue.
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.
