Cisco Headend System Release 2.7 Installation Guide
Perform a Disaster Recovery Full Sync
4023737 Rev C
173
13 On the Active DNCS, log in to monitor the backup log file, abServer.log, as
follows:
cd /dvs/dncs/tmp
tail -f abServer.log
Note: The log file should be indicate that the Full Sync is performing a tar of all
of the system and DBDS Key files. It will then proceed to backing up the Active
DNCS database.
cd /dvs/dncs/tmp
tail -f abServer.log
Note: The log file should be indicate that the Full Sync is performing a tar of all
of the system and DBDS Key files. It will then proceed to backing up the Active
DNCS database.
14 The next major Full Sync task is to restore the DNCS database and key files that
were backed up in the preceding steps to the Inactive DNCS. (This is represented
as the "abRestore" step in the Child Jobs listing of the Full Sync steps.) The DNCS
processes on the Inactive DNCS will be stopped.
as the "abRestore" step in the Child Jobs listing of the Full Sync steps.) The DNCS
processes on the Inactive DNCS will be stopped.
15 On the Inactive DNCS, log in to monitor the restore log file, abServer.log, as
follows:
cd /dvs/dncs/tmp
tail -f abServer.log
Note: The log file should indicate that the Full Sync is extracting the key files to
the Inactive DNCS. It will then proceed to restoring the DNCS database that was
backed up in the preceding steps to the Inactive DNCS.
cd /dvs/dncs/tmp
tail -f abServer.log
Note: The log file should indicate that the Full Sync is extracting the key files to
the Inactive DNCS. It will then proceed to restoring the DNCS database that was
backed up in the preceding steps to the Inactive DNCS.
16 The next major Full Sync task is the restart of the Inactive DNCS and App Server
processes. (This is represented as the "restartDNCS" and "restartAPPS" steps,
respectively, in the Child Jobs listing of the Full Sync steps.) You will want to
monitor the restart of the DNCS and App Server processes to ensure that all
necessary processes are restarted on both Inactive servers.
respectively, in the Child Jobs listing of the Full Sync steps.) You will want to
monitor the restart of the DNCS and App Server processes to ensure that all
necessary processes are restarted on both Inactive servers.
17 The next major Full Sync task is the configuration of the QAM and Netcrypt
Emulators. (This is represented as the "configQamEmulator" step in the Child
Jobs listing of the Full Sync steps.) This step determines what the routing table on
the Inactive DNCS should look like and then sets up the configuration files for
the QAMs and Netcrypts that are to be emulated.
Note: You can estimate the time it will take for the configQamEmulator step to
complete as follows:
Total number of emulated QAMs divided by 200. Use the whole number value,
i.e., the value preceding the decimal point and this is the estimated amount of
time in minutes. If the configQamEmulator step does not complete a within a
minute or two of this estimate it may be stalled/hung-up. If it is indeed stalled
you will need to kill the Full Sync process manually as follows:
On an Active MC, open a terminal/XTERM window and enter:
<PID value> = ps -ef | grep sync_dhct | awk '{print $2}'
kill -9 <PID value>
Jobs listing of the Full Sync steps.) This step determines what the routing table on
the Inactive DNCS should look like and then sets up the configuration files for
the QAMs and Netcrypts that are to be emulated.
Note: You can estimate the time it will take for the configQamEmulator step to
complete as follows:
Total number of emulated QAMs divided by 200. Use the whole number value,
i.e., the value preceding the decimal point and this is the estimated amount of
time in minutes. If the configQamEmulator step does not complete a within a
minute or two of this estimate it may be stalled/hung-up. If it is indeed stalled
you will need to kill the Full Sync process manually as follows:
On an Active MC, open a terminal/XTERM window and enter:
<PID value> = ps -ef | grep sync_dhct | awk '{print $2}'
kill -9 <PID value>