The mount and unmount commands make it possible to transport databases from a source Adaptive Server to a destination Adaptive Server.
The key benefits of the mount and unmount commands are:
The copy operation provided by the quiesce and mount commands makes it possible to package proprietary databases more easily; for example, data files instead of SQL scripts. The associated actions necessary for running these SQL scripts, such as device and database setup, are eliminated.
The quiesce database extension for mount makes it possible to copy databases without a shutdown of the Adaptive Server. The primary Adaptive Server is the source, and the secondary Adaptive Server is the destination. quiesce database also allows a single secondary to act as standby for databases from multiple primaries, since databases from multiple sources can be copied to a single destination.
The mount and unmount commands support two operations:
Copying a database
When you copy a database you must use a command outside of Adaptive Server, such as UNIX dd or ftp, to create a byte-for-byte copy of all pages in a set of one or more databases.
Moving a database
When you move a set of databases from a source Adaptive Server to a destination Adaptive Server, you are physically moving the underlying devices.
With the mount and unmount commands:
Remove a database using unmount, which removes a database and its devices from a server. A manifest file is created for the database that you are unmounting at a location you specify in the command clauses. The manifest file contains information pertinent to the database at the source Adaptive Server, such as database devices, server information, and database information. For more information see “Manifest file”.
Copy or move the database onto the destination Adaptive Server, then use mount to add the devices, attributes, and so on for the database.
Use database online to bring the database up on the destination Adaptive Server without rebooting the server.
WARNING! For every login that is allowed access to a database on the original Adaptive Server, a corresponding login for the same suid must exist at the destination Adaptive Server.
For permissions to remain unchanged, the login maps at the destination Adaptive Server must be identical to those on the source Adaptive Server.
