I'm transferring workloads from a VBR 12 server which will be scrapped to a new VBR 13 server. Mostly by creating new jobs. But there are a couple of long-term copy jobs with monthly and yearly backups that I need to migrate as is and continue on the new server. Do I understand correctly that this procedure should work?
1. Document settings of the backup jobs and their S3 copy jobs.
2. Delete the jobs and the repository.
3. Create the repository on the new server and import backups.
4. Create new jobs with same settings and map the S3 backups to the copy jobs.
If something goes wrong, will I be able to go back to the old server and recreate the original setup, or will the v13 import make changes that makes this impossible?
-
DanielJ
- Service Provider
- Posts: 308
- Liked: 61 times
- Joined: Jun 10, 2019 12:19 pm
- Full Name: Daniel Johansson
- Contact:
-
Mildur
- Product Manager
- Posts: 12128
- Liked: 3474 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Inherit S3 repository between VBR 12 and 13
Hi Daniel,
You won’t be able to connect the object storage repository with a previous version of Veeam Backup & Replication afterwards, so there is no fallback option.
You will need to stay on the same build or higher.
Can you please confirm if you use direct backup or as a capacity tier?
For direct backup, the process itself looks good to me. Make sure that your new backup copy jobs have the exact same GFS settings as the original jobs. If you have some smaller repositories, I recommend to test this procedure first. Or create a new bucket/repository and test the process with a small test vm.
Best,
Fabian
You won’t be able to connect the object storage repository with a previous version of Veeam Backup & Replication afterwards, so there is no fallback option.
You will need to stay on the same build or higher.
Can you please confirm if you use direct backup or as a capacity tier?
For direct backup, the process itself looks good to me. Make sure that your new backup copy jobs have the exact same GFS settings as the original jobs. If you have some smaller repositories, I recommend to test this procedure first. Or create a new bucket/repository and test the process with a small test vm.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: No registered users and 216 guests