/mcputils disaster_recovery restore network <ip-address of remote server> <tarfilename> <backup device name> Example: admin:utils disaster_recovery restore network 10.48.53.160 2017-08-18-14-45-38 linux123 drfCliMsg: WARNING! There are nodes in current production cluster but NOT present in the backup. These nodes will be removed if you restore the Publisher. If you want to keep these nodes, you will need to manually re-add them after the restore. Do you want DRS to perform a SHA-1 File Integrity Check of your backup archives y/n ?(n) : y Please enter the comma seperated features you wish to restore. Valid features for server CUCM160 are PLM,CDR_CAR,UCM:PLM,CDR_CAR,UCM Do you want to restore database from the subscriber y/n ?(n) : n drfCliMsg: Restore initiated successfully. Please run 'utils disaster_recovery status restore' command to see the status ALERT: Please restart the server(s) before performing the next restore for changes to take effect. In case of a cluster, restart the entire cluster. <p style="background-image: url('http://www.cisco.com/en/US/i/templates/note.gif'); background- repeat: no-repeat; background- position: 2px 4px; height: auto; width: auto; padding: 10px 5px 10px 35px; margin-top: 10px; margin-bottom: 10px; border-top: 1px solid #ccc; border-bottom: 1px solid #ccc; overflow-x: hidden;"><strong>Note</strong>: {If you are restoring the system to be in FIPS mode, please note that it will be enabled during this restore, but will not take effect until the next reboot..}</p> Check the restore status 3. A restore procedure could take time depends on the database size. Syntax: utils disaster_recovery status restore Example: admin:utils disaster_recovery status restore Status: SUCCESS :Restore Completed... Tar Filename: 2017-08-18-14-45-38.tar Storage Location: NETWORK Operation: restore Percentage Complete: 100 CDR_CAR CUCM160 CAR SUCCESS Fri Aug 18 15:20:15 CEST 2017 activelog/platform/drf/log/2017-08-18-15-20-01_r_cucm160_cdr_car_car.log PLM CUCM160 ELM-AGENT SUCCESS Fri Aug 18 15:24:34 CEST 2017 activelog/platform/drf/log/2017-08-18-15-20-01_r_cucm160_plm_elm-agent.log PLM CUCM160 ELM-SERVER SUCCESS Fri Aug 18 15:24:34 CEST 2017 activelog/platform/drf/log/2017-08-18-15-20-01_r_cucm160_plm_elm-server.log UCM CUCM160 BAT SUCCESS Fri Aug 18 15:27:06 CEST 2017 activelog/platform/drf/log/2017- 08-18-15-20-01_r_cucm160_ucm_bat.log UCM CUCM160 CCMPREFS SUCCESS Fri Aug 18 15:27:06 CEST 2017 activelog/platform/drf/log/2017-08-18-15-20-01_r_cucm160_ucm_ccmprefs.log UCM CUCM160 PLATFORM SUCCESS Fri Aug 18 15:27:13 CEST 2017 activelog/platform/drf/log/2017-08-18-15-20-01_r_cucm160_ucm_platform.log UCM CUCM160 TCT SUCCESS Fri Aug 18 15:32:15 CEST 2017 activelog/platform/drf/log/2017-