I am debating the choice of having 1 repository, a Scale Out Backup Repository; or 2 repositories, a local disk repo and a SOBR repo.
With the 2 repositories, I would create a backup copy job to move GFS backups into the SOBR and then up into Azure Archive Storage. That way, I don't accidentally move backups into Azure Blob storage and can have more independent control of both repositories.
Although, is a SOBR repository designed to be the primary, single Repo for a backup workflow that moves GFS backups into archive storage? Any suggestions on best practice?
-
- Influencer
- Posts: 10
- Liked: never
- Joined: Jan 24, 2024 7:21 pm
- Full Name: Joel Dodd
- Contact:
-
- Influencer
- Posts: 10
- Liked: never
- Joined: Jan 24, 2024 7:21 pm
- Full Name: Joel Dodd
- Contact:
Re: SOBR Repo Planning Question
I guess to clarify, I would actually create 3 repos:
2 local repos, one to use for the SOBR performance tier; and then the SOBR repo.
Do I need the 2 local repos, or would 1 local repo that is apart of the SOBR be what's designed to work? I'm only afraid that my incremental and full backups will be moved to Azure Object storage when I don't want them to.
2 local repos, one to use for the SOBR performance tier; and then the SOBR repo.
Do I need the 2 local repos, or would 1 local repo that is apart of the SOBR be what's designed to work? I'm only afraid that my incremental and full backups will be moved to Azure Object storage when I don't want them to.
Who is online
Users browsing this forum: No registered users and 18 guests