Trend Micro Incorporated reserves the right to make changes to this document and to the product described herein without notice. Before installing and using the product, review the readme files, release notes, and/or the latest version of the applicable documentation, which are available from the Trend Micro website at:
http://docs.trendmicro.com
Trend Micro and the Trend Micro t-ball logo are trademarks or registered trademarks of Trend Micro Incorporated. All other product or company names may be trademarks or registered trademarks of their owners.
Copyright © 2013. Trend Micro Incorporated. All rights reserved. Document Part No.: APEM26217/131118
Release Date: December 2013
This documentation introduces the main features of the product and/or provides installation instructions for a production environment. Read through the documentation before installing or using the product.
Detailed information about how to use specific features within the product may be available at the Trend Micro Online Help Center and/or the Trend Micro Knowledge Base.
Trend Micro always seeks to improve its documentation. If you have questions,
comments, or suggestions about this or any Trend Micro document, please contact us at docs@trendmicro.com.
Evaluate this documentation on the following site:
i
Table of Contents
Introduction
Introduction ... iii Purpose ... iv
Chapter 1: Backing Up on Physical Machines
Backing up SafeSync 2.0 on a Physical Machine ... 1-2
Chapter 2: Restoring on Physical Machines
Restoring SafeSync 2.0 on a Physical Machine ... 2-2
Chapter 3: Backing Up and Restoring on Virtual Machines
Backing up and Restoring SafeSync 2.0 on a Virtual Machine ... 3-2
Chapter 4: Preparing the Environment
Preparing the Environment for SafeSync 2.1 ... 4-2
Chapter 5: Executing SafeSync 2.1 Migration Script
Migrating Single Server Deployments ... 5-2 Migrating High Availability Deployments ... 5-2
Chapter 6: Verifying Successful Migration
Verifying Successful Migration ... 6-2
Chapter 7: Integrating Active Directory
Integrating Active Directory ... 7-2
Chapter 8: Error Messages
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
ii
iii
Preface
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
iv
Purpose
1-1
Chapter 1
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
1-2
Backing up SafeSync 2.0 on a Physical
Machine
Procedure
1. Get the UUID for the /root and /boot partitions by executing the following command:
root@appliance1:~# sudo cat /etc/fstab.
2. Reboot the server using the Ubuntu Live CD.
Note
Run the backup on a different server.
Backing Up on Physical Machines
1-3
a. Get the name of the original /root and /boot partitions through the “Original UUID” on the new server.
root@appliance1:~# sudo cat /etc/fstab
Note
The name of each partition may be different on the new server, but the UUID remains the same.
b. Backup the /root partition to a file.
root@appliance1:~# sudo dd if=/dev/sda1 of=/mnt/sda1.bk
Note
/dev/sda1 is the name of the /boot partition, and /mnt/sda1.bk is the backup file.
c. Backup the /boot partition to a file.
root@appliance1:~# sudo dd if=/dev/sdb1 of=/mnt/sdb1.bk
Note
/dev/sdb1 is the name of the /boot partition, and /mnt/sdb1.bk is the backup file.
2-1
Chapter 2
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
2-2
Restoring SafeSync 2.0 on a Physical Machine
Procedure
1. Reboot the server using the Ubuntu Live CD.
Note
Install the backup SafeSync for Enterprise on a different computer.
2. To restore the server from the backup files to the original partitions:
a. Get the name of each partition using the “UUID” for the new installation. root@appliance1:~# sudo cat /etc/fstab
Note
The name of each partition may have changed, but UUID is the same. b. Restore the backup file to the /root partition.
root@appliance1:~# sudo dd if=/mnt/sda1.bk of=/dev/sda1
Note
/dev/sda1 is the name of the /root partition, and /mnt/sda1.bk is the backup file.
c. Restore the backup file to the /boot partition.
root@appliance1:~# sudo dd if=/mnt/sdb1.bk of=/dev/sdb1
Note
/dev/sdb1 is the name of the /boot partition, and /mnt/sdb1.bk is the backup file.
Restoring on Physical Machines
2-3 Note
3-1
Chapter 3
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
3-2
Backing up and Restoring SafeSync 2.0 on a
Virtual Machine
Procedure
1. To backup SafeSync 2.0 virtual machines, take a snapshot of the virtual machine.
4-1
Chapter 4
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
4-2
Preparing the Environment for SafeSync 2.1
Procedure
1. Verify the bare metal server or virtual machine meets the following system requirements:
• RAM : 8GB minimum (32~64GB recommended)
• ExtraDisk Space: 32GB available to perform SSFE 2.1 migration.
2. Copy the migration script and upgrade package to the SafeSync 2.0 server:
• Script file: migration.sh
• Package: SafeSyncForEnterprise_UpgradePackage-2.1-XXXX.tar.gz
Note
Copy these files to the target folder /home/safesync.
Note
5-1
Chapter 5
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
5-2
Migrating Single Server Deployments
Procedure
1. Run the migration script as the “root” user.
root@appliance1:~# sudo sh migration.sh
SafeSyncForEnterprise_UpgradePackage-2.1-XXXX.tar.gz
2. Verify that SafeSync 2.0 was backed up.
3. Press Y to continue the migration.
Note
A log file is created during migration: /var/log/osdp/upgrade.log
The new packages install automatically.
4. Press any key to reboot the server after migration completes.
Migrating High Availability Deployments
Procedure
Executing SafeSync 2.1 Migration Script
5-3
root@appliance1:~# :~# sudo sh migration.sh
SafeSyncForEnterprise_UpgradePackage-2.1-XXXX.tar.gz
2. Verify that SafeSync 2.0 was backed up.
3. Press Y to continue the migration.
4. Provide the following information for Appliance2:
• IP address of Appliance2
• Password safesync
5. Press Y to continue the migration.
Note
A log file is created during migration: /var/log/osdp/upgrade.log. The new packages install automatically for Appliance1 and Appliance2.
6-1
Chapter 6
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
6-2
Verifying Successful Migration
Procedure
1. Confirm all services started successfully:
Note
Log on as the “root” user. a. “mgmtui” service
root@appliance1:~# sudo supervisorctl status mgmtui
The service must be RUNNING. b. “healthcheck” service
root@appliance1:~# sudo supervisorctl status healthcheck
The service must be RUNNING. c. “perlbal80” service
root@appliance1:~# sudo supervisorctl status perlbal80
Verifying Successful Migration
6-3
d. “perlbalmgmtui” service
root@appliance1:~# sudo supervisorctl status perlbalmgmtui
The service must be RUNNING. e. “apache2” service
root@appliance1:~# sudo service apache2 status
The service must be running. f. “mogilefsd” service
root@appliance1:~# sudo cat /var/run/mogile/ mogilefsd.pid
The pid of service must be listed. g. “mogstored” service
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
6-4
The pid of service must be listed. h. “grunjobs” service
root@appliance1:~# sudo service grunjobs status
There must be one or more grunjobs running. i. “gearman-job-server” service
root@appliance1:~# sudo cat /var/run/gearman/gearman.pid
The pid of service must be listed. j. “tmsyslog” service
root@appliance1:~# sudo service tmsyslog status
The service must be running. k. “nginx” service
Verifying Successful Migration
6-5
The service must be running. l. “kmsd” service
root@appliance1:~# sudo screen –ls
There must be three sockets in /var/run/screen/S-root. m. “lighttpd” service
root@appliance1:~# sudo service lighttpd status
The service must be running.
2. Purge the browsing history from your browser.
Important
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
6-6
Verifying Successful Migration
6-7
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
6-8
3. Check the system status from the SafeSync management console:
• For single server deployments:
a. Log on to the SafeSync management console. b. Go to the Dashboard screen.
c. Verify that there are no system status alerts.
Note
Verifying Successful Migration
6-9 Note
Ignore the Secondary Server error when deploying a single server.
• For high availability deployments:
a. Log on to the SafeSync management console. b. Go to the Dashboard screen.
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
7-1
Chapter 7
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
7-2
Integrating Active Directory
After successfully preforming the migration, Active Directory integration settings must be reset to connect to the Active Directory server. SafeSync 2.0 Active Directory settings will not work properly for SafeSync 2.1
Procedure
1. Click Enable Active Directory integration.
Integrating Active Directory
7-3
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
7-4
3. If you provided new Active Directory settings in Step 2, click Purge existing AD
user accounts from the SafeSync database. 4. Add new Active Directory user accounts.
Integrating Active Directory
8-1
Chapter 8
Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide
8-2
Pre-installation Migration Error Messages
If you encounter any of the following error messages, troubleshoot the SafeSync 2.0 installation or report the issue to the Trend Micro support team.ERROR MESSAGE INFORMATION
Checking Environment
The minimum system requirements are not met. Failed to stop
Apache2 service
Unable to stop the Apache2 service before migration Failed to backup
MySQL
Unable to back up SafeSync 2.0 database before migration Failed to stop
services
Unable to stop SafeSync 2.0 services before migration Failed to backup
files
Unable to backup SafeSync 2.0 system files before migration
Migration Error Messages
If the following messages appear during migration, the migration may need to be rolled back and Trend Micro support contacted to provide support.
ERROR MESSAGE INFORMATION
Failed to install files Unable to install SafeSync 2.1 files Failed to install third
party packages
Unable to install SafeSync 2.1 packages Failed to run
Custom Script