Cisco Headend System Release 2.5 Installation Guide

Page of 280
1-10 
SR 2.5 and SR 3.5 UniPack Pre-Upgrade Procedures 
78-738190-01 Rev B 
Examine Key Files 
Introduction 
The scripts contained on the UniPack are designed to back up the key files most 
likely to be found on the DNCS. Some sites, however, include special key files that 
are unique to that site, only. As part of the backup, the upgrade scripts ask if you 
have any special files that you want to add to the list of files to be backed up. If you 
answer yes, the system offers you an opportunity to type in the directory path and 
name of any special files you want to back up. 
You can save a lot of time if you spend a few minutes identifying those special files 
now.  
Identify Special Files to be Backed Up 
On a sheet of paper, create a list of special key files that you will back up. Use the 
following guidelines when you create the list: 
• 
Write down the home directories of all user accounts.  
• 
Make a list of all custom scripts that your system uses. 
• 
Review all system cron files and write down any special cron files that you want to 
retain after the upgrade. 
Notes:   
− 
Some of your special cron files may reference custom scripts. Be certain to 
include those custom scripts on any list of special cron files you want backed up. 
− 
Be aware that there is a system limitation of 2 GB of special files that can be 
backed up on an Enterprise 250 server. 
− 
Contact Cisco Services if you are unsure of what cron files you need to back up 
separately. 
Include These Files 
Be sure to include these files when you identify special files to back up: 
• 
All the files in the /dvs/dncs/tmp/dhctStatus2 directory 
Note:  This directory contains the most recent 8 days of DHCT polling data. 
• 
The /dvs/dncs/tmp/signonCount.out file 
Note:  This file is the most recent logfile associated with the signonCount utility. 
• 
The output from the most recent Doctor report.