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.
Good morning, everyone! Quick question. I have a copyjob that is throwing random “No Cloud Gateways available” errors. The odd thing is, it’s the only server that is having the issue and the our cloud connect server is fine. I am not quite sure what is happening between the cloud connect server and that backup server, but I want to get to the bottom of it! What would be the best Veeam log to check for info on that? I can run through the Windows Event Viewer, but I also want to see if any of the Veeam logs can shed some light. You all rock! Thank you so much for being great!
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 some copyjobs that have been running for a significant amount of time due to a catchup-scenario we are in. I have noticed that on some of the jobs, it seems as if they start over. I check the jobs at some point the next day, and instead of the “Last Run” column showing days, I will see 8 hours ago, 3 hours ago, etc. The job will still be in running status. But it also looks like the job may not have started over. These jobs are immediate copy.
Hi, everyone! I have a quick question about coypjob intervals. If I have my copyjob set to 1 day starting at 4am, does that mean that the copy starts at 4am and runs until 4am the next day and then just starts over? I am seeing some warnings about things not being copied over in the copy interval. I’m a little confused on how this works. How can I make the copy interval longer?
Hi, everyoneI have configured Veeam Agent for Windows to backup to One Drive, for a user, and I am getting constant and consistent failures and I am not having much luck finding a solution. The errors mainly are: Veeam Agent 'job’ name finished with Error and will be retried. Job details: Error: Shared memory connection was closed. Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: not an object Failed to download disk. Veeam Agent 'job name’ finished with Error and will be retried. Job details: Error: Shared memory connection was closed. Failed to backup file. File: [C:\WINDOWS\TEMP\digest_cd78e577-1055-4586-b7f1-5c21002d942d]. ItemSpec: [veeamfs:5:6745a759-2205-4cd2-b172-8ec8f7e60ef8 (ca7b02aa-1221-4b84-0868-8d2efa4aa31a)\digest_cd78e577-1055-4586-b7f1-5c21002d942d@cloud://<Path ConnId="f8d8bb00-8579-4324-910f-a29090f1a900" BackupId="197964ed-5767-4f66-9153-c709f0c1fdbb" StgId="838a66be-f1c4-4ce6-9f5f-b19467efea29" LocalPath="C:\
What does “Warning: some restore points failed to process” mean? I got this warning on a cloud copyjob and I can’t really find out what specifically it means or why it happened? Does this mean the copyjob failed or in a disaster recovery scenario that I’d have missing data that I couldn’t restore to from the cloud because it didn’t copy over? I ran a new sync and it was successful, but I am wondering what this warning means and how can I present it in the future?
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?
I work pretty heavily with backups in my current role, and we use your product and another product with some of our clients. The other product has a feature that is incredibly helpful and I think would be an amazing feature to add to Veeam. How feasible would it be to add a “Force Retention” feature? I really believe we need this for situations when we run into low disk space. In Veeam’s current state, if I run into an issue where I need to reclaim disk space, I am forced to break my backup chain and delete data. If I could lower retention on my backup and then force retention, that would effectively eliminate the need for me to have to lose data and break a backup chain. For example: if I am in a situation where I am getting failures due to low disk space, and I have retention on said backup job set to 30 days, if I could cut retention down to, say, 20 days, and force retention, I could maintain my current backup chain and then address the disk space issue accordingly (adding more dis
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.
