Migrration Utility Sm_migrate.pl to migrate customizations from installation to installation(s)

Products

• VMware Smart Assurance

Issue/Introduction

To use sm_migrate.pl to migrate customizations from one installation to another installation, one the same host and different host.

Environment

10.1.x

Resolution

The format to use sm_migrate.pl is as following

sm_perl sm_migrate.pl <options>

 

The following are options available for use:

--new=<dir>	New Install location upto <.../smarts>.  Also -n <dir>
--old=<dir>	Old Install location upto <.../smarts>.  Also -o <dir>
--archive=<file>	Tar or Zip file containing the old files.  Also -a <file>
--upgrade	For In Place upgrade in conjunction with --new=<dir> option.  Also -u
--rollback	To roll back changes made to a new install in conjunction with --new=<dir> option.  Also -r

 

The following are Optional options:

--sitemod=<location>	This is to specify customer specific local.  It is ; separated.  Also -l
--silent	Execute silently without prompts.  Also -s
--help	Print Help Message.  Also -h

 

Examples:

./sm_perl sm_migrate.pl --old=/opt/InCharge/IP/smarts --new=/opt/InCharge2/IP/smarts --sitemods=/opt/InCharge2/IP/smarts/local;local1
./sm_perl sm_migrate.pl --upgrade --new=/opt/InCharge/IP/smarts
./sm_perl sm_migrate.pl --new=/opt/InCharge/IP/smarts --rollback

 

If you are migrating from one host to anoter host:

./sm_perl sm_migrate.pl --old=/opt/InCharge/IP/smarts --archive=InCharge.zip --sitemods=/opt/InCharge/IP/smarts/local/

 

Copy the created zip or tar file to new host then run:

./sm_perl sm_migrate.pl --archive=InCharge.zip --new=/opt/InCharge/IP/smarts/

 

It is important to note, when migratiing from one host to another host, the base directory on both host have to be the same.  No exception.

After running sm_migrate.pl, you'll need to run the merger utility (sm_merge) this is an upgrade. The sm_merge utility is invoked individually for each of the files that may require a three-way merge.  Once the utility completes merging the files, a message is displayed that indicates successful completion of the process.  Review the conflict files created and take appropriate actions.

There maybe a need to copy the security configuration files from .migrate.bkp.<version>/conf to local/conf of the new installation.  

One also should note, if there are migration of dynamic model files involved between two installations of different versions, the dynamic model files needs to be recompiled on the new installation.  

Additional Information

Additional reading regarding Migration Utilities.