Article ID: 2526
Reviewed: 28/07/2014

Product Version:
AhsayOBS: v6.29.0.0, Pre-7.3.2.0
OS: All platforms

Description:
This article contain information on how to migrate your AhsayOBS application onto a new hardware.

Steps:
To migrate your AhsayOBS application to a new server, refer to the following steps:

Value of ${Install-Home} for various operating system:

• (Windows) C:\Program Files\AhsayOBS and AhsayRPS
• (Linux) /usr/local/obsr

1. Document all configuration settings of your current AhsayOBS server (e.g. email settings, system routine job settings, replication settings ... etc).
   
   
   
2. Download the latest version of AhsayOBS (.exe or .tar.gz according to the new server's operating system platform) by Clicking Here.
   
   
   
3. Install AhsayOBS on the new server.
   
   Note:
   For AhsayOBS installation on Windows. If the Windows service uses a non-default account, update the setting after the installation.
   
   
   
   
   
   
4. Shutdown the AhsayOBS service on the existing AhsayOBS:
   
   
   • (Windows) [Control Panel] > [Administrative Tools] > [Services] > [Ahsay Offsite Backup Server and Replication Server]
   • (Linux) Run [ service obsr stop] or [ ${Install-Home} / bin / shutdown.sh ]
   Important:
   If you will be performing the migration gradually (e.g. migrating account-by-account to the new server), skip to the next step.
   
   
   
5. Login to the new AhsayOBS web management console (of the new AhsayOBS), select [Software License] and enter the Licensee Name and License Key
   
   
   
   
   
   
6. Press the [Update] button, ensure that the license is properly applied by checking the User Add-on Modules available under [Software License]
   
   Important:
   Before continuing on with the next step, be absolutely sure that the license has been properly applied onto the new server (before updating the User Home settings). Failure to do so will result in all backup accounts being suspended and add-on modules being reset.
   
   It is recommended to shutdown the previously running AhsayOBS service to ensure that you are not running two servers with the same license key.
   
   However, if the migration will be performed gradually (e.g. migrating account-by-account to the new server), you can apply the same AhsayOBS license onto the second server, but note that an Internal Error 1012 license error will be displayed (which is normal, because a single license is being used by multiple AhsayOBS).
   
   You will be given a grace period of 14 days until the backup service is stopped on one of the AhsayOBS.  At that time, if the migration is not yet completed, you can contact us to extend the grace period.
   
   
   
7. Update the system home, policy home and user home on the new AhsayOBS server.
   
   
   • For migration where the system home, policy home and user home are located on a local volume (they need to be copied to the new server):
     
     
     • Copy the System Home, User Home and Policy Home directories from the existing server to the new AhsayOBS server.
       
       
     • Login to the new AhsayOBS server's web management console.
       
       
     • Select [Manage System] and [Server Configuration], update the system home, policy home and user homes according to their current locations:
       
       
       
     Note:
     Copy the entire User Home to the new server if AhsayOBS will be migrated at once, or copy each backup account one-by-one if the migration will be performed gradually.  For example, copy:
     
     %Existing_Location%\UserHome\%username1%
     %Existing_Location%\UserHome\%username2%
     ...
     
     to
     
     %New_Location%\user_home\%username1%
     %New_Location%\user_home\%username2%
     ...
     
     It is recommended to suspend the backup account while copying their data to ensure that no backup job can be performed while the data are being copied.
     
     
     
   • For migration where the system home, policy home and user home are located on a network volume (they do not need to be moved), skip to the next step.
   
   
8. Re-configure the new AhsayOBS server's setting.
   
   
   • For migration to a different version (e.g. existing AhsayOBS is on version 6.3.0.0, new AhsayOBS is 6.17.0.0) (migrating and upgrading at the same time):
     
     
     • Login to the AhsayOBS web management console of the new server.
       
       
     • Re-configure the new AhsayOBS server manually (e.g. email settings, proxy settings, options, trial user settings, replication settings ... etc), with the settings documented in step 1.
       
       Important:
       Do not replace (copy and paste) any of the xml configuration files from the old to new server directly, configuration files from a previous version is not fully compatible with a newer version of the software. Re-configure the new AhsayOBS server instead.
     
     
   • For migration to an exactly same version (e.g. existing AhsayOBS is on version 6.17.0.0, new AhsayOBS is 6.17.0.0):
     
     
     • Shutdown the AhsayOBS service on the new server.
       
       
     • Copy all configuration files (e.g. server.xml) within the ${Install-Home}\conf folder from the old to the new AhsayOBS server (to the same directory on the new server).
       
       
     • Startup the AhsayOBS service on the new server.
   
   
9. Login to the AhsayOBS web management console of the new server, check and update on the configuration settings if necessary.

Note:
If the backup server hostname is changed after the migration, the hostname setting on the client application must be changed on each client manually:

Open the AhsayOBM / ACB user interface, click Option, then update the Backup Server setting:


In some cases, the login screen maybe bypassed because the user had selected to save their password. Login to the client agent, select User Profile, disable the Save password setting to re-access the login screen.

Important:
The backup server hostname setting cannot be changed from the server side, it must be changed manually via the client computer.


Keywords:
obs, migration, move, relocate, re-locate, hardware