Dbvisit Standby - standby database creation methods

Owned by KrupeshD (Unlicensed)
Last updated: Jun 28, 2013 by Anton Els (Unlicensed)Version comment
2 min read

The following methods are available in Dbvisit Standby to create the standby database.  All three options are available via the GUI and Command Line options:

  1. Direct transfer 
    This method is using a direct transfer method to copy the primary database files to the standby server (on the fly creation) over the network.
    It is not using RMAN but is placing the primary database tablespaces in backup mode while the files are transfered to the standby server.
    This method is not recommended for large databases, but ideal for small database environments.  

    This option is available only if following two conditions are met,

    • Both primary and standby must be non-ASM 
    • All primary datafiles must not be OMF (Oracle Managed Files)

  2. Using a temporary location
    This method of using a temporary location is making use of RMAN to create a complete backup of the primary database on a file level and then transferring the complete backup from the temporary location on the primary server to the temporary location specified on the standby server over the network.  This method is making use of RMAN compressed backups and is more effective for larger environments.  
    Sufficient storage space to hold a compressed backup of the primary database should be available on both the primary and standby servers.  Once the creation of the standby is complete can these temporary backup files be removed.  This is the recommended approach and should be suited for most environments.  

  3. Transportable Media 
    This option of using Transportable Media uses a temporary location - specified by the user, to create a complete backup of the primary database.  Once the backup is complete the user will then manually transfer the complete backup (located on Transportable media) to the standby server. Transportable media is an external device such as a USB drive that is first plugged into the primary server and then manually transferred to the standby site and plugged into the standby server to complete the process. 

 

Option 1 should be chosen for smaller databases.
Option 2 should be chosen for larger databases.
Option 3 should be chosen for very large databases or slow networks.
Option 2 and 3 will require adequate space on the primary server to make a (compressed) copy of the database files.