- Preface
- Overview of Cisco Unified Computing System
- Overview of Cisco UCS Manager
- Overview of Cisco UCS Manager GUI
- Configuring the Fabric Interconnects
- Configuring Ports and Port Channels
- Configuring Communication Services
- Configuring Authentication
- Configuring Organizations
- Configuring Role-Based Access Control
- Configuring DNS Servers
- Configuring System-Related Policies
- Managing Licenses
- Managing Virtual Interfaces
- Registering Cisco UCS Domains with Cisco UCS Central
- LAN Uplinks Manager
- VLANs
- Configuring LAN Pin Groups
- Configuring MAC Pools
- Configuring Quality of Service
- Configuring Network-Related Policies
- Configuring Upstream Disjoint Layer-2 Networks
- Configuring Named VSANs
- Configuring SAN Pin Groups
- Configuring WWN Pools
- Configuring Storage-Related Policies
- Configuring Fibre Channel Zoning
- Configuring Server-Related Pools
- Setting the Management IP Address
- Configuring Server-Related Policies
- Configuring Server Boot
- Deferring Deployment of Service Profile Updates
- Configuring Service Profiles
- Managing Power in Cisco UCS
- Managing Time Zones
- Managing the Chassis
- Managing Blade Servers
- Managing Rack-Mount Servers
- Starting the KVM Console
- CIMC Session Management
- Backing Up and Restoring the Configuration
- Recovering a Lost Password
- Backup Operations in UCS
- Backup Types
- Considerations and Recommendations for Backup Operations
- Scheduled Backups
- Import Configuration
- Import Methods
- System Restore
- Required User Role for Backup and Import Operations
- Configuring Backup Operations
- Configuring Scheduled Backups
- Configuring Import Operations
- Restoring the Configuration for a Fabric Interconnect
Backing Up and Restoring the Configuration
This chapter includes the following sections:
- Backup Operations in UCS
- Backup Types
- Considerations and Recommendations for Backup Operations
- Scheduled Backups
- Import Configuration
- Import Methods
- System Restore
- Required User Role for Backup and Import Operations
- Configuring Backup Operations
- Configuring Scheduled Backups
- Configuring Import Operations
- Restoring the Configuration for a Fabric Interconnect
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.
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.
-
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.
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.
- 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.
Scheduled Backups
You can configure policies in Cisco UCS to schedule the following types of backups:
You cannot schedule any other type of backup.
Full State Backup Policy
The full state backup policy allows you to schedule regular full state backups of a snapshot of the entire system. You can choose whether to configure the full state backup to occur on a daily, weekly, or biweekly basis.
Cisco UCS Manager maintains a maximum number of backup files on the remote server. The maxfiles parameter is used when Cisco UCS Manager is registered with Cisco UCS Central. The maxfiles parameter is user configurable on Cisco UCS Central and controls the number of backup files stored on Cisco UCS Central.
If Cisco UCS Manager is not registered with Cisco UCS Central, and the user is storing backup files on a remote backup server, the backup files are not managed by Cisco UCS Manager. The remote machine server administrator must monitor the disk usage and rotate the backup files to create space for new backup files.
All Configuration Export Policy
The all configuration backup policy allows you to schedule a regular backup and export of all system and logical configuration settings. This backup does not include passwords for locally authenticated users. You can choose whether to configure the all configuration backup to occur on a daily, weekly, or bi-weekly basis.
Cisco UCS maintains a maximum number of backup files on the remote server. When that number is exceeded, Cisco UCS overwrites the oldest backup file.
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.
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.
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.
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. |
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.
Configuring Backup Operations
Creating a Backup Operation
Obtain the backup server IPv4 or IPv6 address and authentication credentials.
Running a Backup Operation
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:
| ||
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. |
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
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.
| ||||||
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:
|
Configuring Scheduled Backups
Configuring the Full State Backup Policy
Obtain the backup server IPv4 or IPv6 address and authentication credentials.
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:
| ||||||||||||||||||||||
Step 5 | (Optional)
In the
Backup/Export Config Reminder area, complete
the following fields:
| ||||||||||||||||||||||
Step 6 | Click Save Changes. |
Configuring the All Configuration Export Policy
Obtain the backup server IPv4 or IPv6 address and authentication credentials.
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:
| ||||||||||||||||||||||
Step 5 | (Optional)
In the
Backup/Export Config Reminder area, complete
the following fields:
| ||||||||||||||||||||||
Step 6 | Click Save Changes. |
Configuring Import Operations
Creating an Import Operation
You cannot import a Full State backup file. You can import any of the following configuration files:
Collect the following information to import a configuration file:
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:
| ||||||||||||||||||||
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 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 9 | (Optional)
To view the progress of the import operation, do the following:
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:
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: |
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
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
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.
| ||||||
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:
|
Restoring the Configuration for a Fabric Interconnect
It is recommended that you 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. You can also use a full state backup to restore a system if they have the same release train. For example, you can use a full state backup taken from a system running Release 2.1(3a) to restore a system running Release 2.1(3f).
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.
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.
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: | ||||||||||||
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 | On the Express Setup page, select Restore From Backup and click Submit. | ||||||||||||
Step 8 | 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: | ||||||||||||
Step 9 | In the
Server
Information area, complete the following fields:
| ||||||||||||
Step 10 | 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. |