4-20
Cisco ONS 15310-MA SDH Reference Manual, Release 9.1 and Release 9.2
78-19417-01
Chapter 4 Cisco Transport Controller Operation
Database Backup
From the node view, select a card and right-click to open a menu with the hard-reset and soft-reset
commands. A card must be in the Out-of-Service and Management, Maintenance
(locked-enabled,maintenance) service state before you can perform a hard reset.
4.10 Database Backup
You can store a back-up version of the database on the workstation running CTC. This operation should
be part of a regular ONS 15310-MA SDH maintenance program performed at approximately weekly
intervals and should also be completed when preparing an ONS 15310-MA SDH for a pending natural
disaster, such as a flood.
A database backup may be restored in two ways, partial or complete. A partial database restore operation
restores only the provisioning data. A complete database restore operation restores both system and
provisioning data. For more information on restore database, refer to the Cisco ONS 15310-MA SDH
Procedure Guide.
Note The following parameters are not backed up and restored: node name, IP address, mask and gateway, and
Internet Inter-ORB Protocol (IIOP) port. If you change the node name and then restore a backed up
database with a different node name, the circuits will map to the new node name. Cisco recommends
keeping a record of the old and new node names.
4.11 Software Revert
When you click the Activate button after a software upgrade, the 15310E-CTX-K9 copies the current
working database and saves it in a reserved location in the 15310E-CTX-K9 flash memory. If you later
need to revert to the original working software load from the protect software load, the saved database
installs automatically. You do not need to restore the database manually or recreate circuits.
The revert feature is useful if a maintenance window closes while you are upgrading CTC software. You
can revert to the standby software load without losing traffic. When the next maintenance window opens,
complete the upgrade and activate the new software load.
Circuits that were created and provisioning that was performed after a software load is activated
(upgraded to a higher release) do not reinstate with a revert. The database configuration at the time of
activation is reinstated after a revert. This does not apply to maintenance reverts (for example 8.0.1 to
8.0.0), because maintenance releases use the same database.