Backup and Restore

Backup Operations in UCS

When you perform a backup through Cisco UCS Manager, you take a snapshot of all or part of the system configuration and export the file to a location on your network. You cannot use Cisco UCS Manager to back up data on the servers.

You can perform a backup while the system is up and running. The backup operation only saves information from the management plane. It does not have any impact on the server or network traffic.

Considerations and Recommendations for Backup Operations

Before you create a backup operation, consider the following:

Backup Locations

The backup location is the destination or folder on the network where you want Cisco UCS Manager to export the backup file. You can maintain only one backup operation for each location where you plan to save a backup file.

Potential to Overwrite Backup Files

If you rerun a backup operation without changing the filename, Cisco UCS Manager overwrites the existing file on the server. To avoid overwriting existing backup files, change the filename in the backup operation or copy the existing file to another location.

Multiple Types of Backups

You can run and export more than one type of backup to the same location. Change the backup type before you rerun the backup operation. We recommend that you change the filename for easier identification and to avoid overwriting the existing backup file.

Scheduled Backups

You can create a backup operation in advance and leave the admin state disabled, until you are ready to run the backup. Cisco UCS Manager does not run the backup operation, save, or export the configuration file until you set the admin state of the backup operation to enabled.

Incremental Backups

You cannot perform incremental backups.

Encryption of Full State Backups

Full state backups are encrypted so that passwords and other sensitive information are not exported as clear text.

Backups from Cisco UCS Manager

Port configurations that include global VLANs and VSANs are not restored when you do an all-config backup in Cisco UCS Manager. Reconfigure the ports from Cisco UCS Central.

FSM Tasks for Backup Policy and Configuration Export Policy

When configuring both Backup Policy and Config Export Policy on the Policy Backup & Export tab and using the same hostname for both policies, Cisco UCS Manager will create only one Backup Operation in the Backup Configuration page to run both tasks. Each policy run will not have a separate FSM task.

To see a separate FSM task for each policy, you can create a hostname alias in your DNS server to point to the same FTP/TFTP/SCP/SFTP server. Then you can use one hostname for the Backup Policy and another hostname for the Config Export Policy.

Password Encryption Key for Backup Configuration Files

Beginning with release 4.2(3d), Cisco UCS Manager introduces Password Encryption Key to enhance security for backup configuration files.

You must set Password Encryption Key in order to create backup configuration files and also to import the backup files. Cisco UCS Manager release 4.2(3d) and later do not allow you to create backup configuration files or import backup configuration files without setting the Password Encryption Key. If the Password Encryption Key is not set, following error is displayed while creating a backup configuration file:

Backup/Export operation requires Password Encryption Key to be set, please refer to Cisco UCS Manager Administration Guide to set the Password Encryption key.

You cannot import a backup configuration file created from Cisco UCS Manager release 4.2(3d) and later into an earlier release. But, you can import a backup configuration file created from an earlier release to Cisco UCS Manager release 4.2(3d) and later with or without a Password Encryption Key.

Required User Role for Backup and Import Operations

You must have a user account that includes the admin role to create and run backup and import operations.

Creating a Backup Operation

Before you begin

Obtain the backup server IPv4 or IPv6 address and authentication credentials.

Beginning with release 4.2(3d), Cisco UCS Manager introduces Password Encryption Key to enhance security for backup configuration files.

You must set Password Encryption Key in order to create backup configuration files and also to import the backup files. Cisco UCS Manager release 4.2(3d) and later do not allow you to create backup configuration files or import backup configuration files without setting the Password Encryption Key. If the Password Encryption Key is not set, following error is displayed while creating a backup configuration file:

Backup/Export operation requires Password Encryption Key to be set, please refer to Cisco UCS Manager Administration Guide to set the Password Encryption key.

You cannot import a backup configuration file created from Cisco UCS Manager release 4.2(3d) and later into an earlier release. But, you can import a backup configuration file created from an earlier release to Cisco UCS Manager release 4.2(3d) and later with or without a Password Encryption Key.

For more information on how to set Password Encryption Key, see Setting Password Encryption Key for Locally Authenticated Users.

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Backup Configuration.

Step 5

In the Backup Configuration dialog box, click Create Backup Operation.

Step 6

In the Create Backup Operation dialog box, complete the following fields:

Name Description

Admin State field

This can be one of the following:

  • Enabled—Cisco UCS Manager runs the backup operation as soon as you click OK.

  • Disabled—Cisco UCS Manager does not run the backup operation when you click OK. If you select this option, all fields in the dialog box remain visible. However, you must manually run the backup from the Backup Configuration dialog box.

Type field

The information saved in the backup configuration file. This can be one of the following:

  • Full state—A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import.

    Note

     

    You can only use a full state backup file to restore a system that is running the same version as the system from which the backup file was exported. It is also important that the bundles from which the backup was taken remain present in the Cisco UCS Manager and should not be deleted.

  • All configuration—An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. This file does not include passwords for locally authenticated users.

  • System configuration—An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.

  • Logical configuration—An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.

Preserve Identities check box

This checkbox remains selected for All Configuration and System Configuration type of backup operation, and provides the following functionality:
  • All Configuration—The backup file preserves all identities derived from pools, including vHBAs, WWPNs, WWNN, vNICs, MACs and UUIDs. Also, the identities for Chassis, FEX, Rack Servers, and user labels for Chassis, FEX, Rack Servers, IOMs and Blade Servers are preserved.

    Note

     

    If this check box is not selected the identities will be reassigned and user labels will be lost after a restore.

  • System Configuration—The backup file preserves identities for Chassis, FEX, Rack Servers, and user labels for Chassis, FEX, Rack Servers, IOMs and Blade Servers.

    Note

     

    If this check box is not selected the identities will be reassigned and user labels will be lost after a restore.

If this checkbox is selected for Logical Configuration type of backup operation, the backup file preserves all identities derived from pools, including vHBAs, WWPNs, WWNN, vNICs, MACs and UUIDs.

Note

 

If this check box is not selected the identities will be reassigned and user labels will be lost after a restore.

Location of the Backup File field

Where the backup file should be saved. This can be one of the following:

  • Remote File System—The backup XML file is saved to a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system.

  • Local File System—The backup XML file is saved locally.

    HTML-based Cisco UCS Manager GUI displays the Filename field. Enter a name for the backup file in <filename>.xml format. The file is downloaded and saved to a location depending on your browser settings.

Protocol field

The protocol to use when communicating with the remote server. This can be one of the following:

  • FTP

  • TFTP

  • SCP

  • SFTP

  • USB A—The USB drive inserted into fabric interconnect A.

    This option is only available for certain system configurations.

  • USB B—The USB drive inserted into fabric interconnect B.

    This option is only available for certain system configurations.

Hostname field

The hostname, IPv4 or IPv6 address of the location where the backup file is stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network.

Note

 

If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local, configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.

Remote File field

The full path to the backup configuration file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file.

User field

The username the system should use to log into the remote server. This field does not apply if the protocol is TFTP.

Password field

The password for the remote server username. This field does not apply if the protocol is TFTP.

Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the backup operation immediately.

Step 7

Click OK.

Step 8

If Cisco UCS Manager displays a confirmation dialog box, click OK.

If you set the Admin State field to enabled, Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box.

Step 9

(Optional) To view the progress of the backup operation, do the following:

  1. If the operation does not display in the Properties area, click the operation in the Backup Operations table.

  2. In the Properties area, click the down arrows on the FSM Details bar.

The FSM Details area expands and displays the operation status.

Step 10

Click OK to close the Backup Configuration dialog box.

The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box.

Running a Backup Operation

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Backup Configuration.

Step 5

In the Backup Operations table of the Backup Configuration dialog box, click the backup operation that you want to run.

The details of the selected backup operation display in the Properties area.

Step 6

In the Properties area, complete the following fields:

  1. In the Admin State field, click the Enabled radio button.

  2. For all protocols except TFTP, enter the password for the username in the Password field.

  3. (Optional) Change the content of the other available fields.

Note

 
If you change other fields -- such as resetting a scheduled backup from weekly to daily -- you must re-enter your user name and password. Otherwise, an FI backup will fail.

Step 7

Click Apply.

Cisco UCS Manager takes a snapshot of the configuration type that you selected and exports the file to the network location. The backup operation displays in the Backup Operations table in the Backup Configuration dialog box.

Step 8

(Optional) To view the progress of the backup operation, click the down arrows on the FSM Details bar.

The FSM Details area expands and displays the operation status.

Step 9

Click OK to close the Backup Configuration dialog box.

The backup operation continues to run until it is completed. To view the progress, re-open the Backup Configuration dialog box.

Modifying a Backup Operation

You can modify a backup operation to save a file of another backup type to that location or to change the filename and avoid overwriting previous backup files.


Note

You can only use a full state backup file to restore a system that is running the same version as the system from which the backup file was exported. It is also important that the bundles from which the backup was taken remain present in the Cisco UCS Manager and should not be deleted.

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Backup Configuration.

Step 5

In the Backup Operations area of the Backup Configuration dialog box, click the backup operation that you want to modify.

The details of the selected backup operation display in the Properties area. If the backup operation is in a disabled state, the fields are dimmed.

Step 6

In the Admin State field, click the enabled radio button.

Step 7

Modify the appropriate fields.

You do not have to enter the password unless you want to run the backup operation immediately.

Step 8

(Optional) If you do not want to run the backup operation immediately, click the disabled radio button in the Admin State field.

Step 9

Click OK.

Deleting One or More Backup Operations

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Backup Configuration.

Step 5

In the Backup Operations table of the Backup Configuration dialog box, click the backup operations that you want to delete.

Tip

 

You cannot click a backup operation in the table if the admin state of the operation is set to Enabled.

Step 6

Click the Delete icon in the icon bar of the Backup Operations table.

Step 7

If a confirmation dialog box displays, click Yes.

Step 8

In the Backup Configuration dialog box, click one of the following:

Option Description

Apply

Deletes the selected backup operations without closing the dialog box.

OK

Deletes the selected backup operations and closes the dialog box.

Backup Types

You can perform one or more of the following types of backups in Cisco UCS Manager and Cisco UCS Central:

  • Full state—A binary file that includes a snapshot of the entire system. You can use the file generated from this backup to restore the system during disaster recovery. This file can restore or rebuild the configuration on the original fabric interconnect, or recreate the configuration on a different fabric interconnect. You cannot use this file for an import.


    Note

    You can only use a full state backup file to restore a system that is running the same version as the system from which the backup file was exported. It is also important that the bundles from which the backup was taken remain present in the Cisco UCS Manager and should not be deleted.

  • All configuration—An XML file that includes all system and logical configuration settings. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore. This file does not include passwords for locally authenticated users.

  • System configuration—An XML file that includes all system configuration settings such as usernames, roles, and locales. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.

  • Logical configuration—An XML file that includes all logical configuration settings such as service profiles, VLANs, VSANs, pools, and policies. You can use the file generated from this backup to import these configuration settings to the original fabric interconnect or to a different fabric interconnect. You cannot use this file for a system restore.

Configuring the Full State Backup Policy

Before you begin

Obtain the backup server IPv4 or IPv6 address and authentication credentials.

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the Backup and Export Policy tab.

Step 4

In the Full State Backup Policy area, complete the following fields:

Name Description

Hostname field

The hostname, IPv4 or IPv6 address of the location where the policy backup file is stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network.

Note

 

If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local, configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.

Protocol field

The protocol to use when communicating with the remote server. This can be one of the following:

  • FTP

  • TFTP

  • SCP

  • SFTP

  • USB A—The USB drive inserted into fabric interconnect A.

    This option is only available for certain system configurations.

  • USB B—The USB drive inserted into fabric interconnect B.

    This option is only available for certain system configurations.

User field

The username the system should use to log into the remote server. This field does not apply if the protocol is TFTP.

Password field

The password for the remote server username. This field does not apply if the protocol is TFTP.

Remote File field

The full path to the policy backup file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file.

Admin State field

This can be one of the following:

  • Enabled—Cisco UCS Manager backs up all policy information using the schedule specified in the Schedule field.

  • Disabled—Cisco UCS Manager does not back up policy information.

Schedule field

The frequency with which Cisco UCS Manager backs up policy information.

Max Files field

The maximum number of backup files that Cisco UCS Manager maintains.

This value cannot be changed.

Description field

The description of the backup policy. The default description is Database Backup Policy.

Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).

Step 5

(Optional) In the Backup/Export Config Reminder area, complete the following fields:

Name Description

Admin State column

This can be one of the following:

  • Enable—Cisco UCS Manager raises a fault if a backup is not taken during the specified time period.

  • Disable—Cisco UCS Manager does not raise a fault if a backup is not taken during the specified time period.

Remind Me After (days) column

The number of days before you are reminded to take a backup. Enter an integer between 1 and 365.

The default value is 30 days.

Step 6

Click Save Changes.

Configuring the All Configuration Export Policy

Before you begin

Obtain the backup server IPv4 or IPv6 address and authentication credentials.

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the Policy Backup & Export tab.

Step 4

In the Config Export Policy area, complete the following fields:

Name Description

Hostname field

The hostname, IPv4 or IPv6 address of the location where the configuration backup file is stored. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network.

Note

 

If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local, configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.

Protocol field

The protocol to use when communicating with the remote server. This can be one of the following:

  • FTP

  • TFTP

  • SCP

  • SFTP

  • USB A—The USB drive inserted into fabric interconnect A.

    This option is only available for certain system configurations.

  • USB B—The USB drive inserted into fabric interconnect B.

    This option is only available for certain system configurations.

User field

The username the system should use to log into the remote server. This field does not apply if the protocol is TFTP.

Password field

The password for the remote server username. This field does not apply if the protocol is TFTP.

Remote File field

The full path to the backup configuration file. This field can contain the filename as well as the path. If you omit the filename, the backup procedure assigns a name to the file.

Admin State field

This can be one of the following:

  • Enabled—Cisco UCS Manager backs up all policy information using the schedule specified in the Schedule field.

  • Disabled—Cisco UCS Manager does not back up policy information.

Schedule field

The frequency with which Cisco UCS Manager backs up policy information.

Max Files field

The maximum number of configuration backup files that Cisco UCS Manager maintains.

This value cannot be changed.

Description field

The description of the configuration export policy. The default description is Configuration Export Policy.

Enter up to 256 characters. You can use any characters or spaces except ` (accent mark), \ (backslash), ^ (carat), " (double quote), = (equal sign), > (greater than), < (less than), or ' (single quote).

Step 5

(Optional) In the Backup/Export Config Reminder area, complete the following fields:

Name Description

Admin State column

This can be one of the following:

  • Enable—Cisco UCS Manager raises a fault if a backup is not taken during the specified time period.

  • Disable—Cisco UCS Manager does not raise a fault if a backup is not taken during the specified time period.

Remind Me After (days) column

The number of days before you are reminded to take a backup. Enter an integer between 1 and 365.

The default value is 30 days.

Step 6

Click Save Changes.

Import Methods

You can use one of the following methods to import and update a system configuration through Cisco UCS:

  • Merge—The information in the imported configuration file is compared with the existing configuration information. If there are conflicts, the import operation overwrites the information on the Cisco UCS domain with the information in the import configuration file.

  • Replace—The current configuration information is replaced with the information in the imported configuration file one object at a time.

Import Configuration

You can import any configuration file that was exported from Cisco UCS. The file does not need to have been exported from the same Cisco UCS.


Note

You cannot import configuration from a higher release to a lower release.

The import function is available for all configuration, system configuration, and logical configuration files. You can perform an import while the system is up and running. An import operation modifies information on the management plane only. Some modifications caused by an import operation, such as a change to a vNIC assigned to a server, can cause a server reboot or other operations that disrupt traffic.

You cannot schedule an import operation. You can, however, create an import operation in advance and leave the admin state disabled until you are ready to run the import.Cisco UCS will not run the import operation on the configuration file until you set the admin state to enabled.

You can maintain only one import operation for each location where you saved a configuration backup file.

Creating an Import Operation

You cannot import a Full State backup file. You can import any of the following configuration files:

  • All configuration

  • System configuration

  • Logical configuration

Before you begin

Collect the following information to import a configuration file:

  • Backup server IP address and authentication credentials

  • Fully-qualified name of a backup file

Beginning with release 4.2(3d), Cisco UCS Manager introduces Password Encryption Key to enhance security for backup configuration files.

You must set Password Encryption Key in order to create backup configuration files and also to import the backup files. Cisco UCS Manager release 4.2(3d) and later do not allow you to create backup configuration files or import backup configuration files without setting the Password Encryption Key.

You cannot import a backup configuration file created from Cisco UCS Manager release 4.2(3d) and later into an earlier release. But, you can import a backup configuration file created from an earlier release to Cisco UCS Manager release 4.2(3d) and later with or without a Password Encryption Key.

For more information on how to set the Password Encryption Key, see Setting Password Encryption Key for Locally Authenticated Users

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Import Configuration.

Step 5

In the Import Configuration dialog box, click Create Import Operation.

Step 6

In the Create Import Operation dialog box, complete the following fields:

Name Description

Admin State field

This can be one of the following:

  • Enabled—Cisco UCS Manager runs the import operation as soon as you click OK.

  • Disabled—Cisco UCS Manager does not run the import operation when you click OK. If you select this option, all fields in the dialog box remain visible. However, you must manually run the import from the Import Configuration dialog box.

Action field

This can be one of the following:

  • Merge—The configuration information is merged with the existing information. If there are conflicts, the system replaces the information on the current system with the information in the import configuration file.

  • Replace—The system takes each object in the import configuration file and overwrites the corresponding object in the current configuration.

Location of the Import File field

Where the backup file that you want to import is located. This can be one of the following:

  • Remote File System—The backup XML file is stored on a remote server. Cisco UCS Manager GUI displays the fields described below that allow you to specify the protocol, host, filename, username, and password for the remote system.

  • Local File System—The backup XML file is stored locally. Cisco UCS Manager GUI displays the Filename field with an associated Browse button that let you specify the name and location for the backup file to be imported.

Protocol field

The protocol to use when communicating with the remote server. This can be one of the following:

  • FTP

  • TFTP

  • SCP

  • SFTP

  • USB A—The USB drive inserted into fabric interconnect A.

    This option is only available for certain system configurations.

  • USB B—The USB drive inserted into fabric interconnect B.

    This option is only available for certain system configurations.

Hostname field

The hostname, IPv4 or IPv6 address from which the configuration file should be imported.

Note

 

If you use a hostname rather than an IPv4 or IPv6 address, you must configure a DNS server. If the Cisco UCS domain is not registered with Cisco UCS Central or DNS management is set to local, configure a DNS server in Cisco UCS Manager. If the Cisco UCS domain is registered with Cisco UCS Central and DNS management is set to global, configure a DNS server in Cisco UCS Central.

Remote File field

The name of the XML configuration file.

User field

The username the system should use to log into the remote server. This field does not apply if the protocol is TFTP.

Password field

The password for the remote server username. This field does not apply if the protocol is TFTP.

Cisco UCS Manager does not store this password. Therefore, you do not need to enter this password unless you intend to enable and run the import operation immediately.

Step 7

Click OK.

Step 8

In the confirmation dialog box, click OK.

If you set the Admin State to enabled, Cisco UCS Manager imports the configuration file from the network location. Depending on the action that you select, the information in the file merges with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box.

Step 9

(Optional) To view the progress of the import operation, do the following:

  1. If the operation does not automatically display in the Properties area, click the operation in the Import Operations table.

  2. In the Properties area, click the down arrows on the FSM Details bar.

The FSM Details area expands and displays the operation status.

Step 10

Click OK to close the Import Configuration dialog box.

The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box.

Running an Import Operation

You cannot import a Full State backup file. You can import any of the following configuration files:

  • All configuration

  • System configuration

  • Logical configuration

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Import Configuration.

Step 5

In the Import Operations table of the Import Configuration dialog box, click the operation that you want to run.

The details of the selected import operation display in the Properties area.

Step 6

In the Properties area, complete the following fields:

  1. In the Admin State field, click the Enabled radio button.

  2. For all protocols except TFTP, enter the password for the username In the Password field.

  3. (Optional) Change the content of the other available fields.

Step 7

Click Apply.

Cisco UCS Manager imports the configuration file from the network location. Depending upon which action you selected, the information in the file is either merged with the existing configuration or replaces the existing configuration. The import operation displays in the Import Operations table of the Import Configuration dialog box.

Step 8

(Optional) To view the progress of the import operation, click the down arrows on the FSM Details bar.

The FSM Details area expands and displays the operation status.

Step 9

Click OK to close the Import Configuration dialog box.

The import operation continues to run until it is completed. To view the progress, re-open the Import Configuration dialog box.

Modifying an Import Operation

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Import Configuration.

Step 5

In the Import Operations area of the Import Configuration dialog box, click the import operation that you want to modify.

The details of the selected import operation display in the Properties area. If the import operation is in a disabled state, the fields are dimmed.

Step 6

In the Admin State field, click the enabled radio button.

Step 7

Modify the appropriate fields.

You do not have to enter the password unless you want to run the import operation immediately.

Step 8

(Optional) If you do not want to run the import operation immediately, click the disabled radio button in the Admin State field.

Step 9

Click OK.

Deleting One or More Import Operations

Procedure

Step 1

In the Navigation pane, click Admin.

Step 2

Click the All node.

Step 3

In the Work pane, click the General tab.

Step 4

In the Actions area, click Import Configuration.

Step 5

In the Import Operations table of the Backup Configuration dialog box, click the import operations that you want to delete.

Tip

 

You cannot click an import operation in the table if the admin state of the operation is set to Enabled.

Step 6

Click the Delete icon in the icon bar of the Import Operations table.

Step 7

If a confirmation dialog box displays, click Yes.

Step 8

In the Import Configuration dialog box, click one of the following:

Option Description

Apply

Deletes the selected import operations without closing the dialog box.

OK

Deletes the selected import operations and closes the dialog box.

System Restore

You can use the restore function for disaster recovery.

You can restore a system configuration from any full state backup file that was exported from Cisco UCS. The file does not need to have been exported from Cisco UCS on the system that you are restoring. When restoring using a backup file that was exported from a different system, we recommend that you use a system with the same or similar system configuration and hardware, including fabric interconnects, servers, adapters, and I/O module or FEX connectivity. Mismatched hardware and system configuration can lead to the restored system not fully functioning. If there is a mismatch between the I/O module links or servers on the two systems, acknowledge the chassis and servers after the restore operation.

In Cisco UCS Manager Release 4.0(1) and later releases, if a full state backup is collected on a UCS 6200 Series Fabric Interconnect with the following unsupported features, then full state restore cannot be used to restore this file on a Cisco UCS 6400 Series Fabric Interconnect:

  • Chassis Discovery Policy and Chassis Connectivity Policy are in non port channel mode

  • Virtual Machine Management is enabled - VMware, Linux KVM, or Microsoft Hypervisor

The restore function is only available for a full state backup file. You cannot import a full state backup file. You perform a restore through the initial system setup. For more information, see the appropriate Cisco UCS Central Installation and Upgrade Guide.


Note

You can only use a full state backup file to restore a system that is running the same version as the system from which the backup file was exported. It is also important that the bundles from which the backup was taken remain present in the Cisco UCS Manager and should not be deleted.

Restoring the Configuration for a Fabric Interconnect

It is recommended to use a full state backup file to restore a system running the same version as the source system from which the backup was exported. You can use a full state backup to restore a system within the same release train. For example, you can use a backup from a system running on Cisco UCS Manager 4.1(3b) release version to restore a system on release 4.1(3m). It is also important to ensure that the bundles from which the backup was taken remain present in Cisco UCS Manager and are not deleted.

To avoid issues with VSAN or VLAN configuration, a backup should be restored on the fabric interconnect that was the primary fabric interconnect at the time of backup.

Before you begin

Collect the following information to restore the system configuration:

  • Fabric interconnect management port IPv4 address and subnet mask, or IPv6 address and prefix

  • Default gateway IPv4 or IPv6 address

  • Backup server IPv4 or IPv6 address and authentication credentials

  • Fully-qualified name of a Full State backup file


    Note

    You must have access to a Full State configuration file to perform a system restore. You cannot perform a system restore with any other type of configuration or backup file.

Procedure

Step 1

Connect to the console port.

Step 2

If the fabric interconnect is off, power on the fabric interconnect.

You will see the power on self-test message as the fabric interconnect boots.

Step 3

At the installation method prompt, enter gui.

Step 4

If the system cannot access a DHCP server, you may be prompted to enter the following information:

  • IPv4 or IPv6 address for the management port on the fabric interconnect

  • Subnet mask or prefix for the management port on the fabric interconnect

  • IPv4 or IPv6 address for the default gateway assigned to the fabric interconnect

Step 5

Copy the web link from the prompt into a web browser and go to the Cisco UCS Manager GUI launch page.

Step 6

On the launch page, select Express Setup.

Step 7

Select UCSM to continue.

Step 8

On the Express Setup page, select Restore From Backup and click Submit.

Step 9

In the Protocol area of the Cisco UCS Manager Initial Setup page, select the protocol you want to use to upload the full state backup file:

  • SCP
  • TFTP
  • FTP
  • SFTP

Step 10

In the Server Information area, complete the following fields:

Name Description

Server IP

The IPv4 or IPv6 address of the computer where the full state backup file is located. This can be a server, storage array, local drive, or any read/write media that the fabric interconnect can access through the network.

Backup File Path

The file path where the full state backup file is located, including the folder names and filename.

Note

 

You can only use a full state backup file to restore a system that is running the same version as the system from which the backup file was exported. It is also important that the bundles from which the backup was taken remain present in the Cisco UCS Manager and should not be deleted.

User ID

The username the system should use to log into the remote server. This field does not apply if the protocol is TFTP.

Password

The password for the remote server username. This field does not apply if the protocol is TFTP.

Password Decryption Key field

Beginning with release 4.2(3d), Cisco UCS Manager introduces Password Decryption Key to enhance security for backup configuration files.

Password Decryption Key should be same as mentioned in Password Encryption Key while creating the backup configuration file. Same key is set as Password Encryption Key after successful restore.

Note

 
For release 4.2(3d) and later, you can perform this procedure only with a backup configuration file created from release 4.2(3d) or later.

Step 11

Click Submit.

You can return to the console to watch the progress of the system restore.

The fabric interconnect logs in to the backup server, retrieves a copy of the specified full-state backup file, and restores the system configuration.

For a cluster configuration, you do not need to restore the secondary fabric interconnect. As soon as the secondary fabric interconnect reboots, Cisco UCS Manager synchronizes the configuration with the primary fabric interconnect.