Import-config

Import-config-Server <Exchange_server_name>-ControlFilePath <name_of_control-file_and_path>-Section <comma_separated_list_of_section_names_to_import-AllowLocal <true | false>-ValidateAndApply <true | false>-Username <username>-Password <password>-ClusterAware <true | false>

Description

This command enables you to import the SnapManager control file that contains the server configuration information. You can import either a section of the control file, or the complete control file.

Parameters

-Server <Exchange_server_name>

Short name: svr

Specifies the name of the Exchange server to which you want to import the control file.

-ControlFilePath <name_of_control-file_and_path>

Short name: config

Specifies the location of the control file to import.

Specify -ControlFilePath with the control file name. If the control file is not in the current directory, the full file name path must be given.

-Section <comma_separated_list_of_section_names_to_import>

Short name: sect

Specifies the comma-separated list of names of sections to import.

You can import the following sections from the control file:

storage, notification, verification, report, backup, scheduledjob, snapmirrorvolume.

If you do not specify particular sections, SnapManager imports all sections in the control file.

-AllowLocal <true | false>

Short name: tolocal

Migrates the databases to the local disk.

-ValidateAndApply <true | false>

Short name: apply

This is an optional parameter. By default, the value is false, that indicates to perform only validation. If the value is set to true, it indicates to perform validation and apply it if the validation is successful.

-Username <username>

Short name: usr

Verifies the user name before creating a scheduled job.

-Password<password>

Short name: pwd

Verifies the user credentials before creating a scheduled job.

-Clusteraware <True|False>

Short form: cl

Assumes significance only when scheduling jobs in cluster configurations, by facilitating scheduling the same job in multiple cluster nodes to improve fault tolerance.

In the case of Single Copy Cluster (SCC), if a job is scheduled with -Clusteraware, the job runs only if the host in which it is scheduled is the active node of the cluster.

In the case of Cluster Continuous Replica (CCR), the processing of -Clusteraware depends on whether the host in which it is scheduled is an active or passive node and the value of -CCRActiveNode. The job runs if the host is a CCR active node and the job targets it with -CCRActiveNode as true. If the host is a CCR passive node, the job runs if the job targets the host with -CCRActiveNode false.