Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle (5900-1504, April 2011)

■ It is not necessary to use the same IO method at the primary and the remote
sites. However if you need the same application performance at the remote
site you may want to use same IO method at remote site.
■ There is no need to run SFDB commands qio_getdbfiles and qio_convertdbfiles
because the Quick IO files are replicated.
Best practices for using ODM or Quick IO with Oracle:
■ Make sure you use same version of Oracle at the primary and the remote site.
■ Make sure you enable ODM by linking the proper ODM library at the remote
site.
■ Quick IO files will be replicated as Quick IO files at the remote site and hence
no extra configuration is required. However, if you are using Cached Quick IO,
and you would like to use Cached Quick IO at the remote site, then you need
to change the mount properties using the qioadmin command and also need
to copy the /etc/vx/qioadmin file from the primary to the remote.
Using Storage Foundation for Databases (SFDB) tools
in a VVR environment
The following procedures describe the additional steps required to use SFDB tools
in a VVR environment.
■ Adding a virtual hostname
■ Using existing Database Storage Checkpoints at the primary site after the DR
switchover
■ Creating new Database Storage Checkpoints at the remote site
■ Using Database FlashSnap with VVR replication
■ Using SmartTier for Oracle with VVR replication
For SFDB commands to work in general in a site replicated with VVR, the following
steps must be performed.
To run SFDB commands in a VVR environment
1
Stop VVR replication.
2
Run fsck for all database volumes on the replicated site.
3
Mount the database volume file systems.
4
As Oracle user, run the dbed_update to either update or create the SFDB
repository, depending on your use case.
Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment
Using Storage Foundation for Databases (SFDB) tools in a VVR environment
284