-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Apr 01, 2019 7:30 am
- Full Name: Dmitriy
- Contact:
In-place replace Veeam Repository
Hello,
I have a 2008R2 server acting as a Veeam Repository ( ~ 40TB of backup data), and it prevents me from upgrading to v12. Also, there is not enough space to create full backup for all jobs.
Also I have a 2022 brand-new server.
The idea is to shutdown 2008R2, reconnect all storages to 2022 and configure the last one with the same settings (ip, shares, permissions, etc).
After rescan and components installed, would Veeam recognize it as the same repository that was before?
May be there is a better way? Thanks.
I have a 2008R2 server acting as a Veeam Repository ( ~ 40TB of backup data), and it prevents me from upgrading to v12. Also, there is not enough space to create full backup for all jobs.
Also I have a 2022 brand-new server.
The idea is to shutdown 2008R2, reconnect all storages to 2022 and configure the last one with the same settings (ip, shares, permissions, etc).
After rescan and components installed, would Veeam recognize it as the same repository that was before?
May be there is a better way? Thanks.
-
- Product Manager
- Posts: 10062
- Liked: 2675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: In-place replace Veeam Repository
Hello Dmitriy
What sort of storage do you have in use? I read shares. Is it a SMB repository?
Best,
Fabian
What sort of storage do you have in use? I read shares. Is it a SMB repository?
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Apr 01, 2019 7:30 am
- Full Name: Dmitriy
- Contact:
Re: In-place replace Veeam Repository
No, repository type is 'Windows' (I mentioned shares, but they are used just for monitoring purposes)
-
- Product Manager
- Posts: 10062
- Liked: 2675 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: In-place replace Veeam Repository
Thank you.
Yes, reconnecting volumes from one server to another server normally works (physical and iSCSI/FC).
Please note, this is done outside of Veeam. We cannot give you any guarantee for the process of reconnecting your storage.
I recommend the following approach:
1. Create a configuration backup with the backup console on the old server
2. Install the same Veeam Backup & Replication build on the new server
3. Disable all services on the old backup server
4. Reconnect your storage from the old server to the new server
5. restore your configuration backup to the new server
6. Add the migrated storage as a new repository
7. rescan the repository
8. Map your backup jobs to the migrated repository
Your next backup session will be an incremental backup.
After the successful backup and restore is confirmed, run the upgrade to Veeam Backup & Replication v12.
Another approach would be to invest in a new backup hardware. I don't know how old your storage is, I assume they are little bit older when they still were used by a server 2008 R2.
It could be the right time to check out new solutions with make your backup fast and/or more secure.
With Server 2022, you could format the backup disks with reFS. This would allow you to use FastClone. A method to create fast and space less synthetic full backups.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Or check out hardened repositories, which will protect your backups against accidental or forced deletion by attackers. It makes your backups safer and also provides fast and space less synthetic full backups through FastClone with XFS as the file system.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Best,
Fabian
Yes, reconnecting volumes from one server to another server normally works (physical and iSCSI/FC).
Please note, this is done outside of Veeam. We cannot give you any guarantee for the process of reconnecting your storage.
I recommend the following approach:
1. Create a configuration backup with the backup console on the old server
2. Install the same Veeam Backup & Replication build on the new server
3. Disable all services on the old backup server
4. Reconnect your storage from the old server to the new server
5. restore your configuration backup to the new server
6. Add the migrated storage as a new repository
7. rescan the repository
8. Map your backup jobs to the migrated repository
Your next backup session will be an incremental backup.
After the successful backup and restore is confirmed, run the upgrade to Veeam Backup & Replication v12.
Another approach would be to invest in a new backup hardware. I don't know how old your storage is, I assume they are little bit older when they still were used by a server 2008 R2.
It could be the right time to check out new solutions with make your backup fast and/or more secure.
With Server 2022, you could format the backup disks with reFS. This would allow you to use FastClone. A method to create fast and space less synthetic full backups.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Or check out hardened repositories, which will protect your backups against accidental or forced deletion by attackers. It makes your backups safer and also provides fast and space less synthetic full backups through FastClone with XFS as the file system.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Influencer
- Posts: 14
- Liked: 1 time
- Joined: Apr 01, 2019 7:30 am
- Full Name: Dmitriy
- Contact:
Re: In-place replace Veeam Repository
This server is just a repository, VBR itself runs on another. Thanks, "map backup" looks promising.
Who is online
Users browsing this forum: Ahrefs [Bot], Bing [Bot], coolsport00, DChiavari and 103 guests