Skip to main content
  • EN

Can anyone point me in the direction of a best practices/recommended process for doing maintenance on VBO repos, for example doing hardware maintenance on the VBO repo server, and want to move the data to another storage location, either temporarily or permanent migration?

Seem to be running into a lot of Jetdb errors, after we tried to figure out the best process

Hello @Cragdoo,

To move your datas to another repo you could:
1. Disable all backup jobs related to the repository you want to move.
2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.
3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).
4. Start the Veeam Backup for Microsoft Office 365 services.
5. Add the new repository with the moved data.
6. Open backup job settings and specify to use the new repository.

Some more detailed informations could be find here:
https://www.veeam.com/kb2649

There is also  a Powershell cmdlet “Move-VBOEntityData” that could be use to move data from one repo to another repo.
https://www.veeam.com/kb3067

 

Hello @Cragdoo,

To move your datas to another repo you could:
1. Disable all backup jobs related to the repository you want to move.
2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.
3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).
4. Start the Veeam Backup for Microsoft Office 365 services.
5. Add the new repository with the moved data.
6. Open backup job settings and specify to use the new repository.

Some more detailed informations could be find here:
https://www.veeam.com/kb2649

There is also  a Powershell cmdlet “Move-VBOEntityData” that could be use to move data from one repo to another repo.
https://www.veeam.com/kb3067

 

 

Just one note from a service provider perspective. If a number of organizations are configured on the same server, it may not be possible to stop the services and put all the backups on hold while the data is being moved.

This is an alternative method that works for changing repository location on the same VBM365 server or migrating data to a new VBM365 server (i.e. also for offloading repository data for a customer).

  1. Remove Backup Jobs from your VBM365. Remember to capture all settings as these jobs will have to be recreated.
  2. Remove Backup Repository from your VBM365.
  3. Copy/Move the files to the new location.
  4. If migrating to new server, add the same organization on the new VBM365 server
  5. (Re)create Backup Repository pointing to new location. It should pick up the settings from the repository.
  6. (Re)create the backup jobs.

Hello @Cragdoo,

To move your datas to another repo you could:
1. Disable all backup jobs related to the repository you want to move.
2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.
3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).
4. Start the Veeam Backup for Microsoft Office 365 services.
5. Add the new repository with the moved data.
6. Open backup job settings and specify to use the new repository.

Some more detailed informations could be find here:
https://www.veeam.com/kb2649

There is also  a Powershell cmdlet “Move-VBOEntityData” that could be use to move data from one repo to another repo.
https://www.veeam.com/kb3067

 

 

Just one note from a service provider perspective. If a number of organizations are configured on the same server, it may not be possible to stop the services and put all the backups on hold while the data is being moved.

This is an alternative method that works for changing repository location on the same VBM365 server or migrating data to a new VBM365 server (i.e. also for offloading repository data for a customer).

  1. Remove Backup Jobs from your VBM365. Remember to capture all settings as these jobs will have to be recreated.
  2. Remove Backup Repository from your VBM365.
  3. Copy/Move the files to the new location.
  4. If migrating to new server, add the same organization on the new VBM365 server
  5. (Re)create Backup Repository pointing to new location. It should pick up the settings from the repository.
  6. (Re)create the backup jobs.

 

 

If only there was a was to export all the job settings ….

It would be great to be able to back up all the job configurations. I know it's on the roadmap.

Hello @Cragdoo,

To move your datas to another repo you could:
1. Disable all backup jobs related to the repository you want to move.
2. Stop all the Veeam Backup for Microsoft Office 365 services before moving any data.
3. Copy the backup repository data to the backup repository location on the new repository location (using robocopy for example).
4. Start the Veeam Backup for Microsoft Office 365 services.
5. Add the new repository with the moved data.
6. Open backup job settings and specify to use the new repository.

Some more detailed informations could be find here:
https://www.veeam.com/kb2649

There is also  a Powershell cmdlet “Move-VBOEntityData” that could be use to move data from one repo to another repo.
https://www.veeam.com/kb3067

 

 

Just one note from a service provider perspective. If a number of organizations are configured on the same server, it may not be possible to stop the services and put all the backups on hold while the data is being moved.

This is an alternative method that works for changing repository location on the same VBM365 server or migrating data to a new VBM365 server (i.e. also for offloading repository data for a customer).

  1. Remove Backup Jobs from your VBM365. Remember to capture all settings as these jobs will have to be recreated.
  2. Remove Backup Repository from your VBM365.
  3. Copy/Move the files to the new location.
  4. If migrating to new server, add the same organization on the new VBM365 server
  5. (Re)create Backup Repository pointing to new location. It should pick up the settings from the repository.
  6. (Re)create the backup jobs.

FYI I wrote a tool to modify the hostnames in config.edb after a move/rename, as I had this issue myself: https://github.com/platima/veeam-host-rename-or-move/. This should save you from step 6 of having to recreate the backup jobs.

Comment


Terms & Conditions