Trend Micro Incorporated reserves the right to make changes to … · 2013. 12. 5. · Trend...

Trend Micro Incorporated reserves the right to make changes to this document and tothe product described herein without notice. Before installing and using the product,review the readme files, release notes, and/or the latest version of the applicabledocumentation, 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 ofTrend Micro Incorporated. All other product or company names may be trademarks orregistered trademarks of their owners.

Copyright © 2013. Trend Micro Incorporated. All rights reserved.

Document Part No.: APEM26217/131118

Release Date: December 2013

Protected by U.S. Patent No.: 5,951,698; 5,951,698

http://docs.trendmicro.com/en-us/home.aspx

This documentation introduces the main features of the product and/or providesinstallation instructions for a production environment. Read through the documentationbefore installing or using the product.

Detailed information about how to use specific features within the product may beavailable at the Trend Micro Online Help Center and/or the Trend Micro KnowledgeBase.

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 [email protected].

Evaluate this documentation on the following site:

http://www.trendmicro.com/download/documentation/rating.asp

mailto:%[email protected]

http://www.trendmicro.com/download/documentation/rating.asp

i

Table of ContentsIntroduction

Introduction ....................................................................................................... iii

Purpose ............................................................................................................... iv

Chapter 1: Backing Up on Physical MachinesBacking up SafeSync 2.0 on a Physical Machine ....................................... 1-2

Chapter 2: Restoring on Physical MachinesRestoring SafeSync 2.0 on a Physical Machine .......................................... 2-2

Chapter 3: Backing Up and Restoring on Virtual MachinesBacking up and Restoring SafeSync 2.0 on a Virtual Machine ................ 3-2

Chapter 4: Preparing the EnvironmentPreparing the Environment for SafeSync 2.1 ............................................. 4-2

Chapter 5: Executing SafeSync 2.1 Migration ScriptMigrating Single Server Deployments ......................................................... 5-2

Migrating High Availability Deployments .................................................. 5-2

Chapter 6: Verifying Successful MigrationVerifying Successful Migration ..................................................................... 6-2

Chapter 7: Integrating Active DirectoryIntegrating Active Directory ......................................................................... 7-2

Chapter 8: Error MessagesPre-installation Migration Error Messages ................................................. 8-2

Trend Micro™ SafeSync™ for Enterprise 2.1 System Migration Guide

ii

Migration Error Messages ............................................................................. 8-2

iii

Preface

Introduction


iv

PurposeThis internal document describes the process for system migration from the SafeSync™2.0 to 2.1.

1-1

Chapter 1

Backing Up on Physical Machines


1-2

Backing up SafeSync 2.0 on a PhysicalMachine

Procedure

1. Get the UUID for the /root and /boot partitions by executing the followingcommand:

root@appliance1:~# sudo cat /etc/fstab.

2. Reboot the server using the Ubuntu Live CD.

Note

Run the backup on a different server.

3. To backup the original /root and /boot partitions:

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

NoteThe name of each partition may be different on the new server, but the UUIDremains 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 thebackup 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 thebackup file.

4. Reboot the server without the Ubuntu Live CD.

2-1

Chapter 2

Restoring on Physical Machines


2-2

Restoring SafeSync 2.0 on a Physical Machine

Procedure

1. Reboot the server using the Ubuntu Live CD.

NoteInstall 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

NoteThe 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 thebackup 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 thebackup file.

3. Reboot the server without the Ubuntu Live CD.

Restoring on Physical Machines

2-3

NoteRollback to the original SafeSync for Enterprise 2.0 installation.

3-1

Chapter 3

Backing Up and Restoring on VirtualMachines


3-2

Backing up and Restoring SafeSync 2.0 on aVirtual Machine

Procedure

1. To backup SafeSync 2.0 virtual machines, take a snapshot of the virtual machine.

2. To restore SafeSync 2.0 on a virtual machine, revert to the SafeSync 2.0 backupsnapshot.

4-1

Chapter 4

Preparing the Environment


4-2

Preparing the Environment for SafeSync 2.1

Procedure

1. Verify the bare metal server or virtual machine meets the following systemrequirements:

• 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

NoteCopy these files to the target folder /home/safesync.

NoteFor high availability deployments, the files only need to be copied to Appliance1, notto both appliances.

5-1

Chapter 5

Executing SafeSync 2.1 MigrationScript


5-2

Migrating Single Server Deployments

Procedure

1. Run the migration script as the “root” user.

root@appliance1:~# sudo sh migration.shSafeSyncForEnterprise_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

1. Run the migration script as the “root” user.

Executing SafeSync 2.1 Migration Script

5-3

root@appliance1:~# :~# sudo sh migration.shSafeSyncForEnterprise_UpgradePackage-2.1-XXXX.tar.gz

2. Verify that SafeSync 2.0 was backed up.


4. Provide the following information for Appliance2:

• IP address of Appliance2

• Password safesync


Note

A log file is created during migration: /var/log/osdp/upgrade.log.

The new packages install automatically for Appliance1 and Appliance2.

6. Press any key to reboot the appliance after migration completes.

6-1

Chapter 6

Verifying Successful Migration


6-2


Procedure

1. Confirm all services started successfully:

NoteLog 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


c. “perlbal80” service

root@appliance1:~# sudo supervisorctl status perlbal80



6-3

d. “perlbalmgmtui” service

root@appliance1:~# sudo supervisorctl statusperlbalmgmtui


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

root@appliance1:~# sudo cat /var/run/mogstored.pid


6-4


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


j. “tmsyslog” service

root@appliance1:~# sudo service tmsyslog status


k. “nginx” service

root@appliance1:~# sudo /etc/init.d/nginx status


6-5


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


2. Purge the browsing history from your browser.

ImportantBefore logging on to the management console, purge the browsing history andwebsite cache data from your Internet browser.


6-6

Use the following graphic from Internet Explorer as a guide to delete yourbrowsing history.


6-7

Use the following graphics from Firefox as a guide to delete your browsing history.


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.

NoteIgnore the Database HA warning when deploying a single server.


6-9

NoteIgnore 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.

c. Verify that there are no system status alerts.


6-10

7-1

Chapter 7

Integrating Active Directory


7-2

Integrating Active DirectoryAfter successfully preforming the migration, Active Directory integration settings mustbe reset to connect to the Active Directory server. SafeSync 2.0 Active Directorysettings will not work properly for SafeSync 2.1

Procedure

1. Click Enable Active Directory integration.

2. Reset Active Directory Integration settings as required and click Save.


7-3

When you change any Active Directory server settings, you need to purge existingActive Directory accounts from the SafeSync database.


7-4

3. If you provided new Active Directory settings in Step 2, click Purge existing ADuser accounts from the SafeSync database.

4. Add new Active Directory user accounts.

After configuring Active Directory Integration settings, subscribe to the ActiveDirectory groups that will use SafeSync.


7-5

8-1

Chapter 8

Error Messages


8-2

Pre-installation Migration Error MessagesIf you encounter any of the following error messages, troubleshoot the SafeSync 2.0installation or report the issue to the Trend Micro support team.

ERROR MESSAGE INFORMATION

CheckingEnvironment

The minimum system requirements are not met.

Failed to stopApache2 service

Unable to stop the Apache2 service before migration

Failed to backupMySQL

Unable to back up SafeSync 2.0 database before migration

Failed to stopservices

Unable to stop SafeSync 2.0 services before migration

Failed to backupfiles

Unable to backup SafeSync 2.0 system files before migration

Migration Error MessagesIf the following messages appear during migration, the migration may need to be rolledback 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 thirdparty packages

Unable to install SafeSync 2.1 packages

Failed to runCustom Script

Unable to install SafeSync 2.1 configuration files

Date post:	29-Sep-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Trend Micro Incorporated reserves the right to make changes to … · 2013. 12. 5. · Trend...

Documents