Cisco Headend System Release 2.7
Preserving Your Previous Configuration
78-745238-01 Rev D
57
Preserving Your Previous Configuration
Important: If you are upgrading and you need to preserve the ability to roll back the
Services Portal to a previous version, you must copy and rename the config.dat file
to prevent the new installation from overwriting the earlier version's configuration
parameters. To do this, complete the following procedure before you begin the
upgrade to Services Portal 3.0.
1 Open an xterm window on the DNCS.
2 Type cd /dvs/appFiles/ServicesPortal/data and press Enter. The
1 Open an xterm window on the DNCS.
2 Type cd /dvs/appFiles/ServicesPortal/data and press Enter. The
/dvs/appFiles/ServicesPortal/data directory becomes the working directory.
3 Type cp -p config.dat config.vXX (where XX is your current version number of
the Services Portal, before upgrading) and press Enter. This copies, renames, and
date stamps the configuration file so that you keep a copy of the original
config.dat file.
Example: If you are upgrading from Services Portal 2.0, copy the configuration
Example: If you are upgrading from Services Portal 2.0, copy the configuration
file as config.v20. Type the following command and press Enter:
cp -p config.dat config.v20
cp -p config.dat config.v20
4 Proceed with the upgrade.
If you need to roll the version back, rename the file back to its original name
If you need to roll the version back, rename the file back to its original name
(config.dat) after you roll back the version to preserve your configuration of the
earlier Services Portal version. Refer to Rolling Back to a Previous Version (on page
141) for more information.
Important: Keep the installation CD of the previous version of Services Portal. This
Important: Keep the installation CD of the previous version of Services Portal. This
will help if you ever need to roll back the version.