-
- Service Provider
- Posts: 37
- Liked: never
- Joined: Aug 20, 2015 1:37 pm
- Full Name: Kyle Slaughter
- Contact:
SOBR Placement Policies - Best Practice
We have a SOBR consisting of SAS and SATA backed CIFS shares. Wondering if there is a best practice for backup placement settings for a SOBR. Specifically, should we have all of our incrementals stored on the SAS extents and the fulls stored on the SATA? If we do that though, how would this affect the merging of the oldest restore point into the full .vbk (we are doing forward incrementals)? What is the affect of changing the backup placement settings now? Would all .vbk's/.vib's be migrated automatically, or would this setting only affect future jobs?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SOBR Placement Policies - Best Practice
Hi Kyle, looks like using performance policy is reasonable in your case. This will not affect the merge process. New policy will be applied to future backupsб existing backups will be left where they are.
-
- Service Provider
- Posts: 37
- Liked: never
- Joined: Aug 20, 2015 1:37 pm
- Full Name: Kyle Slaughter
- Contact:
Re: SOBR Placement Policies - Best Practice
Thanks Foggy. So we are currently using the Performance placement policy for our SOBR. However, we are allowing all backup (full or incremental) on both our SATA and SAS extents. Would you recommend putting just the fulls on SATA and the incrementals on SAS then?
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: SOBR Placement Policies - Best Practice
This doesn't play a big role unless you use deduplication on of the extents.
Who is online
Users browsing this forum: Semrush [Bot] and 68 guests