I have a SOBR repository with a large backup job on it and due to a change in backup strategy the SOBR is running out of space more quickly than anticipated (in a few months). But in the interim I want to move an archive job off of the SOBR and on to an RDM that I will add to a proxy (on our SAN in the BCP site which has space).
Is the process more complex than removing the backups from the configuration, copying the files across, and the importing them back in? Will there be any complications given the files were split across two extents with regards to the vbm and importing them back in (e.g will the vbm or the import throw up errors)?
Should I bear anything in mind with creation of a 40TB RDM? I know that an ISCSI attached to the guest OS is generally the preferred way of using SAN storage for Veeam backup but given that no new backups will be taken and as the retention policy starts being applied in a month or two they will be deleted (although this being done by script as the job is no longer active.
Obviously I will buy an extra shelf of storage and expand the SOBR but for various reasons it will be good to have a little more breathing room.
Thanks in advance for any pointers and advice.
-
- Enthusiast
- Posts: 66
- Liked: 5 times
- Joined: Jan 30, 2018 12:06 pm
- Full Name: Simon Osborne
- Contact:
-
- Veeam Software
- Posts: 21070
- Liked: 2115 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Manually Moving Backup Job From SOBR
Since each extent has the same copy of VBM, there will not be any issues with import/rescan. You can also go with adding the new repo as an extent to SOBR, evacuating all the backups there, and finally removing that extent from SOBR - just an option.
Who is online
Users browsing this forum: No registered users and 46 guests