Veeam job question, year's worth of data.

[Lanz]

Moving from commvault to veeam.

Have 2 physical backup boxes acting as proxies and repositories, one at each site. Doing network based backups at the moment.

If we wanted to keep a years worth data that is stored both locally for quick restores and remotely for DR whats the best way of doing this.

Right now with testing, we are running 2 jobs for each group of VM's, a local reverse incremental job every night, with 365 restore points, with a full backup once a month. And straight after that job is finished, we run a forward incremental job with a synthetic full on a sat with 365 points that gets sent to the remote repository.

Seems like a crazy way of doing things to me, running two jobs doing the same thing, but it seems there's no decent way of copying to a remote site.

Do we make single jobs with 365 restore points, or do we create multiple, smaller restore point jobs for weekly, monthly etc?

thanks

 

[Lanz]

We are using 2 win2008R2 servers, Dell R720XD with 34TB for the repository (RAID6)on each.

Some people seem to do forward incrementals and then just rsync/robocopy the files over to the other site rather than running 2 jobs, but with that you cant really use reverse incrementals as all files get touched.

We really need to store a year at both sites, just incase one repository gets wiped.

So if we used Win2012, would a year's worth of those weekly/monthly full's get deduped by the OS? I've not looked at 2012, we dont have any currently on our domain.

Obviously only some of our VM's need to be kept a year (user data), the majority of the app servers etc just need 3 months. We have about 200+ VM's with a 70/30 split at each site.

 

[Lanz]

Thanks for teh info, with forward incrementals, can we just use standard robocopy transfers, or does it need a block level, rsync type copy?

Also, what's the impact of restore times when using forward rather than reverse, and can you use vpower instant recovery still?