Hi,
Newbie to the forum and VBR here ... we have a NAS that is currently serving as our on-prem repository and we have a backup copy job that copies the backups to a cloud provider. We were just thinking, it is better to use the NAS as the performance tier in a scale-out repo and using the cloud provider as the capacity tier so that the same thing can be accomplished without creating 2 jobs (backup to NAS and then copy whats in the NAS to cloud).
But what's not clear to us is: what would happen to the existing backups in both the NAS and the cloud repo if we were to use them as part of the SOBR? Will they get deleted?
-
- Novice
- Posts: 3
- Liked: never
- Joined: Mar 29, 2020 6:24 am
- Full Name: M.Y.
- Contact:
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: Using existing repository as scale-out repository
Hey M.Y.,
When you add an existing repo to a Scale Out Repository, it informs you that all jobs pointing to that repository will be re-pointed to the new Scale out. (automagically no new full necessary, it just works as you would want it to)
From experience, there are a few checks also to make sure you don't put unsupported backups into the Scale Out, so you should be fine Just try it and it is quite seamless from dozens of times doing this with my clients.
When you add an existing repo to a Scale Out Repository, it informs you that all jobs pointing to that repository will be re-pointed to the new Scale out. (automagically no new full necessary, it just works as you would want it to)
From experience, there are a few checks also to make sure you don't put unsupported backups into the Scale Out, so you should be fine Just try it and it is quite seamless from dozens of times doing this with my clients.
Who is online
Users browsing this forum: acmeconsulting, Bing [Bot], gojain, Google [Bot], josema.anton, Semrush [Bot] and 128 guests