Best Practice

Availability for the Always-On Enterprise

Best Practice

Veeam Logoby sorell.it » Sun Nov 19, 2017 11:30 pm 1 person likes this post

Hi,

We are backing up to a offsite repo over the internet. We did have it configured to do GFS but this takes a lot of disk space and is apparently old school thinking. I have been reading up on using a seed and creating a job that's mapped to the seed and runs every 30 days and keeps the last 12 restore points or runs every day and keeps the last 30 to roughly fall in line with the GFS method. Mapped backups seems to be a 1 to 1 relationship as it says "this job is currently mapped to job x, are you sure you want to reassign it?" when i try to configure the 2nd job.

Is it possible to have multiple jobs running from a single seed without 2 copies of the seed?

Should I just keep the last 365 restore points or does this cause issues as well? It seems excessive and there would be little difference to the business if a restored backup is 235 vs 230 days old.

Are there better ways to manage 12 months worth of backups on limited disk space?

Thanks.
sorell.it
Novice
 
Posts: 4
Liked: 3 times
Joined: Mon Oct 24, 2016 10:22 pm
Full Name: Sorell IT

Re: Best Practice

Veeam Logoby PTide » Mon Nov 20, 2017 10:38 am

Hi,

We are backing up to a offsite repo over the internet. We did have it configured to do GFS but this takes a lot of disk space and is apparently old school thinking.

It's not quite clear if you use Backup Copy job with GFS retention to ship the backups to the offsite storage, or do you use just plain backup job and maintain GFS by other means?

Thanks
PTide
Veeam Software
 
Posts: 3311
Liked: 275 times
Joined: Tue May 19, 2015 1:46 pm

Re: Best Practice

Veeam Logoby sg_sc » Mon Nov 20, 2017 9:04 pm

It seems to me you need ReFS 64k with block cloning and BackupCopyJobs with GFS.
sg_sc
Enthusiast
 
Posts: 45
Liked: 8 times
Joined: Tue Mar 29, 2016 4:22 pm
Full Name: sg_sc

Re: Best Practice

Veeam Logoby taurus1978 » Wed Nov 22, 2017 3:32 pm

Hello,

some tips for offsite backup.

- Configure primary Jobs to backup to local storage.
- Create a seed of the primary Job. Transfer it to the remote location
- Then configure BC Job to use GFS Retention and send it to remote Repositories. Map it to the seed. "Map backup...."
- Use dedicated Proxies on each site, with local Storage for them.
- For primary Job and BC Job set Storage Optimization to LAN or WAN Target. Depends on you Line capacities. This sets the blocksize for the backupfiles.
- For very poor wan lines use WAN accelerator feature.

How many GFS points you define depends on your recovery policies. F.e.: If you want to recover the data for about 12 Months on a weekly basis you need to configure 52 weekly GFS Points. Or for one year on a monthly basis you need to keep 12 Monthly GFS Points.

Hope this helps you a little bit.

Regards,
taurus1978
Technology Partner
 
Posts: 4
Liked: never
Joined: Mon May 11, 2015 11:51 am
Full Name: Patrick Huber


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google [Bot], Google Feedfetcher and 1 guest