Seed Backup Migration
Overview
Seed Backup Migration is a useful feature to quickly move large backup data from the client machine to the backup server. Using this feature, the initial seed backup can be taken in a local external drive connected to the client machine and the external drive can then be physically moved to the remote backup server’s environment to migrate the data into the backup server. After the data migration and after performing the server side and client side Seed Backup Migration steps, the incremental backups can run directly from the client to the remote backup Server.
Seed Backup Migration
-
Configure a backup schedule in the ACCDataVault client system. Log into client’s ACCDataVault web console page and select 'Backup -> Add Backup Schedule' from the top menu.
-
Select the ‘Backup Type’ as ‘Same Machine’ in Step 3 and enter the external drive location for the ‘Local Backup Location’. After entering all the other backup details, save the backup schedule.
Note : 'Same Machine' backup feature is available only from 2.3 release. It can be used only for 'Seed Backup Migration'.
-
Run the backup, check the progress and make sure the backup runs to completion.
-
When the backup is complete, suspend the backup schedule.
-
(You can skip this step if you are migrating the backup data from a Client installation using local backup) If you are migrating the backup data from v3.0/later backup server using MySQL Server as the backend database, then the ACCDataVault database 'sgbackup.db' file will not be available in the backup location since v3.0/later backup server uses MySQL as the backend database. You need to export the metadata from MySQL to SQLite database by following the below steps :
- Open a command prompt and go the <ACCDataVault_HOME> folder.
- Execute the following command :
'bin\StoreGrid.exe ExportToSQLiteDatabase' (for Windows)
'./bin/StoreGrid ExportToSQLiteDatabase' (for Linux) This will export all the clients and backups' to SQLite database (sgbackup.db) in the backup location. If you wish to migrate a particular client (or) backup, then you can execute the above command as follows :
bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name>
bin\StoreGrid.exe ExportToSQLiteDatabase <Client_Name> <Backup_Name>
-
Disconnect the external drive from the client machine and connect the external device to the remote backup server.
-
Copy the client's data (Z:\backup\1) from the external device to some temporary location in the drive where you are planning to store the backup data in the remote backup server. Like for example, if your storage device is the E: drive, then copy the data to say “E:\LTOR”. You don’t have to copy the data to the temporary location and you can migrate the data directly from the external drive itself. However, the migration might take a little longer to complete, based on the speed of the external drive.
 
-
Go to the remote backup server’s web console "Server Admin-> Reseller Management -> Seed Backup Migration (Icon)" page. Enter the location of the client's data followed by the 1/ directory. For example, if you have copied the client's data from the external drive to the temporary E:\LTOR location in the backup server, enter location as E:/LTOR/1/ in this page. If you have not copied the data to a temporary location, enter the location of the external drive, like for example Z:/backup/1. After entering the path, click on the "Submit Location" button.
-
The client name will be displayed. Select the client. If you are doing the data migration from this client for the first time, enter the target customer under which the client is to be migrated and the location where the backup data is to be stored. Click the "Migrate" button.
-
In the client system, take a backup of the <ACCDataVault Installation Location>/data/<backup name>/sgprp.db file. This is just to ensure you can recover this DB file if you need to do the client side migration again, if required.
-
Go to “Administration -> Seed Backup Migration” page in the client machine. If the client machine is backing up locally, then select the backups that should continue with the incremental backups directly to the remote backup server. Provide the New Backup Server Name and confirm that the backup data of the selected schedules has already been moved to the new backup server and that you have run the Seed Backup Migration module in the remote backup server (confirm this from the check box).
If the client machine is backing up to a remote Backup Server, then select the remote Backup Server from the list to where the client machine is currently backing up to and then:
-
Choose the option 'Make this client machine backup to a different backup server from now on' to continue with the incremental backups directly to the remote backup server and provide the New Backup Server Name. In the table listing the backup schedules, select the backup schedule(s) whose data has been moved to the new backup server. You can select all the backup schedules by checking the checkbox against the "Available Backups" column name. Confirm that the backup data of the selected schedules has already been moved to the new backup server and that you have run the Seed Backup Migration module in the remote backup server (confirm this from the check box).
-
Choose the option 'Make this client machine backup locally (same machine) from now on' to make the client machine start backing up locally to itself. You can use this option to do 'Seed Backup Migration of Additional Fullbackup data'. After selecting this option, you need to provide the Local Backup Location for the selected backup schedule(s). In the table listing the backup schedules, select the backup schedule(s) to start backing up locally to the same machine. You can select all the backup schedules by checking the checkbox against the "Available Backups" column name. Confirm that you have opted to run Additional Full Backup locally in this machine to the specified backup location. (confirm this from the check box).
Click the Migrate button to complete migration.
-
To confirm that the migration has been successful, try running an incremental backup. If the incremental backup runs fine, the migration is successful and you can delete the backup of the db file that you created in step 10 above. If the client starts taking a full backup, then suspend the backup, replace the sgprp.db file with its backup that you created in step 10 and check the server migration steps again.
Seed Backup Migration Progress
-
Summary of progress
This gives the total summary of the Migration progress.
Success Rate : This gives the total success rate.
Elapsed Time : This gives the total time taken after the migration started.
No of clients migrated : This gives the total number of clients migrated out of the total clients for migration.
Messages : Messages regarding the Migration.
Warning : Warnings regarding the migration progress.
Overall migration progress.
-
Clients scheduled for migration
This lists the client lists for migration, their total number of backups for migration, their total migrated backups, their target customer and their migration status.
Troubleshooting Tips
Limitations
- ACCDataVault version of the client should be the same as the Backup Server while performing server side Seed Backup Migration.
- When ACCDataVault is stopped during Server side "Seed Backup Migration", it cannot be resumed later from where it has been left. It has to be run afresh again.
- Server side "Seed Backup Migration" report cannot be seen once you leave the web console page.
- When there isn’t enough Space in the remote backup server, migration will still proceed to completion by automatically taking the necessary space.
- File version migration is not supported. Only full backups and incremental backups can be migrated.
|
Home 
Print
