Copyright © 2010 Caringo, Inc.All rights reserved 19Version 2.0December 2010a backup set from the restored manifest list. The primary's backup manifest must have at least2 backups in it prior to being used for failover. To assist with this transition, the secondary CSNperiodically pulls the primary's Backup Manifest UUID via the privileged SSH channel and storesit in the following location on the secondary: /etc/caringo/csn/primary-manifest.txt. Atimestamp on this file will notate the last time it was updated.To restore a manifest, click the 'Change Manifest' button at the top of the backup interface. Thiswill bring up a entry box where the UUID you would like to restore can be entered. The enteredUUID must be for a valid backup manifest created by the backup utility. If restoring a manifest ona machine that has an existing manifest and associated backups, admins must be aware that thebackup list will be completely overwritten when the entered manifest is restored.Administrators should be aware that the secondary will effectively take on the identify of the primarywhen the manifest and a selected backup within it are restored.NoteDemotion of a Secondary CSN's backup set onto a Primary CSN is not supported.Failover should only be done when the Primary is not expected to return to service soonenough for the environment's needs. A complete software rebuild of the original Primaryto reconfigure it as a Secondary will be necessary before returning it to service after aSecondary has taken over its role.3.5.5.1. Failover Without DX StorageIf the failure or demotion of the Primary CSN coincides with an outage of the DX Storage cluster,you will be unable to pull the Primary's Backup Manifest UUID from the cluster to restore it ontothe Secondary. In this scenario, an administrator can manually restore the Primary CSN's lastrecorded backup set, which is updated hourly on the Secondary CSN if it has changed. Thefollowing command will restore the Primary's backup set onto the Secondary, effectively makingthe Secondary assume the role of the Primary CSN. The script should only be performed from theSecondary CSN with both the Primary CSN and the DX Storage cluster offline:/opt/caringo/csn/bin/failover_without_castorThe script will restart the Secondary CSN after the Primary's configuration has been restored.