11.11.2012 Views

HP Systems Insight Manager 7.0 Command Line Guide

HP Systems Insight Manager 7.0 Command Line Guide

HP Systems Insight Manager 7.0 Command Line Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Return values<br />

4. All Jobs and tasks must be completed. Ensure there are no running discovery, identification<br />

or deployment tasks by viewing the task list in <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> GUI.<br />

5. Determine if enough disk space is available on the server. The required disk space is dependent<br />

on the size of the database.<br />

No return value.<br />

Note: This tool continues even if an <strong>HP</strong> <strong>Insight</strong> Control software fails during export.<br />

Supported Platforms<br />

Post Export<br />

Examples<br />

Author<br />

All versions of <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> supported Windows operating system.<br />

All versions of <strong>Systems</strong> <strong>Insight</strong> <strong>Manager</strong> supported SQL server local or remote database.<br />

Disable the CMS on the source server.<br />

Example 1<br />

To export data without specifying file name and password.<br />

mxexport<br />

Example 3<br />

To export a data by specifying a password, enter<br />

mxexport[-p d&e128Pa ]<br />

Example 4<br />

To export a data by specifying a filename, enter<br />

mxexport[-f c:\data\Products.zip ]<br />

Example 5<br />

To export a data by specifying a filename and a password, enter<br />

mxexport[-f c:\data\Products.zip -p d&128Pa ]<br />

mxexport was developed by the Hewlett-Packard Company.<br />

Debug Settings<br />

See Also<br />

By default, the debug log is disabled for migration. To turn on the debug log, open the file<br />

migration.props under [<strong>HP</strong>SIM]\config\debugsettings, and modify the value of the<br />

property GlobalEnable to true and set the log level to 20 or above for finest logging. This property<br />

file will be created on the first run of export of import operation. The debug log file will be created<br />

under [<strong>HP</strong>SIM]\logs with name migration_log4j.log. A backup log file will be created<br />

with name migration_log4j_backup.log.<br />

mxexport(1M)<br />

44 <strong>Command</strong> descriptions

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!