Use the following steps to migrate customizations on remote hosts:
1. Prepare to archive the customizations made in the old installation into a tar or zip archive by copying the following files:
• Perl packages: Copy migrateperlpkg.zip from the BASEDIR/smarts/perl directory in the new installation to the BASEDIR/smarts/local directory of the old installation.
For Linux and CentOS, use the unzip migrateperlpkg.zip command, and on Windows use the WinZip software to extract the contents in the zipped file to the BASEDIR/smarts/local directory.
• sm_migrate.pl utility: Copy this file from the BASEDIR/smarts/bin directory of the new installation to the BASEDIR/smarts/bin directory of your old installation.
2. Go to the BASEDIR/smarts/bin directory of your old installation and enter the following command on one line to generate an archive of the customizations:
sm_perl sm_migrate.pl --old=<BASEDIR>/smarts (old installation) --archive=<BASEDIR>/smarts/<tar or zip file to contain
customizations> ----sitemod==<BASEDIR>\smarts\local1;
=<BASEDIR>\smarts\local2
It is recommended to save the archive with .zip extension if you are installing the 9.4.1 product on a Windows platform and .tar extension if you are installing the 9.4.1 product on Linux and CentOS platforms.
For example:
IP Manager c:\InCharge812\IP\smarts\bin>sm_perl sm_migrate.pl --old=c:\InCharge812\IP\smarts
--archive=c:\InCharge812\IP\smarts\backup.zip
--sitemod=c:\InCharge812\IP\smarts\local1;c:\InCharge812\IP\
smarts\local2
Service Assurance Manager
c:\InCharge\SAM\smarts\bin>sm_perl sm_migrate.pl --old=c:\InCharge\SAM\smarts
--archive=c:\InCharge\SAM\smarts\backup.tar
--sitemod=c:\InCharge\SAM\smarts\local1;c:\InCharge\SAM\
smarts\local2
MPLS Manager c:\InCharge40\MPLS\smarts\bin>sm_perl sm_migrate.pl --old=c:\InCharge40\MPLS\smarts
--archive=c:\InCharge40\MPLS\smarts\backup.zip
--sitemod=c:\InCharge40\MPLS\smarts\local1;c:\InCharge40\MPLS\
smarts\local2
Server Manager c:\InCharge\ESM\smarts\bin>sm_perl sm_migrate.pl --old=c:\InCharge\ESM\smarts
--archive=c:\InCharge\ESM\smarts\backup.tar
--sitemod=c:\InCharge\ESM\smarts\local1;c:\InCharge\ESM\smarts\
local2
Customization migration procedures 85
The utility carries out the following functions:
• Verifies the presence of an existing installation in the specified directory.
• Determines the files that must be copied.
• Lists the files that were modified by you. The utility skips files that were introduced by the patch but not modified by you.
• Archives the backup directory into the specified tar or zip archive.
3. Transfer the tar or zip archive that is created in step 2 to the BASEDIR/smarts directory on the host with the 9.4.1 installation.
4. Go to the BASEDIR/smarts/bin directory of your new installation and enter the following command on one line to migrate the customizations from the old installation to your new installation:
sm_perl sm_migrate.pl --new=<BASEDIR>/smarts (new installation) --archive=<BASEDIR>/smarts/<tar or zip file that contains customizations>
For example:
IP Manager c:\InCharge90\IP\smarts\bin>sm_perl sm_migrate.pl --archive=c:\InCharge90\IP\smarts\backup.zip
MPLS Manager c:\InCharge90\MPLS\smarts\bin>sm_perl sm_migrate.pl --archive=c:\InCharge90\MPLS\smarts\backup.zip --new=c:\InCharge90\MPLS\smarts
Server Manager c:\InCharge\ESM\smarts\bin>sm_perl sm_migrate.pl --archive=c:\InCharge\ESM\smarts\backup.tar --new=c:\InCharge\ESM\smarts
Network Protocol Manager
c:\InCharge\NPM\smarts\bin>sm_perl sm_migrate.pl --archive=c:\InCharge\NPM\smarts\backup.tar --new=c:\InCharge\NPM\smarts
Optical Transport Manager
c:\InCharge\OTM\smarts\bin>sm_perl sm_migrate.pl --archive=c:\InCharge\OTM\smarts\backup.tar --new=c:\InCharge\OTM\smarts
VoIP Availability Manager
c:\InCharge\VoIP\smarts\bin>sm_perl sm_migrate.pl --archive=c:\InCharge\VoIP\smarts\backup.tar --new=c:\InCharge\VoIP\smarts
In a Windows environment, you may notice that it takes a longer time to extract the sm_migrate.pl utility and carry out a migration. This behavior is expected and hence do not stop the migration process.
The utility completes the following steps:
• Verifies the presence of the new installation in the specified directory and the existence of the specified tar or zip archive.
• Reads the tar or zip archive and determines the files that must be copied.
• Copies the files from the tar or zip archive to a backup directory in BASEDIR/smarts/.migrate.bkp.<old_version>.
• Creates <BASEDIR>/smarts/.rollback_<version_timestamp> directory
• Lists the files that were modified by you.
5. Press y or any other key to start the file merge utility (sm_merge), and then press Enter. The sm_merge utility is invoked individually for each of the files that may require a three-way merge. (“Three-way merge utility” on page 92 provides details.) Once the utility completes merging the files, a message is displayed that indicates successful completion of the process.
or
Press n to skip the invocation of the sm_merge utility.
6. Review the files (merged, auto-merged and .conflict) after the migration is over. Take appropriate actions as mentioned in the “User Action” column in “Custom file migration use cases” on page 89.
7. Press y or any other key to copy security configuration files, and then press Enter. This will copy the security configuration files from .migrate.bkp.<version>/conf to local/conf of the new installation.
or
Press n to skip the copying of security configuration files.
Customization migration procedures 87