Database FlashSnap offers three options for creating database snapshots. The option you choose is specified in the snapplan.
create a clone database for decision-support, reporting, and testing purposes.
back up the primary database at the operating system level
With this option, the db2ed_vmsnap command will first put the database into WRITE SUSPEND mode. After db2ed_vmsnap finishes creating the snapshot, it will take the database out of WRITE SUSPEND mode. The online redo log must be included in the snapshot.
Use this option to create a "hot backup." The online_mirror option creates a mirror of the database without creating a clone database. Creating a clone database is not allowed with the online_mirror option. The mirror database can be used to restore the primary database if media failure occurs.
With this option, the db2ed_vmsnap command will first put the database into WRITE SUSPEND mode. After db2ed_vmsnap finishes creating the snapshot, it will take the database out of WRITE SUSPEND mode. The active log must not be included in the snapshot.
The offline option can be used to clone or back up a database. With this option, the database must be inactive when the snapshot is created. Because the database is inactive, it is not required to be placed into WRITE SUSPEND mode. This type of snapshot is a valid database backup. You must include all data and active transaction log space volumes used by its database in the snapshot.