✎ [V9] FAQ: How to migrate AhsayCBS onto a new server? [Ahsay Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
===== [V9] FAQ: How to migrate AhsayCBS onto a new server? =====

<html>
 <b>
  Article ID</b>: 9307
 <br/>
 <b>
  Reviewed</b>: 2022-01-10
 <br/>
 <br/>
 <b>
  Product Version:
 </b>
 <br/>
 AhsayCBS: 9.1 to 9.x
 <br/>
 OS: Windows, Linux
</html>


===== Description =====
This article contains information on how to migrate your AhsayCBS application onto a new hardware (Windows to Windows, or Linux to Linux).
Migration from/to different OS platform is not supported (AhsayUBS to Windows, Windows to Linux, etc), and may require configuring new settings.


===== Steps to setup new CBS host =====
<html>
 To migrate your AhsayCBS application to a new server, refer to the following steps:
 <br/>
 <br/>
 <u>Value of %Applicaton Home% for various operating system</u>:
 <br/>
 <ul>
  <li>
   <font color=black>(Windows) C:\Program Files\AhsayCBS</font>
  </li>
  <li>
   <font color=black>(Linux) /usr/local/cbs</font>
  </li>
 </ul>

 <BR>
 <ol>
  <li>
   <font color=black>Document all configuration settings of your current AhsayCBS server (e.g. email settings, policy settings, replication settings ... etc).</font>
   <br/>
   <br/>
   <br/>
  </li>
  <li>
   <font color=black>It is recommended you install the same CBS version as your current AhsayCBS server. 
   <br/>
   However, if you did not retain a copy of that version's installer, then Download the latest version of AhsayCBS (.exe or .tar.gz according to the new server's operating system platform) by
   <a href="http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_downloads_latest-software_ahsaycbs">Clicking Here</a>. (It is recommended you first do an in-place upgrade of your current CBS with the new version you just downloaded, before continuing to migrate the CBS settings.)</font>
   <br/>
   <br/>
   <br/>
  </li>
  <li>
   <font color=black>Install AhsayCBS on the new server.
   <br/>
   <br/>
   Note: For AhsayCBS installation on Windows, update the Windows Service's <I>Log On</I> setting if necessary.
    <br/>
    <br/>
      <img style="width:25%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5215_0.png"/>
    <br>
    <br>
    Do not edit the Windows <I>Log On</I> setting of the NFS Service (Ahsay Systems Corporation) Service.</font>
   <br/>
   <br/>
   <br/>
  </li>
  <li>
   <font color=black>Shutdown the AhsayCBS service on the current production (original) AhsayCBS server.
   <br/>
   <br/>
   <ul>
    <li>
     <font color=black>(Windows) <b>Control Panel</b> &gt; <b>Administrative Tools</b> &gt; <b>Services</b> &gt; <b>Ahsay Cloud Backup Suite</b></font>
    </li>
    <li>
     <font color=black>(Linux) Run the script file at  [ %Applicaton Home% / bin / shutdown.sh ]</font>
    </li>

   </ul>  <!--  xxxxxxxxxx -->
<!--
   <br>
   <font color=orange>
     <b>Note</b>: If you are performing the migration in multiple stages (e.g. migrating account-by-account to the new server), skip this step and continue to the next step.</font>
   </span>
   <br/>
-->
   <br/>
   <br/>
  </li>

  </OL>
  <U><FONT SIZE=+1 COLOR=black>CBS Configuration Migration</FONT></U>
  <UL>
   <font color=black>1. Copy the configuration files to, or manually re-configure the setting for the new AhsayCBS server.</font>
   <br/>
   <br/>
   <ul>
    <!-- xxx SAME PLATFORM xxx -->  
    <li>
     <font color=black><b>For migration to a the <u>same OS platform</u> (e.g. Windows to Windows, or Linux to Linux) <U>and</U>, on  <u>exact same version</u> (e.g. AhsayCBS version 9.1.0.50 to version 9.1.0.50) or <u>different CBS Version</u> (e.g. from AhsayCBS version 8.5.4.86 to new host running version 9.1.0.50), you can copy the configuration files over to the new server</b>. This will preserve Sub-Admin ID#, Predefined Destination ID#, SSL Certificate, 2FA settings, User Profiles, etc.</font>
     <br/>
     <br/>
     <font color=black>(If <b><i>different CBS Version</i></b>, it is recommended you first do an in-place upgrade of your current CBS with the new version, before continuing to migrate the CBS settings.) </font>
     <br/>
     <br/>
     <ul>
      <li>
       <font color=black>a. Shutdown the AhsayCBS service on the new AhsayCBS server.</font>
       <br/>
       <br/>
       <ul>
        <li>
         <font color=black>(Windows) <b>Control Panel</b> &gt; <b>Administrative Tools</b> &gt; <b>Services</b> &gt; <b>Ahsay Cloud Backup Suite</b></font>
        </li>
        <li>
         <font color=black>(Linux) Run the script file at  [ %Applicaton Home% / bin / shutdown.sh ]</font>
        </li>
       </ul>
      </li>
      <br>
      
      <li>
       <font color=black>b. Copy the following directories from the existing AhsayCBS to the new AhsayCBS server.
       <br/>
       <br/>
<!--
       %Applicaton Home%\conf\*.*
       <br/>
       %Applicaton Home%\conf\Branding
-->
       %Applicaton Home%\conf
       <br/>
       <br/>
       Note: AhsayCBS migration procedure is only applicable when the current and new hardware run same OS platform (Windows to Windows, or Linux to Linux); we do not support cross-platform migration (Linux to Windows, AhsayUBS to Linux, etc).
       <br>
       <br>
       Also, if you have not shutdown the existing AhsayCBS server, you may be in violation of licensing terms by running two servers with the same license. Only one license key may be applied to any one active CBS server. From the CBS Web Console, access the License page to verify.
       </font>
       <br/>
       <br/>
       </li>
       
       
      <li>
      <font color=black>c. To preserve existing Policies and User Groups, copy the following directories from the existing AhsayCBS to the new AhsayCBS server. 
       <br>
       <br>
       %Applicaton Home%\system\obs\policies
       </font>
       <br/>
       <br/>
       </li>


      <li>
      <font color=black>d. To preserve existing logs, copy the following directories from the existing AhsayCBS to the new AhsayCBS server. 
       <br>
       <br>
       %Applicaton Home%\logs
       <br/>
       %Applicaton Home%\system
       </font>
       <br/>
       <br/>
       </li>


<!--
      <li>
       <font color=black>e. Startup the AhsayCBS service on the <B>new</B> AhsayCBS server. (The old CBS server should remain shutdown)</font>
       <br/>
       <br/>
       <ul>
        <li>
         <font color=black>(Windows) <b>Control Panel</b> &gt; <b>Administrative Tools</b> &gt; <b>Services</b> &gt; <b>Ahsay Cloud Backup Suite</b></font>
        </li>
        <li>
         <font color=black>(Linux) Run the script file at  [ ${Install-Home} / bin / startup.sh ]</font>
        </li>
       </ul>
      </li>
     </ul>
     <br/>
     <br>
    </li>
-->

</UL>
    <!-- xxx DIFFERENT PLATFORM xxx -->  
    <li>
     <font color=black><b>For migration to a <u>different OS</u>, you will need to manually re-configure the server settings</b>.</font> <FONT COLOR=orange>Warning: Your Sub-Admin ID and Predefined Destination settings may receive new ID# and break existing User Profile or Policy Group assignment.</FONT>
     <br/>
     <br/>
     <ul>
      <li>
       <font color=black>a. Login to the AhsayCBS web console of the new server.</font>
       <br/>
       <br/>
      </li>
      <li>
       <font color=black>b. Manually re-configure all settings for the new AhsayCBS server, matching the settings found on your current AhsayCBS server.
       <br/>
       <br/>
       <font color=red><b>Important</b>: Do not replace the configuration files from the old to new server directly, configuration files from a old CBS host platform (e.g. AhsayUBS) is not fully compatible with the new CBS host (e.g. Windows).
        </font>
        </font>
      </li>
      <br/>
      <li>
       <font color=black>c. After you have manually configured the new CBS to match, you can copy from the original CBS the <I>"%Applicaton Home%\conf\users.xml"</I> and the <I>"%Applicaton Home%\system\obs\policies\*.*"</I>, to the new CBS server. Warning: Predefined Destination ID# and Sub-Admin ID# may be different; further manual reconfiguration may be required to successfully migrate your CBS to new platform.
       </font>
      </li>
     </ul>
    </li>
   </ul>
   <br/>
   <br/>


  </li>
  <li>
   <font color=black>2. Copy the System Home and User Home to the new AhsayCBS server. [AhsayCBS Service should be <I>stopped</I>]</font>
   <br/>
   <br/>
   <ul>
    <li>
     <font color=black><b>For System Home and User Home directories located on <u>local volumes</u>, you can copy the System Home and User Home over to the new server</b>:</font>
     <br/>
     <br/>
     <ul>
      <li>
       <font color=black>a. Copy the System Home folder from the existing server to the new AhsayCBS server.</font>
       <br/>
       <br/>
      </li>
      <li>
       <font color=black>b. Login to the AhsayCBS web console (of the new AhsayCBS).</font>
       <br/>
       <br/>
      </li>
      <li>
       <font color=black>c. (If necessary) Update the System Home setting under <b>System Settings</b> &gt; <b>Basic</b> &gt; <b>General</b> &gt; <b>System Home</b> to where you have copied the System Home folder to.</font>
       <br/>
       <br/>
          <img style="width:55%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5215_1.png"/>
         <br>
       <br>
      </li>
      <li>
       <font color=black>d. With the AhsayCBS Service <b><I>stopped</I></b> on both servers, Copy the User Home folder from the existing server to the new AhsayCBS server.</font>
       <br/>
       <br/>
       <font color=black>Note: Copy the entire User Home to the new server if the AhsayCBS will be migrated at once. 
       <br><br>
       Alternatively, copy each backup account one-by-one if the migration will be performed in stages:
       <br>
       <ul>
        For example, copy:
        <br/>
        <br/>
        %Existing_Location%\UserHome\%username1%
        <br/>
        %Existing_Location%\UserHome\%username2%
        <br/>
        ...
        <br/>
        <br/>
        to
        <br/>
        <br/>
        %New_Location%\UserHome\%username1%
        <br/>
        %New_Location%\UserHome\%username2%
        <br/>
        ...
        </ul>
       </font>
       <br/>
       <br/>
      </li>
      <li>
       <font color=black>e. (If necessary) Update the User Home setting under <b>Backup / Restore</b> &gt; <b>Basic</b> &gt; <b>General</b> &gt; <b>User Home</b> to where you have copied the User Home folder to.</font>
       <br/>
       <br/>
          <img style="width:55%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5215_2.png"/>
      </li>
     </ul>
     <br>
     <br/>
    </li>
    <li>
     <font color=black><b>For System Home and User Home directories located on a <u>network volume</u>, ensure that the network System Home and User Home are accessible on the new server</b>:</font>
     <br/>
     <br/>
     <ul>
      <li>
       <font color=black>a. Make sure that the network System Home and User Home are accessible by the new AhsayCBS server.</font>
       <br/>
       <br/>
      </li>
      <li>
       <font color=black>b. Login to the AhsayCBS web console of the new server, check on the System Home setting under <b>System Settings</b> &gt; <b>Basic</b> &gt; <b>General</b> &gt; <b>System Home</b>, confirm if it is configured to the correct network volume.</font>
       <br/>
       <br/>
      </li>
      
      <li>
       <font color=black>c. Check on the User Home setting under <b>Backup / Restore</b> &gt; <b>Basic</b> &gt; <b>General</b> &gt; <b>User Home</b>, confirm if it is configured to the correct network volume.</font>
      </li>
     </ul>
    </li>
   </ul>
   <br/>
   <br/>
  </li>
  
  <li>
   <font color=black>3. Check on the AhsayCBS settings afterward.</font>
   <br/>
   <br/>
   <ul>
    <li>
     <font color=black>Confirm if the License Details under the AhsayCBS web console at <b>System Settings</b> &gt; <b>License</b> &gt; <b>General</b>.</font>
     <br/>
     <br/>
        <img style="width:55%; border:thin solid black" src="http://wiki.ahsay.com/lib/exe/fetch.php?media=public:5215_3.png"/>
     <br>
     <br>
    </li>
    <li>
     <font color=black>Confirm if all backup users are displayed under the AhsayCBS web console at <b>Backup / Restore</b> &gt; <b>Users, Groups, Policies</b> &gt; <b>Backup User</b>.</font>
     <br/>
     <br/>
    </li>
    <li>
     <font color=black>Re-configure the server settings if necessary.</font>
    </li>
    <br/>
    <li>
     <font color=black>If branded, then <B>Rebuild Clients</B></font>
    </li>
   </ul>
  </li>
 </ol>
 <br/>
 <br/>

 <font color=black>4. Change in CBS Backup Server FQDN?</font>
 <br/> <br/>
 <UL><font color=red><b>Important</b>: For cases where the backup server's FQDN is changed after the migration, and you cannot reuse the old FQDN, the client agents must be re-configured to point to the new CBS FQDN on each client manually. There is no method to push the change.</font>
 </UL>
  <UL>Open the AhsayOBM / ACB user interface, click <b>Show advanced option</b>, to update the Backup Server setting.</UL>


<br/><br/><br/>
</html>



===== Keywords =====
obs, migration, move, relocate, re-locate, hardware, new cbs, new hardware, cbs-to-cbs
User Tools

Site Tools

Page Tools
