nick3young wrote:Basically, the problem I have is that I occasionally get an error for the job saying that 'some VMs were not processed during the copy interval'. But then very shortly after... it completes successfully. Is there a way to remove this?
nick3young wrote:As for the two backup copy jobs - do I simply setup an entirely new backup copy job (exactly how I did for the first one) and just point it to a different target? Will this not hit performance then?
foggy wrote:Do you mean it completes during the next copy interval?
foggy wrote:As an alternative, you can also use backups produced by your first backup copy job as a source for the second one. For this, you need to point the second one to a backup repository used by the first job to store its backups.
nick3young wrote:On the Saturday, the backup copy job reports as running successfully for a full 24hrs (with all VMs processed), but then I get a fail every Monday at the start of the new interval (job starting at 22:30 on the Sunday)... but weirdly the 'fail' says the job has been running for only 22 minutes.
nick3young wrote:I like the sound of this. So I simply create a 'backup copy job' on the repository I use for my first backup copy? Would this be better than creating two backup copy jobs on my 1st backup server?
You don't have anything to copy during weekends, since the source backup job doesn't run
nick3young wrote:And since each copy interval finishes at 22:30 each night... this only gives roughly 10 hours to complete the 'copy job'. The full backup takes 16 hours... so the copy job should take at least that.
Users browsing this forum: adapterer, Bing [Bot], Google [Bot] and 1 guest