Backup Copy Job retention is independent from the source job's retention, so the presence of fulls won't affect the length of the backup copy chain.We are trying to only keep one week on the cloud repository for space issues so that's why we don't have full or synthetic backups on the main Backup Job.
I'd suggest you to use Backup Copy with GFS settings for that.We also want to have a separate full backup job run on Saturday every weekly with 5 restore points retained.
No, it won't, jobs overlapping is handled automatically by Veeam B&R.That is will it disrupt the incremental jobs that run the rest of the week if they see that a full backup was run on Saturday?
No, it won't cause conflicts, however it is recommended to use Backup Copy Job in such scenarios. Please tell me ehy would you want to run another full Backup Job against production VM on Saturdays thus causing an extra load on the storage if you already have Saturday incremental backups that have been produced by your daily jobs and can be used to create separate full backups?If I setup another backup job using type 'Backup Job' to do my weekly backups will that cause any conflicts at all?
I'm not sure that I understand what flag are you referring to, please elaborate.I was told that VMs get flagged as already backed up and I don't want one job to change the flag for another job.
The source for a backup job is a VM. The source for a backup copy is a backup file.
By configuring a backup copy you are not grabbing data from your production vms each time it runs thus eliminating any potential performance impact you could see.
To short answer to your second question is no, you don't have to worry. You will see two separate jobs for which you can restore data from (even though they contain the same machines), one will have your daily restore points while the other has your weekly restore points.
Users browsing this forum: billcouper, Google Feedfetcher and 1 guest