Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Migrating Virtual Mobile Infrastructure (TMVMI) and Secure Access to TMVMI and Secure Access version 5.0

    • Updated:
    • 29 Mar 2016
    • Product/Version:
    • Virtual Mobile Infrastructure 3.0
    • Virtual Mobile Infrastructure 5.0
    • Platform:
    • Citrix XenServer 5.5
    • VMware ESX - 5.0
Summary

Learn how to migrate Virtual Mobile Infrastructure (TMVMI) and Secure Access 3.0 to version 5.0.

Note that we only support the migration of TMVMI Server and Secure Access 3.0 to version 5.0. If you are using TMVMI 1.0, 2.0, or 2.1, please upgrade first to TMVMI 3.0.

Contact the support team to get the migration script for TMVMI Server and Secure Access.

Details
Public

Before performing the migration, please check first the list below. If you do not follow the list, the migration will fail.

  • All the users should be offline. To forcefully disconnect all the users, you may consider stopping the server to execute the migration.
  • It is recommended to take snapshots of the server before doing the migration.
  • Disable HA, if it is enabled.
  • Do NOT shutdown the external storage during migration.
 
Contact the Trend Micro Technical Support to get the migration script "migrate.py".

If TMVMI 3.0 server is in single mode:

  1. Copy the migrate.py file to the /root folder of the TMVMI 3.0 server.
  2. Open the terminal on TMVMI Master Server and log on with the root user account.
  3. Navigate to /root folder and run the following command:

    cd /root

  4. Run the migrate script using the command below to export the TMVMI data:

    python migrate.py -a export

    The data file will be generated in path /gluster/server-data-backup and the file name is <server IP>.tar. For example, if your TMVMI 3.0 server IP is 10.64.91.230, the export data file is /gluster/server-data-backup/10.64.91.230.tar.

  5. Back up the export data to another server or your removable storage device.
  6. Shut down the TMVMI 3.0 server.
  7. Install the TMVMI 5.0 server. Follow the installation steps in IDG.
  8. Make sure the network configuration of TMVMI 5.0 is the same with TMVMI 3.0 server.
  9. Open the terminal on TMVMI Master Server and log on with the root user account.
  10. Run the following command to create folder /gluster/server-data-restore:

    mkdir /gluster/server-data-restore

  11. Copy the exported data file <server IP>.tar to /gluster/server-data-restore.
  12. Copy the migrate script migrate.py to /root.
  13. Open the terminal on TMVMI Master Server and log on with the root user account.
  14. Navigate to root folder and run the migrate.py script using the following command:

    cd /root
    python migrate.py -a import

  15. Reboot the TMVMI 5.0 server.

If TMVMI server is in multiple server mode:

  1. Copy the migrate.py file to the /root folder in the TMVMI 3.0 master server and slave server(s).
  2. Export the data from master server.
    1. Open the terminal on TMVMI master server and log on with the root user account by running the command below:

      cd /root

    2. Run the migrate script in master server using the command below:

      python migrate.py -a export

      For multiple servers, the number of export data files is dependent on the number of TMVMI slave servers. For example, if there are two (2) servers, one is master and the other is slave, it will generate two (2) export data files. If there are three (3) servers, one is master and the others are slave, it will generate three (3) export files.

      The export data files will be generated in path /gluster/server-data-backup, the file names are <master server IP>.tar and <slave server ip-metadata>.tar. For example, your TMVMI master server IP is 10.64.91.230 and slave server is 10.64.91.231, the export data files are /gluster/server-data-backup/10.64.91.230.tar and /gluster/server-data-backup/10.64.91.231- metadata.tar.

    3. Back up the exported data to another server or your removable storage device.
  3. Export the data from slave server(s).
    1. Open the terminal on TMVMI slave server and log on with the root user account using the command below:

      cd /root

    2. Run the migrate script in slave server using the following command:

      python migrate.py -a export –m <ipaddr>-metadata.tar

      The exported data file will be generated in path /gluster/server-data-backup and the file name is <server IP>.tar. For example, TMVMI slave server IP is 10.64.91.231, the exported data file name is /gluster/server-data-backup/10.64.91.231.tar.

    3. Back up the exported data to another server or your removable storage device. If there are multiple slave servers, you need to run Step 3 on each slave server.
  4. Shut down the TMVMI 3.0 servers.
  5. Install TMVMI 5.0 servers. Follow the installation steps in IDG.
  6. Make sure the network configuration of TMVMI 5.0 servers is the same with TMVMI 3.0 servers.
  7. Create folder /gluster/server-data-restore in both master server and slave server(s) using the following command:

    mkdir /gluster/server-data-restore

  8. Copy the exported data file to master server and slave server(s).
    1. Copy the files (<mster server IP>.tar and <slave server ip-metadata>.tar) that you exported in Step 2 to the folder /gluster/server-data-restore in master server.
    2. Copy the files (<slave server ip>.tar) that you exported in Step 3 to the folder /gluster/server-data-restore in slave server(s). If there are multiple slave servers, you need to copy the <slave server ip>.tar to each slave server.
  9. Copy the migrate script migrate.py to /root on master server and slave server(s).
  10. Navigate to root folder and run migrate.py on master server and slave server(s) using the command:

    cd /root
    python migrate.py -a import

  11. Reboot TMVMI 5.0 master server and slave server(s).

After you finished the TMVMI server migration, please also migrate the secure access server from version 3.0 to 5.0.

Not configured OAuth 2.0 for enrollment in TMVMI 3.0:

If you do NOT enable OAuth 2.0 for enrollment in TMVMI 3.0, we suggest to have a fresh installation of TMVMI 5.0 Secure Access server.

  1. Shut down the TMVMI 3.0 secure access server.
  2. Install a new TMVMI 5.0 secure access server.

Configured OAuth 2.0 for enrollment in TMVMI 3.0:

If you are using OAuth 2.0 for enrollment in TMVMI 3.0, please do migrate the secure access server using the following steps:

  1. Copy the migration script "migrate.py" to TMVMI 3.0 secure access server.
    For example, you can copy it to folder /root.
  2. Open the terminal on TMVMI 3.0 secure access server and log on with the root user account.
  3. Navigate to root folder using the command:

    cd /root

  4. Export OAuth data in TMVMI 3.0 secure access server by running the command below:

    python migrate.py export /root

    After the successful migration, you can get the migrate_data.tar.gz file in the root folder.

  5. Install TMVMI 5.0 secure access server.
  6. After the installation, copy the migrate.py and migrate_data.tar.gz to the root folder of TMVIM 5.0 secure access server.
  7. Import the OAuth data to TMVMI 5.0 secure access server using the following command:

    python migration.py import /root

  8. Restart the httpd service using the following command:

    service httpd restart

Premium
Internal
Rating:
Category:
Migrate
Solution Id:
1113239
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support


To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.


Need More Help?

Create a technical support case if you need further support.