Fire Safe Backups...

[CHiLL]

Why would you even mention the word robocopy? Veeam backup copy job does it all plus you get total control of what kind of data retention (grandfather, father, son, etc) you have on the job in order to maximise you're use of space on the backup copy target.

I am looking to use it to backup to two separate NAS targets. I can't get the jobs to perform after another job, its time-based only...and I think I'd run out of time.

[TechMonkey]

Hmm, OK. I've just had a look and the scheduling looks more promising! Would that be a solution for disaster recovery?

 

How many copies of the VM do you keep? Say Server1 performed a VM copy job to NAS1 yesterday. How do you manage the Server1 VM that copied to NAS1 yesterday? Do you keep that copy and it creates a new one? Does it overwrite the old Server1 VM file? Do you manually delete it? Do you delete it via script?

My view is it does. We only keep a very small number of copies on the remote system. If you have a catastrophic failure where your main backup is fried then you will only really need the latest. But we keep a few mothly backups as well just incase. I'll have to have a look as it was setup last year and I haven't really had to touch it.

 

I am looking to use it to backup to two separate NAS targets. I can't get the jobs to perform after another job, its time-based only...and I think I'd run out of time.

Set the job to be continuous and it will do it as and when it can. Our last job took 1 hour 7 minutes and 14 seconds.

[CHiLL]

My view is it does. We only keep a very small number of copies on the remote system. If you have a catastrophic failure where your main backup is fried then you will only really need the latest. But we keep a few mothly backups as well just incase. I'll have to have a look as it was setup last year and I haven't really had to touch it.

 

 

Set the job to be continuous and it will do it as and when it can. Our last job took 1 hour 7 minutes and 14 seconds.

It appears our NAS is bottlenecking the job that I started this morning at 8.30am. It is now 4pm, and it has only done 42%! It's writing at around ~50MB/s. Because this is the first time this job has been run, its doing a full backup to the NAS and the rest will be forever-forward incrementals (so I have read).

[TechMonkey]

I may have read the wrong thing that day. Just looked now and it is just finishing off after 9 hours 39. But that is all background so no ill effects on the network.