- Service Provider
- Posts: 15
- Liked: never
- Joined: Nov 20, 2015 6:21 am
- Full Name: Stephen Cilesio
It also takes time restoring from backups on the AltaVault when considering these days, SLA for Data/Server restores are much more prominent now.
The idea i have is to put a caching tier in front of the AltaVault so for example, On the caching tier running faster disks (SAS), would have 7 - 14 Dailies with an active-full. Then from there have a Backup copy job and tick the option for the GFS restore points to be copied from the caching tier repository.
We have followed all best practice guides with setting up Veeam with NetApp AltaVault integration and was wondering if anyone else has specific design considerations or more efficient way of implementing this for larger deployments/Servers? Also getting those restore times down?
- Posts: 113
- Liked: 15 times
- Joined: Jun 06, 2014 2:45 pm
- Full Name: csinetops
When we were looking at the AltaVault a year ago, the NetApp engineer recommended setting it up this way as you don't want to try and dump directly to a dedupe/compression device. Same with restores, if you have to do all your restores from it, it's going to be slower than having some plane-jane disk and a few normal restore points. The AltaVault really isn't meant to be the main landing site for backups. It's a long term/2nd tier/archival ( or whatever you want to call it) storage device. I think of it as a replacement for tape drives.
That being said. My biggest VM's are ~6TB, they take under 5 minutes to mount a FLR from local data on the AltaVault. Cloud data you have to factor in the time it takes to pre-populate the data on the AltaVault before kicking off the restore. What kind of restore times/speeds are you seeing?
- Veeam Software
- Posts: 255
- Liked: 48 times
- Joined: Mar 23, 2015 11:55 am
- Full Name: Michael Cade
- Location: Cambridge, United Kingdom
Users browsing this forum: Exabot [Bot], Google [Bot] and 20 guests