Use the mount and unmount commands to:
More easily package proprietary databases; for example, as data files instead of as SQL scripts. The associated actions necessary for running these SQL scripts, such as device and database setup, are eliminated.
Move 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.
Copy databases without a shutting down Adaptive Server. When you copy a database from the command line, you must operate outside of Adaptive Server, and use commands like the UNIX dd or ftp to create a byte-for-byte copy of all pages in a set of one or more databases.
Run mount and unmount from the isql prompt: the primary Adaptive Server is the source, and the secondary Adaptive Server is the destination. quiesce database also allows a single secondary Adaptive Server to act as standby for databases from multiple primaries, since databases from multiple sources can be copied to a single destination.
To unmount, and then re-mount, a database are:
Use unmount to remove a database and its devices from a server. A manifest file is created for the database 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. See “Manifest file”.
Copy or move the database onto the destination Adaptive Server.
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 restarting the server.
See the Reference Manual: Commands for complete documentation of mount and unmount database.
mount database and unmount
database are supported in the Cluster Edition. These commands
may be aborted if an instance failover recovery takes place while
you are using these commands. In this case, the user must re-issue the
command when the instance failover recovery is complete.
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.
