HP Insight Management 7.3 DMT White Paper

mxexport [–f <filename>] [-p <password>]
Where the parameters are listed in the following:
-f—Optional. Specifies a different filename or path for the export archive. The default file name
is Products.zip and is placed in the <SIM Install Path>\data\configdata-
export directory
-p—Optional. Enables the password to be passed in on the command line for non-interactive
operations such as a script. This is the password that will be used to encrypt the exported file,
Products.zip. If –p is not specified, the user is prompted to enter the password in a secure
fashion. HP recommends not specifying the password on the command line.
The password must meet the following requirements:
• It must be 8 or more characters long.
• It should be alphanumeric, but not be your domain password.
• It should not contain any special characters.
Example
mxexport –f c:\export.zip –p somepassword
For more details refer to Step 9: Running the export utility on the source CMS.
Import
The import command-line (CLI) command and syntax is:
mximport [–f <filename>] [-p <password>] [-v <cluster IP>] [-n
<cluster name>]
–v—Mandatory. Used to specify the cluster IP, also known as the MSCS cluster virtual server IP
address of the target CMS.
–n—Mandatory. Used to specify the cluster name/host name, also known as the MSCS cluster
virtual server name of the target CMS. If cluster name/host name is not available, then do not
use the cluster IP parameter.
–h—Mandatory. Used to specify the FQDN of source HP SIM virtual network name.
–t— Mandatory. Used to specify the FQDN of target HP SIM virtual network name
-r—Mandatory. Used to specify the cluster CMS has a remote database server.
Cluster CMS example
Use the following CLI command to import data to Cluster CMS setup::
mximport -f<filename> –p <password> –v <cluster cms IP> -n <cluster cms name> -h <Source HP
SIM Virtual Network Name> -t <Target HP SIM Virtual Network Name>
Cluster CMS with remote database example
Use the following CLI command to import data to Cluster CMS setup with remote DB: :
58