Migrate the Absolute Service Virtual Appliance (VA)

Version 1

    Details

    PROBLEM
    When upgrading to a new LiveTime Virtual Appliance, there is a Migrate option that will allow you to bring attachments and other stored information to the new Virtual Appliance guest virtual machine.

    ENVIRONMENT
    LiveTime Virtual Appliance (All Versions)

    RESOLUTION
    Steps to migrate between old and new Virtual Appliance:

    [list=1:]

  • Get both Virtual Appliances up on different IP addresses but where they can still contact each other.
  • Ensure the new VA has plenty of RAM and disk space upon deployment to be usable.
  • Ensure the database details are known, or screenshot them, but the password will need to be known since that is not on screen.
  • Optionally, point the new VA to a temporary database to collect the Host tab information to get a new license (and skip Step 9). See Additional Information for details.
  • Stop Tomcat on old VA.
  • Backup the database.
  • If the new VA is going to need use the same IP as the old one, change the IP on the old VA to something different.
  • Point the new VA to the existing LiveTime database and upgrade as per upgrade instructions (use upgrade button in the browser under Advanced).
  • Request a license for the new Virtual Appliance with a screenshot of it's host tab. To get that, it will need to connect to a database first, but do NOT connect it to the existing database at this point in time.
  • Use the Migrate function on the new box to copy the output folder with attachments, indexes, etc. over from the old VA to the new one.
  • Once migration is complete the old VA can be shut down and provided no issues are reported with missing attachments, etc, then it can be removed completely.

    ADDITIONAL INFORMATION

    To prevent downtime, you may prefer to create a temporary database to connect the new Virtual Appliance to in Step 4. This way you can obtain the Host tab information required for a new license prior to proceeding. This allows for the time it takes to have the request for a new license fulfilled prior to bringing down your production LiveTime Virtual Appliance and causing downtime.

    Once you have the new license on hand, you can continue at Step 5 and skip Step 9 because you already have the license.

     


    Resolution

    PROBLEM
    When upgrading to a new LiveTime Virtual Appliance,  there is a Migrate option that will allow you to bring attachments and  other stored information to the new Virtual Appliance guest virtual  machine.

    ENVIRONMENT
    LiveTime Virtual Appliance (All Versions)

    RESOLUTION
    Steps to migrate between old and new Virtual Appliance:

    [list=1:]

  • Get both Virtual Appliances up on different IP addresses but where they can still contact each other.
  • Ensure the new VA has plenty of RAM and disk space upon deployment to be usable.
  • Ensure the database details are known, or screenshot them, but the password will need to be known since that is not on screen.
  • Optionally,  point the new VA to a temporary database to collect the Host tab  information to get a new license (and skip Step 9). See Additional  Information for details.
  • Stop Tomcat on old VA.
  • Backup the database.
  • If the new VA is going to need use the same IP as the old one, change the IP on the old VA to something different.
  • Point  the new VA to the existing LiveTime database and upgrade as per upgrade  instructions (use upgrade button in the browser under Advanced).
  • Request  a license for the new Virtual Appliance with a screenshot of it's host  tab. To get that, it will need to connect to a database first, but do  NOT connect it to the existing database at this point in time.
  • Use  the Migrate function on the new box to copy the output folder with  attachments, indexes, etc. over from the old VA to the new one.
  • Once  migration is complete the old VA can be shut down and provided no  issues are reported with missing attachments, etc, then it can be  removed completely.

    ADDITIONAL INFORMATION

    To prevent downtime, you may prefer to create a temporary database to connect the new  Virtual Appliance to in Step 4. This way you can obtain the Host tab  information required for a new license prior to proceeding. This allows  for the time it takes to have the request for a new license fulfilled  prior to bringing down your production LiveTime Virtual Appliance and  causing downtime.

    Once you have the new license on hand, you can continue at Step 5 and skip Step 9 because you already have the license.
  •