About SCC Appliance Operations : SCC backups and high availability
  
SCC backups and high availability
The SCC can back up its own configuration, appliance snapshots, and statistics to an external file server over NFS, SSH, or CIFS. Choose Administration > Maintenance: External Backup and configure the external file server to use for backup.
You can also use the external backup functionality to migrate data and configuration settings from one SCC to another. For details, go to Knowledge Base article S14439.
In SCC 9.2 and later, you can use a public security key associated with the user instead of a password. Configuring external backups using a public key eliminates the need for password authentication. You can generate a 2048-bit encryption key from the SCC Management Console and then cut and paste the key to your home directory target machine, for example, /u/test/.ssh/authorized_keys.
To restore an SCC from an external backup, choose Administration > Maintenance: External Backup and select a restore type from the Backup Operation.
If you want to restore the SCC management IP addresses with those from the external backup configuration, select Restore Primary and Aux network interfaces. This selection is useful if the SCC you want to restore is located in the same data center and on the same subnet as the original SCC.
For details on the SCC external backup process, see the SteelCentral Controller for SteelHead User Guide.
You can maintain a second SCC offline as a cold, standby device. If the primary SCC fails and is no longer available, then you can power on the second SCC and configure it through a restore operation from the external backup configuration and data. You can manage all appliances with one SCC.
The SCC doesn’t support true active-active high availability failover. If you use SCC-VE, you can restore a failed host with VMware high-availability features such as vMotion and Distributed Resource Scheduler (DRS). In addition, you can routinely restore external backups from a primary SCC to a secondary SCC to keep their state consistent. This routine restoration allows for a faster switchover in the event that the primary SCC fails.
Use one of the following methods to switch the managed SteelHeads from the primary to the secondary SCC:
• Assign the primary IP address of the primary SCC to the secondary SCC. If the secondary SCC was restored from an external backup of the primary SCC, select Restore Primary and Aux network interfaces. The secondary SCC has the list of managed appliances from the external backup.
• If you’re using automatic registration, update the SCC hostname in the DNS accordingly. The default SCC hostname configured in SteelHeads is riverbedcmc.
• Use the cmc hostname and scc hostname commands on each managed SteelHead to set it to the correct SCC.
Multiple SCCs can’t manage the same SteelHead. When performing a full restore on an SCC on warm standby, there’s potential risk that the standby SCC will take over the management for some SteelHead if there’s a temporary network disruption to the active (primary) SCC connectivity.
Each SCC requires its own set of licenses. You can’t share licenses among difference SCC appliances.