Archiving and restoring the server is the most complex—and
the most difficult—way to back up and restore databases. Therefore,
avoid using the server archive and restore commands unless you are
familiar with database logging techniques and neither of the methods
discussed previously is practicable in your environment. Because the
administrative complexities of this backup method are considerable,
it might be more cost effective for you to invest in hardware solutions
for high availability, such as disk mirrors or other RAID capabilities,
and to use one of the other backup methods to protect against complete
system failure and satisfy other backup requirements.
A server archive creates an archive (servername)
file containing only the metadata for the server databases, instead
of producing a pack file that contains the file system data and the
metadata or a dump file that contains metadata for a single database.
The only significant advantage to server archive is that it enables
incremental or even continuous online backup of the metadata.
You cannot use a server archive to upgrade to a new release of Rational® Synergy.
Archive your database servers to help prevent unexpected loss of
data due to abnormal circumstances. Some examples of abnormal circumstances
include:
- Disk failure
- Machine failure
- Software failure, including system and application software packages
- User error, such as a user accidentally deleting a project
Back
up databases using the ccmdb backup command. Archive
a database only when using the ccmdb backup command
is not possible or practical because of the database size.
For
more information, see:
ccmdb backup
ccmdb backup
ccmdb backup