Splitting backup jobs

[dan.kennedy]

Is there any way to split an existing backup job without having to start from scratch with new jobs?

We originally set up a job for a customer to backup their whole organisation (in one job) but they since decided to migrate fully to Sharepoint Online and their repository size has grown to more than 5TB - and it's getting a bit out of hand!

I plan to create new separate jobs for Sharepoint, OneDrive, and Mailboxes but is there any way of doing this so we keep the files already backed up and don't end up doubling up on storage at our end?

[Polina]

Hi Dan,

There shouldn't be any issues with data duplication - if you point your new jobs to the same old repository VBO will reuse the existing data. Also, deleting a job from the console doesn't mean that the corresponding backup data is along with it; backups will remain safe in your repository.

[dan.kennedy]

Hi Polina,

Sorry, i didn't actually mention that the point of this would be to eventually get rid of this 5TB drive where all their data is currently stored and replace it with multiple smaller drives which are easier to manage going forward.

The customer has 7 year retention so i need to keep the data we have already backed up but I want to split it across different repositories (drives) so I can create new separate jobs without losing the historical backups and also doubling up data storage?

[Polina]

Hey Dan,

You will need to do some PowerShell scripting to move existing backups to new locations, and after that, your older restore points will still be available and accessible. Next, when you point your new backup jobs to the corresponding new repositories with older backups, VBO will perform a full run to re-enumerate all items in a database but at the same time backup traffic will be reduced to only the new or changed data.

Makes sense?