Hi Team,
We have Veeam B&R 12.0. and we have two storage devices one is IBM storage which is iSCSI repository added in Veeam and one is Dell Storage iSCSI added repository in Veeam.
IBM storage is running out of space, so we brought Dell Storage, now we want to move last 6 months or 1 year backups from IBM to Dell.
Repository Policy : we have 10 days retention policy with 4 weeks full backup , monthly backups 12 , yearly backups 5 years. All are Vmware Virtual machine backups. so we want to move more than 6 months backups to Dell repository and those backups need to be managed by Veeam. we don't have any cloud backups all are on-prem backup. please advice me on this thank you in advance.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jul 31, 2023 1:40 pm
- Full Name: Srini
- Contact:
-
- Veeam Software
- Posts: 2590
- Liked: 606 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Veeam B&R 12.0 - Move more than 6 or 1 year backups to new repository
Hi Srini,
Backup Move will be what you want to use in most of your cases. This will move the entire backup chain however, so likely you will need to choose based on the job workload rather than a time based period as per your request. Right now there is not a means to "tier" out backups in this manner from one local repository to another.
I advise review the User Guide link above as there are some requirements for the Backup Move feature, but this should help with your migration to the new storage device.
Similarly, if you don't need the granularity of picking which backups are moved, you can automate the process by creating a Scale-out Backup Repository and using the Rebalance Extents feature. This will distribute the backups across all extents in the Scale-out Backup Repository automatically, but keep in mind that this is an automated process. You can later on use Backup Move if you want to move backups back to the original location.
Backup Move will be what you want to use in most of your cases. This will move the entire backup chain however, so likely you will need to choose based on the job workload rather than a time based period as per your request. Right now there is not a means to "tier" out backups in this manner from one local repository to another.
I advise review the User Guide link above as there are some requirements for the Backup Move feature, but this should help with your migration to the new storage device.
Similarly, if you don't need the granularity of picking which backups are moved, you can automate the process by creating a Scale-out Backup Repository and using the Rebalance Extents feature. This will distribute the backups across all extents in the Scale-out Backup Repository automatically, but keep in mind that this is an automated process. You can later on use Backup Move if you want to move backups back to the original location.
David Domask | Product Management: Principal Analyst
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jul 31, 2023 1:40 pm
- Full Name: Srini
- Contact:
Re: Veeam B&R 12.0 - Move more than 6 or 1 year backups to new repository
Hi David,
Thank you for the response, I checked the Scale-out backup and Re-balance extents options and they are helpful. from below link we can map the backup which are moved manually, if we map backups will the backup retention will be there on those backups and can be managed by Veeam. thank you in advance.
link : https://helpcenter.veeam.com/docs/backu ... ml?ver=120
Thank you for the response, I checked the Scale-out backup and Re-balance extents options and they are helpful. from below link we can map the backup which are moved manually, if we map backups will the backup retention will be there on those backups and can be managed by Veeam. thank you in advance.
link : https://helpcenter.veeam.com/docs/backu ... ml?ver=120
-
- Veeam Software
- Posts: 2590
- Liked: 606 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Veeam B&R 12.0 - Move more than 6 or 1 year backups to new repository
Hi Srini,
Manually moving backups and mapping is indeed possible, just be sure that the .VBM file is moved as well. I would make a _copy_ at first, and once the mapping is successful, clear the old backups out, but that should work.
Backup Move and the Scale-out Backup Repository (SOBR) rebalancing will handle the mapping automatically.
Good luck with the new storage and migration!
Manually moving backups and mapping is indeed possible, just be sure that the .VBM file is moved as well. I would make a _copy_ at first, and once the mapping is successful, clear the old backups out, but that should work.
Backup Move and the Scale-out Backup Repository (SOBR) rebalancing will handle the mapping automatically.
Good luck with the new storage and migration!

David Domask | Product Management: Principal Analyst
Who is online
Users browsing this forum: DaStivi, epaape, HenkeZan and 168 guests