-
- Novice
- Posts: 5
- Liked: never
- Joined: Sep 15, 2020 4:46 pm
- Contact:
Moving data to new repository
Hi,
I am currently trying to move backup data from a repository on a NAS device to a local repository (on the backup server). After reading up on this it seemed, that it would simply be possible to add a new repository (with identical configuration) and then Robocopy the data to the new repository. After doing this the repository shows as "invalid" in Veeam Backup for M365. Is there anything I could check/change?
I am currently trying to move backup data from a repository on a NAS device to a local repository (on the backup server). After reading up on this it seemed, that it would simply be possible to add a new repository (with identical configuration) and then Robocopy the data to the new repository. After doing this the repository shows as "invalid" in Veeam Backup for M365. Is there anything I could check/change?
-
- Service Provider
- Posts: 470
- Liked: 119 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
-
- Product Manager
- Posts: 9793
- Liked: 2585 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Moving data to new repository
Hello Taalas
Moving data to a new repository is simple.
1) Remove the old repository in the VB365 console. This is important to close the open database connections to the repository files. If there are jobs pointed to that repository, disable them and point them to temporary repository while doing the migration.
2) Important: Copy the entire folder structure from the original repository to the new location
The following files/folders must be present in the root folder of the repository:
- Repository.sqlite
- Repository.xml
- Folders with year numbers which contain the database files
3) Add the root folder to the VB365 backup console as a new repository.
4) Target the job to the new repository.
If you have followed this steps and it still doesn't work, please open a case with our support team and tell me the case number.
Best,
Fabian
Moving data to a new repository is simple.
1) Remove the old repository in the VB365 console. This is important to close the open database connections to the repository files. If there are jobs pointed to that repository, disable them and point them to temporary repository while doing the migration.
2) Important: Copy the entire folder structure from the original repository to the new location
The following files/folders must be present in the root folder of the repository:
- Repository.sqlite
- Repository.xml
- Folders with year numbers which contain the database files
3) Add the root folder to the VB365 backup console as a new repository.
4) Target the job to the new repository.
If you have followed this steps and it still doesn't work, please open a case with our support team and tell me the case number.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 470
- Liked: 119 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Moving data to new repository
no need to shutdown the services? nice.
-
- Product Manager
- Posts: 9793
- Liked: 2585 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Moving data to new repository
If you want to move a single repository, services don't have to be disabled. But it can also work with disabling the services.
Just make sure, that the database files are not in use while copying or moving the data to the new location
Best,
Fabian
Just make sure, that the database files are not in use while copying or moving the data to the new location
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 470
- Liked: 119 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: Moving data to new repository
is there a way to check if they are in use, maybe powershell? just to be sure.
Who is online
Users browsing this forum: No registered users and 16 guests