Veritas Storage Foundation 5.1 SP1: Storage and Availability Management for Oracle Databases HP-UX 11i v3 HP Part Number: 5900-1504 Published: April 2011 Edition: 1.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents Technical Support ............................................................................................... 4 Section 1 Storage and availability management for Oracle databases ................................................... 17 Chapter 1 Overview of Storage Foundation for Databases (SFDB) tools .................................................................... 19 About Storage Foundation for Databases (SFDB) tools for Oracle ..........
8 Contents Deploying Storage Foundation for Database (SFDB) tools in a virtualization environment ...................................................... 36 Deploying Storage Foundation for Database (SFDB) tools with SmartMove and Thin Provisioning ............................................ 36 Chapter 3 Administering Storage Foundation for Databases (SFDB) tools ....................................................................
Contents About Oracle Disk Manager ............................................................ How Oracle Disk Manager improves database performance ............ About Oracle Disk Manager and Oracle Managed Files ........................ How Oracle Disk Manager works with Oracle Managed Files .......... About Cached ODM ...................................................................... Considerations for using Cached ODM ....................................... Supported configurations ................
10 Contents Accessing regular VxFS files as Quick I/O files ................................... 91 Converting Oracle files to Quick I/O files .......................................... 92 About sparse files ......................................................................... 98 Handling Oracle temporary tablespaces and Quick I/O ........................ 99 Displaying Quick I/O status and file attributes ................................. 101 Extending a Quick I/O file .................................
Contents About Database Storage Checkpoints and Storage Rollback in SF Enterprise products .............................................................. 127 Chapter 10 Using Database FlashSnap for backup and off-host processing ..................................................................... 129 Planning to use Database FlashSnap .............................................. Selecting the snapshot mode .................................................. Selecting one or two hosts (off-host) .......
12 Contents Backing up and recovering the database using Storage Checkpoints ........................................................................ Specify the Storage Checkpoint option ..................................... Verifying a Storage Checkpoint ............................................... Backing up using a Storage Checkpoint ..................................... Recovering a database using a Storage Checkpoint ..................... Guidelines for Oracle recovery ...........................
Contents Moving files ........................................................................ Moving sub-file objects .......................................................... How SmartTier for Oracle works ................................................... How partitions change the way Oracle stores database objects .......................................................................... Database extents to file location .............................................. Statistics in Oracle ............
14 Contents Using AWR statistics to identify sub-file objects for potential relocation ..................................................................... 275 Relocating a hot database segment to a higher performance tier .............................................................................. 277 Relocating old table data to a lower cost or secondary tier ............ 278 Section 5 Deploying SFDB tools in a replicated environment ............................................................
Contents Valid HOME directory for Storage Foundation for Databases (SFDB) .......................................................................... About the vxdbd daemon ............................................................. Troubleshooting Database FlashSnap ............................................. Troubleshooting SmartTier for Oracle ............................................ Upgrading Veritas Storage Foundation for Databases (SFDB) tools from 5.0MP2 to 5.1SP1 (2003131) ..................
16 Contents Sample configuration file for Storage Foundation for Clustered File System HA .......................................................................... 318 Sample configuration file for Storage Foundation for Oracle RAC ................................................................................... 324 Appendix C Database FlashSnap status information ...................... 331 About Database FlashSnap status information .................................
Section 1 Storage and availability management for Oracle databases ■ Chapter 1. Overview of Storage Foundation for Databases (SFDB) tools ■ Chapter 2. Deploying Storage Foundation for Databases (SFDB) tools ■ Chapter 3.
18
Chapter 1 Overview of Storage Foundation for Databases (SFDB) tools This chapter includes the following topics: ■ About Storage Foundation for Databases (SFDB) tools for Oracle ■ Storage management features for Storage Foundation products About Storage Foundation for Databases (SFDB) tools for Oracle This guide documents the deployment and use of the SFDB tools with Storage Foundation and High Availability products in Oracle database environments.
20 Overview of Storage Foundation for Databases (SFDB) tools About Storage Foundation for Databases (SFDB) tools for Oracle Table 1-1 Veritas Storage Foundation database management features Feature Uses Enhanced I/O methods enable ■ To improve Oracle performance and manage system you to improve database bandwidth through an improved Application performance: Programming Interface (API) that contains advanced kernel support for file I/O, use Veritas Oracle Disk ■ Veritas Extension for Manager (ODM).
Overview of Storage Foundation for Databases (SFDB) tools About Storage Foundation for Databases (SFDB) tools for Oracle Table 1-1 Veritas Storage Foundation database management features (continued) Feature Uses Point-in-time copy features enable you to capture an instantaneous image of actively changing data: ■ ■ Database FlashSnap ■ Database Storage Checkpoints ■ ■ ■ ■ To create an online point-in-time image of a database in an Oracle environment, use the Storage Foundation Database Flashsn
22 Overview of Storage Foundation for Databases (SFDB) tools Storage management features for Storage Foundation products Storage management features for Storage Foundation products The following table lists the Veritas Storage Foundation product suites in which each advanced feature is available.
Overview of Storage Foundation for Databases (SFDB) tools Storage management features for Storage Foundation products Table 1-2 Advanced features in Storage Foundation (continued) Storage Foundation feature Product licenses which enable this feature Cached Quick I/O Storage Foundation Basic Storage Foundation Standard Storage Foundation Standard HA Storage Foundation Enterprise Storage Foundation Enterprise HA Storage Foundation Cluster File System Storage Foundation Cluster File System HA Storage Found
24 Overview of Storage Foundation for Databases (SFDB) tools Storage management features for Storage Foundation products Table 1-2 Advanced features in Storage Foundation (continued) Storage Foundation feature Product licenses which enable this feature Portable Data Containers Storage Foundation Basic Storage Foundation Standard Storage Foundation Standard HA Storage Foundation Enterprise Storage Foundation Enterprise HA Storage Foundation Cluster File System Storage Foundation Cluster File System HA S
Chapter 2 Deploying Storage Foundation for Databases (SFDB) tools This chapter includes the following topics: ■ Storage Foundation for Databases (SFDB) tools deployment options ■ Requirements for Storage Foundation for Databases (SFDB) tools ■ Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation environment ■ Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation HA environment ■ Deploying Storage Foundation for Databases (SFDB) tools in a SF Cl
26 Deploying Storage Foundation for Databases (SFDB) tools Storage Foundation for Databases (SFDB) tools deployment options ■ Deploying Storage Foundation for Database (SFDB) tools with SmartMove and Thin Provisioning Storage Foundation for Databases (SFDB) tools deployment options Storage Foundation extended storage management tools for Oracle databases are included with Enterprise licensing for the following products: ■ Storage Foundation, which supports host systems with single-instance Oracle ■ S
Deploying Storage Foundation for Databases (SFDB) tools Storage Foundation for Databases (SFDB) tools deployment options ■ sfua_db_config functionality is changed: this command is no longer needed to create a SFDB repository. The functionality of sfua_db_config is now used to set user and group access to various SFDB directories. ■ Use the dbed_update command to create a new SQLite SFDB repository. ■ sfua_rept_adm was used in 5.
28 Deploying Storage Foundation for Databases (SFDB) tools Requirements for Storage Foundation for Databases (SFDB) tools Veritas Storage Foundation for Databases (SFDB) tools features which are no longer supported Commands which are no longer supported as of version 5.1: ■ ORAMAP (libvxoramap) ■ Storage mapping commands dbed_analyzer, vxstorage_stats ■ DBED providers (DBEDAgent), Java GUI, and dbed_dbprocli. The SFDB tools features can only be accessed through the command line interface.
Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation environment For the most current information on Storage Foundation for Oracle RAC and Oracle RAC versions supported, see: http://entsupport.symantec.com/docs/280186 Review the current Oracle documentation to confirm the compatibility of your hardware and software.
30 Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation HA environment Figure 2-1 Storage Foundation setup example system1 Oracle Oracle mountpoints Repository Database volume Repository Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation HA environment If you are deploying the SFDB tools with Storage Foundation HA (single instance Oracle) your setup configuration will reflect the following
Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation HA environment Figure 2-2 Storage Foundation HA setup example system1 system2 Oracle Oracle Oracle mountpoints Oracle mountpoints Repository Repository Database volume Repository 31
32 Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in a SF Cluster File System (HA) environment Figure 2-3 Storage Foundation HA failover example system1 system2 Oracle Oracle Oracle mountpoints Oracle mountpoints Repository Repository Database volume Repository Deploying Storage Foundation for Databases (SFDB) tools in a SF Cluster File System (HA) environment If you are deploying the SFDB tools with SF Cluster File System HA (sin
Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in a SF Cluster File System (HA) environment In the figures below the repository directory resides in the Oracle mount points.
34 Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation for Oracle RAC environment Figure 2-5 SFCFS HA failover example system1 (offline) (offline) system2 (online) Oracle Oracle Oracle mountpoints Oracle mountpoints Repository Repository (online) Database volume Repository Deploying Storage Foundation for Databases (SFDB) tools in a Storage Foundation for Oracle RAC environment If you are deploying the SFDB to
Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Databases (SFDB) tools in replicated environments ■ 35 Clustered ODM is supported for this configuration. In the figure below the repository directory resides in the Oracle mount points.
36 Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Database (SFDB) tools in a NetBackup environment Deploying Storage Foundation for Database (SFDB) tools in a NetBackup environment If you are deploying the Storage Foundation for Databases (SFDB) tools in an environment that includes Veritas NetBackup, your setup configuration will reflect the following considerations: ■ NetBackup tools are supported. ■ Block-Level Incremental (BLI) Backup is supported.
Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Database (SFDB) tools with SmartMove and Thin Provisioning See the Veritas Storage Foundation Advanced Features Guide.
38 Deploying Storage Foundation for Databases (SFDB) tools Deploying Storage Foundation for Database (SFDB) tools with SmartMove and Thin Provisioning
Chapter 3 Administering Storage Foundation for Databases (SFDB) tools This chapter includes the following topics: ■ About administering the Storage Foundation for Databases (SFDB) tools ■ About the Storage Foundation for Databases (SFDB) repository database ■ Configuring the Storage Foundation for Databases (SFDB) repository ■ About upgrading Storage Foundation for Databases (SFDB) tools ■ Using SFDB tools after upgrading Oracle to 11.2.0.
40 Administering Storage Foundation for Databases (SFDB) tools About administering the Storage Foundation for Databases (SFDB) tools About administering the Storage Foundation for Databases (SFDB) tools After you have installed and configured your base Storage Foundation product, you can set up and administer the Storage Foundation for Databases tools for optimizing storage for your Oracle database. The following procedures apply for all Storage Foundation 5.
Administering Storage Foundation for Databases (SFDB) tools Configuring the Storage Foundation for Databases (SFDB) repository ■ The ORACLE_SID and the ORACLE_HOME variables must be specified with and -S and -H options. Locations for the SFDB repository Locations for the repository: ■ The default is on the volume where the SYSTEM tablespace resides. ■ You can specify an alternate location using –R option of dbed_update. In the figure below the repository directory resides in the Oracle mount points.
42 Administering Storage Foundation for Databases (SFDB) tools Configuring the Storage Foundation for Databases (SFDB) repository ■ ■ ■ Make sure that the repository and the Oracle database are failed over together to the same host For Storage Foundation Cluster File System (HA): on shared storage.
Administering Storage Foundation for Databases (SFDB) tools Configuring the Storage Foundation for Databases (SFDB) repository 43 Preparing to set up the SFDB repository Before you run any SF for Databases tools commands, you must set the permissions correctly to prevent permission problems. To prepare to set up the SFDB repository ◆ To set the permissions correctly for the SFDB directories, use the sfua_db_config command.
44 Administering Storage Foundation for Databases (SFDB) tools Configuring the Storage Foundation for Databases (SFDB) repository Option Sample value Description -H ORACLE_HOME The ORACLE_HOME setting for the ORACLE_SID database. -P ORACLE_PFILE Specifies the fully qualify path of the Oracle pfile if it is not located under ORACLE_HOME/dbs directory. -R REPOSITORY_PATH Specifies a user-defined location for the repository. In a RAC or HA situation, it should be located on shared storage.
Administering Storage Foundation for Databases (SFDB) tools About upgrading Storage Foundation for Databases (SFDB) tools To set up the SFDB repository ◆ As Oracle DBA user, run the following to create or update the SFDB repository for the database. $ dbed_update -S $ORACLE_SID -H $ORACLE_HOME About upgrading Storage Foundation for Databases (SFDB) tools If you are upgrading from 5.1, there are no issues. Follow the normal upgrade procedures for your Storage Foundation Enterprise product.
46 Administering Storage Foundation for Databases (SFDB) tools Using SFDB tools after upgrading Oracle to 11.2.0.2 (2203228) ■ ■ Upgrade from Storage Foundation for Oracle to Storage Foundation 5.1 SP1. ■ Migrate the SFDB repository database to version 5.1 SP1. ■ For upgrade and conversion procedures: See Veritas Storage Foundation™ and High Availability Installation Guide Storage Foundation for Oracle RAC: ■ Upgrade to Storage Foundation for Oracle RAC 5.1 SP1.
Administering Storage Foundation for Databases (SFDB) tools Backing up and restoring the Storage Foundation for Databases (SFDB) repository ■ The disk space at backup location is automatically managed. ■ Each SFDB repository backup file has a timestamp in its filename. ■ The backup command preserves only last seven backups. 47 For high availability environments: ■ Make sure the backup location is accessible by all nodes. ■ The backup command can be run from any node.
48 Administering Storage Foundation for Databases (SFDB) tools Migrating Storage Foundation for Databases (SFDB) objects from single instance Oracle to Oracle RAC To back up an SFDB repository 1 Verify that the database is online and that the backup location directory has write permission enabled for the DBA Oracle user. 2 Verify the SFDB repository is up to date: $ dbed_update -S $ORACLE_SID -H $ORACLE_HOME 3 As Oracle DBA user, run the backup command with the appropriate options.
Administering Storage Foundation for Databases (SFDB) tools Updating the Storage Foundation for Databases (SFDB) repository after adding a node 49 To re-create the SFDB repository 1 After migrating from Storage Foundation HA to Storage Foundation for Oracle RAC, run dbed_update. 2 Re-create the SFDB objects that existed in the Storage Foundation HA environment. They will now be supported for SFRAC.
50 Administering Storage Foundation for Databases (SFDB) tools Updating the Storage Foundation for Databases (SFDB) repository after removing a node Updating the Storage Foundation for Databases (SFDB) repository after removing a node If you are using Database Checkpoints, Database Flashsnap, or SmartTier for Oracle in your configuration, update the SFDB repository to remove the reference for the node after removing the node from the cluster.
Administering Storage Foundation for Databases (SFDB) tools Removing the Storage Foundation for Databases (SFDB) repository after removing the product To remove the SFDB repository 1 Change directories to the location of the local lookup information for the Oracle SID. For example: # cd /var/vx/vxdba/$ORACLE_SID 2 Identify the SFDB repository file and any associated links: For example: # ls -al lrwxrwxrwx 1 oracle oinstall /ora_data1/TEST/.sfdb_rept 26 Jul 21 13:58 .
52 Administering Storage Foundation for Databases (SFDB) tools Removing the Storage Foundation for Databases (SFDB) repository after removing the product
Section 2 Improving performance with database accelerators ■ Chapter 4. Overview of database accelerators ■ Chapter 5. Improving database performance with Veritas Extension for Oracle Disk Manager ■ Chapter 6. Improving database performance with Veritas Cached Oracle Disk Manager ■ Chapter 7. Improving database performance with Veritas Quick I/O ■ Chapter 8.
54
Chapter 4 Overview of database accelerators This chapter includes the following topics: ■ About Storage Foundation database accelerators ■ About Quick I/O ■ About Oracle Disk Manager ■ About Oracle Disk Manager and Oracle Managed Files ■ About Cached ODM About Storage Foundation database accelerators The major concern in any environment is maintaining respectable performance or meeting performance SLAs.
56 Overview of database accelerators About Quick I/O is no need for third-party multi-pathing software, reducing the total cost of ownership. Storage Foundation database accelerators enable you to manage performance for your database with more precision. ■ To improve Oracle performance and manage system bandwidth through an improved Application Programming Interface (API) that contains advanced kernel support for file I/O, use Veritas Oracle Disk Manager (ODM).
Overview of database accelerators About Oracle Disk Manager How Quick I/O works Veritas Quick I/O supports direct I/O and kernel asynchronous I/O and allows databases to access regular files on a VxFS file system as raw character devices. The benefits of using Quick I/O are: ■ Improved performance and processing throughput by having Quick I/O files act as raw devices.
58 Overview of database accelerators About Oracle Disk Manager Quick I/O-like capabilities, but is transparent to the user. Unlike Veritas Quick I/O, files managed using Veritas Extension for Oracle Disk Manager do not require special file naming conventions. The Oracle Disk Manager interface uses regular database files. If you are upgrading to Oracle10g or later, you should convert from Quick I/O to Oracle Disk Manager. Database administrators can choose the datafile type used with the Oracle product.
Overview of database accelerators About Oracle Disk Manager ■ Supporting many concurrent I/Os in one system call ■ Avoiding duplicate opening of files per Oracle instance ■ Allocating contiguous datafiles About kernel asynchronous I/O support Asynchronous I/O performs non-blocking system level reads and writes, allowing the system to perform multiple I/O requests simultaneously.
60 Overview of database accelerators About Oracle Disk Manager and Oracle Managed Files About avoiding duplicate file opens Oracle Disk Manager allows files to be opened once, providing a “file identifier.” This is called “identifying” the files. The same file identifiers can be used by any other processes in the Oracle instance. The file status is maintained by the Oracle Disk Manager driver in the kernel.
Overview of database accelerators About Oracle Disk Manager and Oracle Managed Files when considering auto-extensible tablespaces. Oracle Disk Manager eliminates this concern. When Oracle Disk Manager is used in conjunction with OMF, special care is given within Veritas Extension for Disk Manager to ensure that contiguous disk space is allocated to datafiles, including space allocated to a tablespace when it is auto-extended. The table and index scan throughput does not decay as the tablespace grows.
62 Overview of database accelerators About Oracle Disk Manager and Oracle Managed Files system as opposed to a collection of datafiles. Since OMF uses the Oracle Disk Manager file resize function, the tablespace files are initially created with the default size of 100MB and grow as needed. Use the MAXSIZE attribute to limit growth. The following example shows the commands for creating an OMF database and for creating the EMP_TABLE and EMP_INDEX tablespaces in their own locale.
Overview of database accelerators About Cached ODM -rw-r--r-- 1 oracle10g dba 186 May 3 15:03 PROD.ora ./EMP_INDEX: total 204808 -rw-r--r-- 1 oracle10g dba 104861696 May 3 15:43 ora_emp_inde_BEakGfun.dbf ./EMP_TABLE: total 204808 -rw-r--r-- 1 oracle10g dba 104861696 May 3 15:43 ora_emp_tabl_BEak1LqK.dbf About Cached ODM ODM I/O normally bypasses the file system cache and directly reads from and writes to disk.
64 Overview of database accelerators About Cached ODM Supported configurations Cached ODM is supported for: ■ Storage Foundation (HA) ■ Storage Foundation Cluster File System (HA) ■ Local and cluster mounts Storage Foundation for Oracle RAC is not currently supported. Cached ODM does not affect the performance of files and file systems for which you did not enable caching.
Chapter 5 Improving database performance with Veritas Extension for Oracle Disk Manager This chapter includes the following topics: ■ Setting up Veritas Extension for Oracle Disk Manager ■ Configuring Veritas Extension for Oracle Disk Manager ■ How to prepare existing database storage for Oracle Disk Manager ■ Converting Quick I/O files to Oracle Disk Manager files ■ Verifying that Oracle Disk Manager is configured ■ Disabling the Oracle Disk Manager feature Setting up Veritas Extension for Or
66 Improving database performance with Veritas Extension for Oracle Disk Manager Setting up Veritas Extension for Oracle Disk Manager Usage Notes When the Quick I/O feature is available, Oracle Disk Manager uses the Quick I/O driver to perform asynchronous I/O. Do not turn off the Quick I/O mount option, which is the default. ■ Oracle uses default file access methods if Oracle10g or later or a Veritas Storage Foundation Standard or Enterprise product is not installed, or VxFS 5.
Improving database performance with Veritas Extension for Oracle Disk Manager Configuring Veritas Extension for Oracle Disk Manager To link the Veritas extension for Oracle Disk Manager library into Oracle home for Oracle 10g 1 Shut down the database instance before linking the Oracle Disk Manager library. 2 Use the mv and ln commands as follows: For HP-UX PA, enter: # mv ${ORACLE_HOME}/lib/libodm10.sl \ ${ORACLE_HOME}/lib/libodm10.sl.orig # ln -s /opt/VRTSodm/lib/libodm.
68 Improving database performance with Veritas Extension for Oracle Disk Manager How to prepare existing database storage for Oracle Disk Manager # cd $ORACLE_HOME/lib ■ Take backup of libodm10.so, enter. # mv libodm10.so libodm10.so.oracle-`date '+%m_%d_%y-%H_%M_%S'` ■ Link libodm10.so with Veritas ODM library, enter: # ln -s /opt/VRTSodm/lib64/libodm.so libodm10.so For Oracle11g: ■ Change to the $ORACLE_HOME/lib directory, enter: # cd $ORACLE_HOME/lib ■ Take backup of libodm11.so, enter.
Improving database performance with Veritas Extension for Oracle Disk Manager Converting Quick I/O files to Oracle Disk Manager files If you are using Quick I/O files in a VxFS file system and you want to move to Oracle Disk Manager, convert the Quick I/O files to normal files using the qio_convertdbfiles -u command. You must be running Oracle10g or later to use Oracle Disk Manager.
70 Improving database performance with Veritas Extension for Oracle Disk Manager Verifying that Oracle Disk Manager is configured Prerequisites For HP Integrity systems: ■ /opt/VRTSodm/lib/libodm.sl must exist. ■ If you are using Oracle 10g, $ORACLE_HOME/lib/libodm10.sl is linked to /opt/VRTSodm/lib/libodm.sl. ■ The VRTSdbed license must be valid. ■ The VRTSodm package must be installed. For HP 9000 systems: ■ /opt/VRTSodm/lib/libodm.so must exist. ■ The VRTSdbed license must be valid.
Improving database performance with Veritas Extension for Oracle Disk Manager Verifying that Oracle Disk Manager is configured 71 To verify that Oracle Disk Manager is configured 1 Verify that the ODM feature is included in the license: # /opt/VRTS/bin/vxlicrep | grep ODM QLOGODM ODM = Enabled = Enabled The output verifies that ODM is enabled. Note: Verify that the license key containing the ODM feature is not expired. If the license key has expired, you will not be able to use the ODM feature.
72 Improving database performance with Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature To verify that Oracle Disk Manager is running 1 Start the Oracle database. 2 Check that the instance is using the Oracle Disk Manager function: # cat /dev/odm/stats # echo $? 0 3 Verify that the Oracle Disk Manager is loaded: # /usr/sbin/kcmodule -P state odm state loaded 4 In the alert log, verify the Oracle instance is running.
Improving database performance with Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature To disable the Oracle Disk Manager feature in an Oracle instance 1 Shut down the database instance. 2 Use the rm and ln commands to remove the link to the Oracle Disk Manager Library. For Oracle 11g, enter: # rm ${ORACLE_HOME}/lib/libodm11.sl $ ln -s ${ORACLE_HOME}/lib/libodmd11.sl \ ${ORACLE_HOME}/lib/libodm11.sl For Oracle 10g, enter: # rm ${ORACLE_HOME}/lib/libodm10.
74 Improving database performance with Veritas Extension for Oracle Disk Manager Disabling the Oracle Disk Manager feature 3 Restart the database instance.
Chapter 6 Improving database performance with Veritas Cached Oracle Disk Manager This chapter includes the following topics: ■ Configuring Cached ODM ■ Administering Cached ODM settings with Cached ODM Manager Configuring Cached ODM Configuring Cached ODM requires first enabling Cached ODM for a file system. After enabling Cached ODM, it can be configured in two ways: ■ The primary configuration method: turn caching on or off for all I/O on a per-file basis.
76 Improving database performance with Veritas Cached Oracle Disk Manager Configuring Cached ODM Enabling Cached ODM for file systems Cached ODM is initially disabled on a file system. You can enable Cached ODM for a file system by setting the odm_cache_enable option of the vxtunefs command after the file system is mounted. See the vxtunefs(1M) manual page. Note: The vxtunefs command enables conditional caching for all of the ODM files on the file system.
Improving database performance with Veritas Cached Oracle Disk Manager Configuring Cached ODM To enable unconditional caching on a file ◆ Enable unconditional caching on the file /mnt1/file1: # /opt/VRTS/bin/odmadm setcachefile /mnt1/file1=on With this command, ODM caches all reads from file1. To disable caching on a file ◆ Disable caching on the file /mnt1/file1: # /opt/VRTS/bin/odmadm setcachefile /mnt1/file1=off With this command, ODM does not cache reads from file1.
78 Improving database performance with Veritas Cached Oracle Disk Manager Configuring Cached ODM To add caching advisories to the cachemap 1 Add a caching advisory to the cachemap: # /opt/VRTS/bin/odmadm setcachemap data/data_read_seq=cache,readahead With this example command, ODM uses caching and readahead for I/O to online log files (data) that have the data_read_seq I/O type. You can view the valid file type and I/O type values from the output of the odmadm getcachemap command.
Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager Administering Cached ODM settings with Cached ODM Manager The Cached ODM Manager simplifies the task of managing the cached ODM settings for database administrators: ■ Cached ODM Manager enables you to manage and configure cached ODM on database files without requiring root privileges.
80 Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager Table 6-1 Cached ODM Manager command options (continued) Option Use -o off Disable Cached ODM. -o odmstats Displays Cached ODM I/O statistics per file. -o iostats Displays cumulative I/O statistics for file-type and I/O-type combinations. -c column_index The File I/O statistics would be sorted on specified column index. This is an optional field.
Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager After you enable Cached ODM on the first set of datafiles using the –o on option, you can continue to call the dbed_codm_adm -o display option to display the next set of candidate datafiles. The following example procedures indicate the usage for this command.
82 Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager You can use Cached ODM Manager to enable and disable Cached ODM settings on database datafiles. dbed_codm_adm -S ORACLE_SID -H ORACLE_HOME -o [ on | off ] -f list_file datafile | \ For enabling or disabling Cached ODM on database data files: ■ Values for datafile and list_file should contain absolute pathnames.
Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager ■ The Cached ODM Manager will execute the odmadm setcachefile abc=on command and also add or update the entry into the configuration file. If you want to disable caching for abc: ■ The Cached ODM Manager will only execute the command odmadm setcachefile abc=off and also update the entry in the configuration file.
84 Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager Output is sorted from files with Cached ODM set to ON first then the files with cached ODM set to OFF for ease in finding all the files with Cached ODM ON.
Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager Notes ■ 85 If a datafile or a list of datafiles is not supplied, it will display odmstats of all the files that are being cached ODM enabled for the specified ORACLE_SID. Statistics are reset to zero when the file is no longer opened by anyone. ■ ODM statistics are only collected for filesystems where odm_cache_enable has been set.
86 Improving database performance with Veritas Cached Oracle Disk Manager Administering Cached ODM settings with Cached ODM Manager ■ The I/O statistics provide only counts of operations and do not indicate whether the operations were cached or not. ■ ODM I/O statistics are only collected for filesystems where odm_cache_enable has been set.
Chapter Improving database performance with Veritas Quick I/O This chapter includes the following topics: ■ Creating database files as Quick I/O files using qiomkfile ■ Preallocating space for Quick I/O files using the setext command ■ Accessing regular VxFS files as Quick I/O files ■ Converting Oracle files to Quick I/O files ■ About sparse files ■ Handling Oracle temporary tablespaces and Quick I/O ■ Displaying Quick I/O status and file attributes ■ Extending a Quick I/O file ■ Using Ora
88 Improving database performance with Veritas Quick I/O Creating database files as Quick I/O files using qiomkfile Creating database files as Quick I/O files using qiomkfile The best way to preallocate space for tablespace containers and to make them accessible using the Quick I/O interface is to use the qiomkfile. You can use the qiomkfile to create the Quick I/O files for either temporary or permanent tablespaces. Prerequisites ■ You can create Quick I/O files only on VxFS file systems.
Improving database performance with Veritas Quick I/O Creating database files as Quick I/O files using qiomkfile Specifies the space to preallocate for a file in bytes, kilobytes, megabytes, gigabytes, or sectors (1024 bytes) by adding a k, K, m, M, g, G, s, or S suffix. The default is bytes—you do not need to attach a suffix to specify the value in bytes.
90 Improving database performance with Veritas Quick I/O Preallocating space for Quick I/O files using the setext command -rw-r--r-- 1 oracle dba 104890368 Oct 2 13:42 .dbfile lrwxrwxrwx 1 oracle .dbfile::cdev:vxfs: dba 19 Oct 2 13:42 dbfile -> \ In the example, qiomkfile creates a regular file named /db01/.dbfile, which has the real space allocated. Then, qiomkfile creates a symbolic link named /db01/dbfile. This symbolic link is a relative link to the Quick I/O interface for /db01/.
Improving database performance with Veritas Quick I/O Accessing regular VxFS files as Quick I/O files 3 Create a symbolic link to allow databases or applications access to the file using its Quick I/O interface: # ln -s .filename::cdev:vxfs: filename 4 Change the owner and group permissions on the file: # chown oracle:dba .filename # chmod 660 .
92 Improving database performance with Veritas Quick I/O Converting Oracle files to Quick I/O files Usage notes ■ When possible, use relative path names instead of absolute path names when creating symbolic links to access regular files as Quick I/O files. Using relative path names prevents copies of the symbolic link from referring to the original file when the directory is copied. This is important if you are backing up or moving database files with a command that preserves the symbolic link.
Improving database performance with Veritas Quick I/O Converting Oracle files to Quick I/O files tables and the qio_convertdbfiles command to convert this list of database files to use Quick I/O. Note: It is recommended that you create a Storage Checkpoint before converting to or from Quick I/O. See “Creating Storage Checkpoints using dbed_ckptcreate” on page 212.
94 Improving database performance with Veritas Quick I/O Converting Oracle files to Quick I/O files Usage notes ■ ■ ■ ■ ■ ■ Converting existing database files to Quick I/O files may not be the best choice if the files are fragmented. Use of the -f option to determine the fragmentation levels is not supported for 5.1. If you choose to create new files, they will be contiguous.
Improving database performance with Veritas Quick I/O Converting Oracle files to Quick I/O files The following options are available for the qio_convertdbfiles command: -a Changes regular files to Quick I/O files using absolute path names. Use this option when symbolic links need to point to absolute path names (for example, at a site that uses SAP). -h Displays a help message. Creates the extra links for all datafiles and log files in the /dev directory to support SAP's brbackup.
96 Improving database performance with Veritas Quick I/O Converting Oracle files to Quick I/O files To extract a list of Oracle files to convert ◆ With the database instance up and running, run the qio_getdbfiles command from a directory for which you have write permission: $ cd /extract_directory $ /opt/VRTSdbed/bin/qio_getdbfiles -T ora The qio_getdbfiles command extracts the list file names from the database system tables and stores the file names and their size in bytes in a file called mkqio.
Improving database performance with Veritas Quick I/O Converting Oracle files to Quick I/O files To convert the Oracle database files to Quick I/O files 1 Shut down the database. 2 Run the qio_convertdbfiles command from the directory containing the mkqio.dat file: $ cd /extract_directory $ /opt/VRTSdbed/bin/qio_convertdbfiles The list of files in the mkqio.dat file is displayed. For example: file1 file2 file3 file4 file5 --> --> --> --> --> .file1::cdev:vxfs: .file2::cdev:vxfs: .file3::cdev:vxfs: .
98 Improving database performance with Veritas Quick I/O About sparse files To undo the previous run of qio_convertdbfiles and change Quick I/O files back to regular VxFS files 1 If the database is running, shut it down. 2 Run the following command from the directory containing the mkqio.dat file: $ cd /extract_directory $ /opt/VRTSdbed/bin/qio_convertdbfiles -u The list of Quick I/O files in the mkqio.dat file is displayed. For example: .file1::cdev:vxfs: .file2::cdev:vxfs: .file3::cdev:vxfs: .
Improving database performance with Veritas Quick I/O Handling Oracle temporary tablespaces and Quick I/O So a 1TB file system can potentially store up to 2TB worth of files if there are sufficient blocks containing zeroes. Quick I/O files cannot be sparse and will always have all blocks specified allocated to them. Handling Oracle temporary tablespaces and Quick I/O You can create a new temporary tablespace using Quick I/O files.
100 Improving database performance with Veritas Quick I/O Handling Oracle temporary tablespaces and Quick I/O To drop an existing temporary tablespace and recreate using Quick I/O files 1 Drop the temporary tablespace, including its contents: $ sqlplus /nolog SQL> connect / as sysdba; SQL> drop tablespace tablespace_name including contents; 2 Create a Quick I/O file on a VxFS file system: # /opt/VRTS/bin/qiomkfile -h header_size -s size \ /mount_point/filename.
Improving database performance with Veritas Quick I/O Displaying Quick I/O status and file attributes size 100M reuse; Tablespace created. Displaying Quick I/O status and file attributes You can obtain and display information about Quick I/O status and file attributes using various options of the ls command: -al Lists all files on a file system, including Quick I/O files and their links. -1L Shows if Quick I/O was successfully installed and enabled.
102 Improving database performance with Veritas Quick I/O Extending a Quick I/O file To determine if an Oracle datafile has been converted to Quick I/O ◆ Use the ls command as follows: $ ls -lL filename The following example shows how to determine if Quick I/O is installed and enabled: $ ls -lL dbfile crw-r--r-- 1 oracle dba crw-r--r-- 1 oracle dba 45, 1 237 0x000004 Oct 2 13:42 dbfile Oct 2 13:42 dbfile where the first character, c, indicates it is a raw character device file, and the major
Improving database performance with Veritas Quick I/O Extending a Quick I/O file Usage notes ■ You can also grow VxFS file systems online (provided the underlying disk or volume can be extended) using the fsadm command. You can expand the underlying volume and the filesystem with the vxresize command. ■ You must have superuser (root) privileges to resize VxFS file systems using the fsadm command. ■ See the fsadm_vxfs (1M) and qiomkfile (1M) manual pages for more information.
104 Improving database performance with Veritas Quick I/O Using Oracle's AUTOEXTEND with Quick I/O files Using Oracle's AUTOEXTEND with Quick I/O files Oracle supports an automatic extend feature that automatically grows a database file by a prespecified amount, up to a prespecified maximum size. For regular file system files, AUTOEXTEND works transparently, provided the underlying file system has enough space. For example, suppose the current size of a database file emp.
Improving database performance with Veritas Quick I/O Recreating Quick I/O files after restoring a database -e Extends the file by a specified amount to allow Oracle tablespace resizing. -r Increases the file to a specified size to allow Oracle tablespace resizing. You can grow underlying VxFS file systems online (provided the underlying disk or volume can be extended) using the fsadm command. See the fsadm_vxfs(1M) manual page for more information.
106 Improving database performance with Veritas Quick I/O Recreating Quick I/O files after restoring a database you have performed a full database recovery. The qio_recreate command uses the mkqio.dat file, which contains a list of the Quick I/O files used by the database and the file sizes. For information on recovering your database, refer to the documentation that came with your database software.
Improving database performance with Veritas Quick I/O Disabling Quick I/O If... Then... a Quick I/O file is smaller than the size listed the Quick I/O file is not recreated and a in the mkqio.dat file warning message is displayed. Disabling Quick I/O If you need to disable the Quick I/O feature, you first need to convert any Quick I/O files back to regular VxFS files. Then, remount the VxFS file system using a special mount option.
108 Improving database performance with Veritas Quick I/O Disabling Quick I/O
Chapter 8 Improving database performance with Veritas Cached Quick I/O This chapter includes the following topics: ■ Tasks for setting up Cached Quick I/O ■ Enabling Cached Quick I/O on a file system ■ Determining candidates for Cached Quick I/O ■ Enabling and disabling Cached Quick I/O for individual files Tasks for setting up Cached Quick I/O To set up and use Cached Quick I/O, you should do the following in the order in which they are listed: ■ Enable Cached Quick I/O on the underlying file sy
110 Improving database performance with Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system Enabling Cached Quick I/O on a file system Cached Quick I/O depends on Veritas Quick I/O running as an underlying system enhancement in order to function correctly. Follow the procedures listed here to ensure that you have the correct setup to use Cached Quick I/O successfully.
Improving database performance with Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system 111 To enable the qio_cache_enable flag for a file system ◆ Use the vxtunefs command as follows: # /sbin/fs/vxfs5.0/vxtunefs -s -o qio_cache_enable=1 / mount_point For example: # /sbin/fs/vxfs5.0/vxtunefs -s -o qio_cache_enable=1 /db02 where /db02 is a VxFS file system containing the Quick I/O files and setting the qio_cache_enable flag to “1” enables Cached Quick I/O.
112 Improving database performance with Veritas Cached Quick I/O Enabling Cached Quick I/O on a file system ■ volname is the name of the volume For example: /dev/vx/dsk/PRODdg/db01 qio_cache_enable=1 /dev/vx/dsk/PRODdg/db02 qio_cache_enable=1 where /dev/vx/dsk/PRODdg/db01 is the block device on which the file system resides. The tunefstab (4) manual pages contain information on how to add tuning parameters. See the tunefstab (4) manual page.
Improving database performance with Veritas Cached Quick I/O Determining candidates for Cached Quick I/O For example: # /opt/VRTS/bin/vxtunefs /db01 The vxtunefs command displays output similar to the following: Filesystem i/o parameters for /db01 read_pref_io = 2097152 read_nstream = 1 read_unit_io = 2097152 write_pref_io = 2097152 write_nstream = 1 write_unit_io = 2097152 pref_strength = 10 buf_breakup_size = 2097152 discovered_direct_iosz = 262144 max_direct_iosz = 1048576 default_indir_size = 8192 qio
114 Improving database performance with Veritas Cached Quick I/O Determining candidates for Cached Quick I/O following steps more than once to determine the best possible candidates for Cached Quick I/O. Before determining candidate files for Quick I/O, make sure the following conditions have been met: Prerequisites ■ You must enable Cached Quick I/O for the file systems. See “Enabling Cached Quick I/O on a file system” on page 110. Usage notes ■ See the qiostat (1M) manual page for more information.
Improving database performance with Veritas Cached Quick I/O Determining candidates for Cached Quick I/O About I/O statistics The output of the qiostat command is the primary source of information to use in deciding whether to enable or disable Cached Quick I/O on specific files. Statistics are printed in two lines per object.
116 Improving database performance with Veritas Cached Quick I/O Determining candidates for Cached Quick I/O Analyze the output to find out where the cache-hit ratio is above a given threshold. A cache-hit ratio above 20 percent on a file for a given application may be sufficient to justify caching on that file. For systems with larger loads, the acceptable ratio may be 30 percent or above. Cache-hit-ratio thresholds vary according to the database type and load.
Improving database performance with Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files Other tools for analysis While the output of the qiostat command is the primary source of information to use in deciding whether to enable Cached Quick I/O on specific files, we also recommend using other tools in conjunction with qiostat. For example, benchmarking software that measures database throughput is also helpful.
118 Improving database performance with Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files To enable Cached Quick I/O for an individual file ◆ Use the qioadmin command to set the cache advisory to ON as follows: $ /opt/VRTS/bin/qioadmin -S filename=ON /mount_point For example, running qiostat shows the cache hit ratio for the file /db01/system.dbf reaches a level that would benefit from caching. To enable Cached Quick I/O for the file /db01/system.
Improving database performance with Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files To enable or disable individual file settings for Cached Quick I/O automatically after a reboot or mount ◆ Add cache advisory entries in the /etc/vx/qioadmin file as follows: device=/dev/vx/dsk// filename,OFF filename,OFF filename,OFF filename,ON For example, to make the Cached Quick I/O settings for individual files in the /db01 file system persistent, edit the /et
120 Improving database performance with Veritas Cached Quick I/O Enabling and disabling Cached Quick I/O for individual files To display the current cache advisory settings for a file ◆ Use the qioadmin command with the -P option as follows: $ /opt/VRTS/bin/qioadmin -P filename /mount_point For example, to display the current cache advisory setting for the file cust.dbf in the /db01 file system: $ /opt/VRTS/bin/qioadmin -P cust.dbf /db01 cust.
Section 3 Making point-in-time copies ■ Chapter 9. About point-in-time copies ■ Chapter 10. Using Database FlashSnap for backup and off-host processing ■ Chapter 11. Using Database Storage Checkpoints and Storage Rollback ■ Chapter 12.
122
Chapter 9 About point-in-time copies This chapter includes the following topics: ■ Database snapshot and backup options ■ About Veritas Database FlashSnap ■ How Veritas Database FlashSnap works ■ About Database Storage Checkpoints and Storage Rollback in SF Enterprise products Database snapshot and backup options You can configure the following database components for cloning and recovery of databases: ■ Storage Checkpoints ■ Database FlashSnap The following sections provide a brief overview o
124 About point-in-time copies Database snapshot and backup options snapshot is no longer needed, the database administrator can import the original snapshot back to the primary host and resynchronize the snapshot to the original database volumes. Database FlashSnap commands are executed from the command line interface.
About point-in-time copies About Veritas Database FlashSnap ■ A Database Storage Checkpoint keeps track of block change information and thereby enables incremental database backup at the block level. ■ A Database Storage Checkpoint helps recover data from incorrectly modified files. ■ A Database Storage Checkpoint can be mounted, allowing regular file system operations to be performed.
126 About point-in-time copies How Veritas Database FlashSnap works ■ Not supported for Oracle RAC environments Database FlashSnap significantly reduces the time it takes to backup your database, increase the availability of your production database, and still maintain your production database’s performance.
About point-in-time copies About Database Storage Checkpoints and Storage Rollback in SF Enterprise products Veritas Database FlashSnap offers a flexible and efficient means of managing business-critical data. Database FlashSnap lets you capture an online image of an actively changing database at a given instant, called a point-in-time copy. You can perform system backup, upgrade, or perform other maintenance tasks on point-in-time copies while providing continuous availability of your critical data.
128 About point-in-time copies About Database Storage Checkpoints and Storage Rollback in SF Enterprise products Note: Veritas Storage Foundation Enterprise products only supports the SFDB features described in this guide. Additionally, the information in this chapter is only applicable for a Veritas Storage Foundation Enterprise products configuration.
Chapter 10 Using Database FlashSnap for backup and off-host processing This chapter includes the following topics: ■ Planning to use Database FlashSnap ■ Preparing hosts and storage for Database FlashSnap ■ About creating database snapshots ■ FlashSnap commands Planning to use Database FlashSnap Before using Database FlashSnap, you must first determine your intended application.
130 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap Selecting one or two hosts (off-host) If maintaining the performance of your primary database is critical, you can offload processing of the snapshots to a secondary host. For off-host processing, storage must be shared between the primary and secondary hosts.
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap Figure 10-1 Example of a Database FlashSnap solution on a primary host Primary Host 1 2 Disks containing primary volumes to hold production databases SCSI or Fibre Channel Connectivity Disks containing synchronized full-sized instant snapshot volumes Database FlashSnap off-host configuration A Database FlashSnap off-host configuration allows CPU- and I/O-intensive operations to be performe
132 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap Figure 10-2 Example of an off-host Database FlashSnap solution Secondary Host Primary Host Network 1 2 Disks containing primary volumes to hold production databases SCSI or Fibre Channel Connectivity Disks containing snapshot volumes Host and storage requirements Before using Database FlashSnap, ensure that the following requirements are met: ■ All files are on VxFS file systems ove
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap ■ The same version of Oracle is installed on both hosts, the Oracle binaries and datafiles are on different volumes and disks. ■ The UNIX login for the database user and group must be the same on both hosts. The UNIX UID and GID must also be the same. ■ You must have an Enterprise license on both hosts.
134 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap Prerequisites ■ You must be logged in as superuser (root). ■ The disk group must be version 110 or later. For more information on disk group versions, see the vxdg(1M) online manual page. Be sure that a data change object (DCO) and a DCO log volume are associated with the volume for which you are creating the snapshot.
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap The following sample procedure is for existing volumes without existing snapshot plexes or associated snapshot volumes. In this procedure, volume_name is the name of either a volume or a volume set. Note: You must be logged in as superuser (root) to issue the commands in the following procedure.
136 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap 4 Create a mirror of a volume: # vxsnap -g diskgroup addmir volume_name alloc=diskname Example of creating 3 mirrors for a particular volume: # vxsnap -g diskgroup addmir datavol \ nmirror=3 alloc=disk1,disk2,disk3 5 List the available mirrors: # vxprint -g diskgroup -F%name -e"pl_v_name in \"volume_name\"" 6 Enable database FlashSnap to locate the correct mirror plexes when creating sn
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap Note: You must be logged in as superuser (root) to issue the commands in the following procedure.
138 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap 8 Verify that the dbed_flashsnap tag has been set to the desired data plex, data_vol-02: # vxprint -g PRODdg -F%name -e"pl_v_name in \"data_vol\" \ && p2 in \"dbed_flashsnap\"" data_vol-02 9 TY dg dm dm dm NAME PRODdg PRODdg01 PRODdg02 PRODdg03 ASSOC PRODdg Disk_1 Disk_2 Disk_3 To verify that the snapshot volume was created successfully, use the vxprint -g dg command as follows: KSTATE
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap Upgrading existing volumes to use Veritas Volume Manager 5.1 SP1 The procedure below describes how to upgrade a volume created using a version older than VxVM 5.0 so that it can take advantage of Database FlashSnap. Note the following requirements and caveats for this procedure: ■ The plexes of the DCO volume require persistent storage space on disk to be available.
140 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap 3 For a volume that has one or more associated snapshot volumes, use the following command to reattach and resynchronize each snapshot: # vxsnap [-g diskgroup] snapback snapvol If persistent FastResync was enabled on the volume before the snapshot was taken, the data in the snapshot plexes is quickly resynchronized from the original volume.
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap 9 If the plex is in a SNAPDONE state, convert it to an ACTIVE state: # vxplex [-g diskgroup] convert state=ACTIVE data_plex 10 Convert the data plexes to a SNAPDONE state and associate a DCO plex with the data plex that will be used for snapshot operations: # vxplex [-g diskgroup] -o dcoplex=dco_plex_name convert \ state=SNAPDONE data_plex where dco_plex_name is the name of the DCO plex you are
142 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap 5 Disassociate and remove any older DCO object and DCO volumes. # vxassist -g PRODdg remove log data_vol logtype=dco 6 Upgrade the volume by associating a new DCO object and DCO volume. # vxsnap -g PRODdg prepare data_vol alloc="PRODdg01,PRODdg02" 7 View the existing DCO plexes and plex state. Scenario 1 In this scenario, there are enough DCO plexes for the data plexes.
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap pl data_vol_dcl-02 data_vol_dcl ENABLED 560 sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 0 ■ ACTIVE - - - - - Convert the data plex state from SNAPDONE to ACTIVE. # vxplex -g PRODdg convert state=ACTIVE data_vol-04 ■ Associate the data plex with a new DCO plex and convert it back to a SNAPDONE state.
144 Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap ENABLED 560 pl data_vol_dcl-01 data_vol_dcl ENABLED 560 sd PRODdg01-02 data_vol_dcl-01 ENABLED 560 pl data_vol_dcl-02 data_vol_dcl DISABLED 560 sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 - ACTIVE - - - ACTIVE - - 0 - - - - DCOSNP - - 0 - - - Scenario 2 In this scenario, there are fewer DCO plexes than data plexes.
Using Database FlashSnap for backup and off-host processing Preparing hosts and storage for Database FlashSnap sd PRODdg01-02 data_vol_dcl-01 ENABLED 560 0 ■ - - - Add a DCO plex to the DCO volume using the vxassist mirror command. # vxsnap -g PRODdg addmir data_vol_dcl alloc=PRODdg02 ■ Associate the data plex with the new DCO plex and convert it to a SNAPDONE state. The following command is used for a system running the HPUX OS.
146 Using Database FlashSnap for backup and off-host processing About creating database snapshots DISABLED 560 sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 0 DCOSNP - - - - - Changing the default control file location For Oracle 11gR2, while creating a database using DBCA, one of the control file locations defaults to the flash recovery area. (parameter : flash_recovery_area).
Using Database FlashSnap for backup and off-host processing About creating database snapshots Online database snapshots Table 10-1 describes the three types of snapshots that can be created. Table 10-1 Database snapshot types Database snapshot type Description online If the SNAPSHOT_MODE specified in the snapplan is set to online, the dbed_vmsnap command first puts the tablespaces to be snapshot into backup mode.
148 Using Database FlashSnap for backup and off-host processing About creating database snapshots Optionally, you can use the VxVM command (vxsnap) to create volume snapshots. However, unlike the Database FlashSnap commands, the vxsnap command does not automate disk group content reorganization functions. Figure 10-3 depicts the sequence of steps leading up to taking a snapshot using Database FlashSnap.
Using Database FlashSnap for backup and off-host processing About creating database snapshots Creating a snapshot Make sure the volumes used by the database are configured properly before attempting to take a snapshot. This database configuration requires superuser (root) privileges. Note: Database FlashSnap commands must be run by the Oracle database administrator.
150 Using Database FlashSnap for backup and off-host processing About creating database snapshots 4 On the secondary host, use the dbed_vmclonedb command to create a clone database using the disk group deported from the primary host. For more information: See “Cloning a database (dbed_vmclonedb)” on page 181.
Using Database FlashSnap for backup and off-host processing About creating database snapshots The following flow chart depicts the actions you can perform after creating a snapshot of your database using Database FlashSnap, and involve the following four questions: See Figure 10-4 for actions you can perform after creating a snapshot using Database FlashSnap.
152 Using Database FlashSnap for backup and off-host processing About creating database snapshots After creating a snapshot of your database Figure 10-4 Snapshot Create the snapshot volumes (dbed_vmsnap -o snapshot) No Do you want to clone the database? Yes Do you want to resynchronize the snapshot volumes? Will you use a clone on a secondary host? Yes Yes The snapshot diskgroup will be imported.
Using Database FlashSnap for backup and off-host processing About creating database snapshots Figure 10-5 is a flow chart of this process.
154 Using Database FlashSnap for backup and off-host processing About creating database snapshots Resynchronize the database Figure 10-6 Do you want to resynchronize the snapshot volumes? No Yes Resynchronize and reattach the snapshot volumes (dbed_vmsnap -o resync) Begin reverse resynchronization (dbed_vmsnap -o reverse_resync begin) Commit the reverse resynchronization changes? No Yes Commit the reverse resynchronization changes (dbed_vmsnap -o reverse_resync_commit) Abort reverse resynchroniza
Using Database FlashSnap for backup and off-host processing About creating database snapshots Figure 10-7 Clone on a secondary host? Will you use the clone on a secondary host? Yes No Do you want to (1) mount the snapshot volumes, (2) clone the database automatically, or (3) clone manually? (1) Mount the snapshot volumes dbed_vmclonedb -o mount (2) Mount the snapshot volumes and create the clone automatically dbed_vmclonedb -o recoverdb The snapshot disk group will be imported.
156 Using Database FlashSnap for backup and off-host processing FlashSnap commands Figure 10-8 Finished with the snapshot Are you done with the snapshot? Yes Shut down the database and unmount the snapshot volume dbed_vmclonedb -o umount Yes Is the clone on a secondary host? Deport the snapshot disk group.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Creating a snapplan (dbed_vmchecksnap) The dbed_vmchecksnap command creates a snapplan that dbed_vmsnap uses to create a snapshot of an Oracle database. The snapplan specifies snapshot scenarios: online, offline, or instant. You can name a snapplan file whatever you choose. Each entry in the snapplan file is a line in parameter=argument format.
158 Using Database FlashSnap for backup and off-host processing FlashSnap commands Table 10-2 Parameter values for dbed_vmchecksnap (continued) Parameter Value ARCHIVELOG_DEST The full path of the archive logs. There are several archive log destinations that can be used for database recovery if you are multiplexing the archive logs. You must specify which archive log destination to use. It is recommended that you have the archive log destination on a separate volume if SNAPSHOT_ARCHIVE_LOG is yes.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Table 10-2 Parameter values for dbed_vmchecksnap (continued) Parameter Value SNAPSHOT_MODE Specifies the database snapshot mode. Values can be online, offline, or instant. If the snapshot is created while the database is online, the dbed_vmsnap command will put the tablespaces into backup mode.
160 Using Database FlashSnap for backup and off-host processing FlashSnap commands Table 10-2 Parameter values for dbed_vmchecksnap (continued) Parameter Value ALLOW_REVERSE_RESYNC Values can be yes or no. By default, reverse resynchronization is off (set equal to no). If it is set to yes, data from the snapshot volume can be used to update the primary volume. Note: This parameter must be set to no for Oracle RAC. SNAPSHOT_MIRROR Specifies the number of plexes to be snapshot.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Prerequisites Storage must be configured as specified: See “Preparing hosts and storage for Database FlashSnap” on page 130. ■ You must be the Oracle database administrator. ■ ■ The disk group must be version 110 or later. For more information on disk group versions, see the vxdg(1M) manual page. ■ Be sure that a DCO and DCO volume are associated with the volume for which you are creating the snapshot.
162 Using Database FlashSnap for backup and off-host processing FlashSnap commands 3 Create a snapplan with default values using the dbed_vmchecksnap command: $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID \ -H ORACLE_HOME -f SNAPPLAN -o setdefaults -t host_name \ [-p PLEX_TAG] [-m] Example output for using multi-dg and for when when you specify -m option for mapped mount point.
Using Database FlashSnap for backup and off-host processing FlashSnap commands $ cd /export/snap_dir $ $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD \ -H /oracle/product/orahome -f snap1 -o setdefaults -t host1 Example ouput for a single disk group environment: Snapplan snap1 for PROD. ===================================================== SNAPSHOT_VERSION=5.
164 Using Database FlashSnap for backup and off-host processing FlashSnap commands host is host1, the secondary host is host2, and the working directory is /export/snap_dir. The following is an example of the dbed_vmchecksnap command and sample output: $cd /export/snap_dir $/opt/VRTS/bin/dbed_vmchecksnap -S PROD \ -H /oracle/product/orahome -f snap2 -o setdefaults -t host2 Example ouput for a single disk group environment: Snapplan snap2 for PROD.
Using Database FlashSnap for backup and off-host processing FlashSnap commands SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=no SNAPSHOT_MIRROR=1 By default, a snapplan’s SNAPSHOT_PLEX_TAG value is set as dbed_flashsnap. You can use the -p option to assign a different tag name. Make use of the -p option when creating the snapplan with the setdefaults option. In the following example, the -p option is used with setdefaults to assign my_tag as the SNAPSHOT_PLEX_TAG value.
166 Using Database FlashSnap for backup and off-host processing FlashSnap commands SNAPSHOT_PLAN_FOR=database SNAPSHOT_PLEX_TAG=my_tag SNAPSHOT_DG_PREFIX=SNAP SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=no SNAPSHOT_MIRROR=1 Example for creating a snapplan with mapped mount option enabled Example for creating a snapplan with mapped mount option enabled. $/opt/VRTS/bin/dbed_vmchecksnap -S PROD \ -H /oracle/product/orahome -f snap2 -o setdefaults -t host2 -m Snapplan snap2 for PROD.
Using Database FlashSnap for backup and off-host processing FlashSnap commands ORACLE_SID=slave ARCHIVELOG_DEST=/oraarch1_1/slave SNAPSHOT_ARCHIVE_LOG=yes SNAPSHOT_MODE=online SNAPSHOT_PLAN_FOR=database SNAPSHOT_PLEX_TAG=dbed_flashsnap SNAPSHOT_DG_PREFIX=SNAP_ SNAPSHOT_VOL_PREFIX=SNAP_ ALLOW_REVERSE_RESYNC=no SNAPSHOT_MIRROR=1 archdg1:arch1vol1= datadg1:data1vol2= datadg1:data1vol1= datadg2:data1vol1= datadg2:data1vol2= Edit the snapplan and add the mountpoints to the dg:volume pairs before you validate t
168 Using Database FlashSnap for backup and off-host processing FlashSnap commands repository. The snapplan is validated using the dbed_vmchecksnap command with the -o validate option. Consider the following prerequisites and notes before validating a snapplan: Prerequisites ■ Usage Notes ■ The database must be up and running while executing the dbed_vmchecksnap command. The dbed_vmchecksnap command must be run as the Oracle database administrator.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Example output for a single disk group environment: PRIMARY_HOST is host1 SECONDARY_HOST is host1 The version of PRIMARY_DG-PRODdg is 160. The primary diskgroup PRODdg is a shared disk group SNAPSHOT_DG is SNAP_PRODdg SNAPSHOT_MODE is online The database is running in archivelog mode.
170 Using Database FlashSnap for backup and off-host processing FlashSnap commands Snapshot plex and DCO log for prodvol1 is on PRODdisk12. SNAP_PRODdg1 for snapshot will include: PRODdisk11 PRODdisk12 Examining Oracle volume and disk layout for snapshot. Volume prodvol2 on PRODdg2 is ready for snapshot. Original plex and DCO log for prodvol2 is on PRODdisk21. Snapshot plex and DCO log for prodvol2 is on PRODdisk22.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Snapshot plex and DCO log for prod_db is on PRODdg04. SNAP_PRODdg for snapshot will include: PRODdg02 ALLOW_REVERSE_RESYNC is no The snapplan snap2 has been created. Example output for an environment with multiple disk groups: PRIMARY_HOST is host1 SECONDARY_HOST is host2 The version of PRIMARY_DG-PRODdg1 is 140. SNAPSHOT_DG is SNAP_PRODdg1 The version of SECONDARY_DG-PRODdg2 is 140.
172 Using Database FlashSnap for backup and off-host processing FlashSnap commands Usage Notes If the local snapplan is updated or modified, you must revalidate it. ■ If the database schema or disk group is modified, you must revalidate it after running dbed_update. ■ Displaying a snapplan You can use the dbed_vmchecksnap command to list all available snapplans and to display detailed information for a particular snapplan.
Using Database FlashSnap for backup and off-host processing FlashSnap commands To display detailed information for a snapplan ◆ Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S \ ORACLE_SID -f SNAPPLAN -o list In the following example, the snapplan snap1 is displayed. $ /opt/VRTS/bin/dbed_vmchecksnap -S PROD -f snap1 -o list SNAPSHOT_VERSION=5.
174 Using Database FlashSnap for backup and off-host processing FlashSnap commands To copy a snapplan from the SFDB repository to your current directory ◆ Use the dbed_vmchecksnap command as follows: $ /opt/VRTS/bin/dbed_vmchecksnap -S ORACLE_SID \ -f SNAPPLAN -o copy In the following example, the snapplan, snap1, is copied from the VxDBA repository to the current directory.
Using Database FlashSnap for backup and off-host processing FlashSnap commands See “About Database FlashSnap status information” on page 331. Prerequisites Usage Notes ■ You must be logged in as the Oracle database administrator. ■ You must create and validate a snapplan using dbed_vmchecksnap before you can create a snapshot image with dbed_vmsnap. ■ If you are performing offhost processing, you should use the dbed_vmsnap command on the primary host.
176 Using Database FlashSnap for backup and off-host processing FlashSnap commands To create a snapshot 1 Change directories to the working directory in which your snapplan is stored: $ cd /working_directory 2 Create the snapshot image using the dbed_vmsnap command. $ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN \ -o snapshot [-F] The snapshot volumes now represent a consistent backup copy of the database.
Using Database FlashSnap for backup and off-host processing FlashSnap commands /prod_db. /prod_ar. dbed_vmsnap ended at 2006-03-02 14:16:11 In this example, a snapshot image of the primary database, PROD, is created for an off-host configuration. In this case, the SECONDARY_HOST parameter specifies a different host name than the PRIMARY_HOST parameter in the snapplan. $ /opt/VRTS/bin/dbed_vmsnap -S PROD -f snap2 -o snapshot dbed_vmsnap started at 2005-03-02 23:01:10 VxDBA repository is up to date.
178 Using Database FlashSnap for backup and off-host processing FlashSnap commands Example system configuration for database backup on a secondary host Figure 10-9 Network Secondary host for database Primary host for database Local Disks Local Disks Controllers C1 C2 C3 C4 Controllers C1 C2 Disk arrays Volumes created on these disks are accessed by the primary host Snapshot volumes created on these disks are accessed by both hosts Backup to disk, tape, or other media by secondary host C3 C4
Using Database FlashSnap for backup and off-host processing FlashSnap commands Prerequisites ■ You must be logged in as the Oracle database administrator to use dbed_vmclonedb command. Before you can use the dbed_vmclonedb command, you must validate a snapplan and create a snapshot. See “Backing up the database from snapshot volumes (dbed_vmclonedb)” on page 177. See “Validating a snapplan (dbed_vmchecksnap)” on page 167. See “Creating a snapshot (dbed_vmsnap)” on page 174.
180 Using Database FlashSnap for backup and off-host processing FlashSnap commands To mount the snapshot volumes ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID \ -o mount,new_sid=new_sid,server_name=svr_name\ -f SNAPPLAN [-H ORACLE_HOME] \ [-r relocate_path] You can now back up an individual file or a group of files under a directory onto the backup media. In this example, snapshot volumes are mounted.
Using Database FlashSnap for backup and off-host processing FlashSnap commands 2 You can mount one of the listed Storage Checkpoints using the dbed_ckptmount command.
182 Using Database FlashSnap for backup and off-host processing FlashSnap commands clone rather than from the primary database to avoid introducing additional burdens on the production database. A clone database can also serve as a valid backup of the primary database. See “Backing up the database from snapshot volumes (dbed_vmclonedb)” on page 177. You can also back up the primary database to tape using snapshot volumes.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Prerequisites ■ You must be logged in as the Oracle database administrator. Before you can use the dbed_vmclonedb command, you must validate a snapplan and create a snapshot. See “About creating database snapshots” on page 146. See “Validating a snapplan (dbed_vmchecksnap)” on page 167. See “Creating a snapshot (dbed_vmsnap)” on page 174. ■ The volume snapshot must contain the entire database.
184 Using Database FlashSnap for backup and off-host processing FlashSnap commands To mount a database and recover it manually 1 Start and mount the clone database to allow manual database recovery: dbed_vmclonedb started at 2010-04-29 02:21:57 Editing remote_login_passwordfile in initclons1.ora. All redo-log files found. Altering instance_name parameter in initclons1.ora. Altering instance_number parameter in initclons1.ora. Altering thread parameter in initclons1.ora.
Using Database FlashSnap for backup and off-host processing FlashSnap commands 185 Altering thread parameter in initclone1.ora. Database CLONE1 (SID=clone1) is in recovery mode. If the database clone1 is recovered manually, you must run dbed_vmclonedb -o update_status to change the snapshot status. dbed_vmclonedb ended at 2010-06-22 00:13:19 The database status (database_recovered) needs to be updated for a clone database on the primary host after manual recovery has been completed.
186 Using Database FlashSnap for backup and off-host processing FlashSnap commands recoverdb option is not used, you can perform point-in-time recovery manually. In the following example, a clone of the primary database is automatically created on the same host as the primary database. $ /opt/VRTS/bin/dbed_vmclonedb -S FLAS11r2 \ -o recoverdb,new_sid=clone1,server_name=motmot.veritas.
Using Database FlashSnap for backup and off-host processing FlashSnap commands dbed_vmclonedb started at 2009-08-01 16:12:00 /prod_db should have been mapped to /tmp/datadst and /prod_ar should have been mapped to /tmp/archdst Editing remote_login_passwordfile in initcl2.ora. All redo-log files found. Altering instance_name parameter in initcl2.ora. Altering instance_number parameter in initcl2.ora. Altering thread parameter in initcl2.ora. Database NEWPROD (SID=NEWPROD) is running.
188 Using Database FlashSnap for backup and off-host processing FlashSnap commands To shut down the clone database and unmount all snapshot file systems ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -o umount,new_sid=NEWPROD,server_name=svr_name \ -f snap1 -r /clone dbed_vmclonedb started at 2006-03-02 15:11:22 umounting /clone/prod_db umounting /clone/arch dbed_vmclonedb ended at 2006-03-02 15:11:47 In this example output, the clone database is shut down, file systems are
Using Database FlashSnap for backup and off-host processing FlashSnap commands To start the clone database ◆ Use the dbed_vmclonedb command as follows: $ /opt/VRTS/bin/dbed_vmclonedb -S ORACLE_SID \ -o restartdb,new_sid=new_sid,server_name=svr_name \ -f SNAPPLAN [-H ORACLE_HOME] \ [-r relocate_path] In this example, the clone database is re-started on the same host as the primary database (same-node configuration).
190 Using Database FlashSnap for backup and off-host processing FlashSnap commands To recreate the Oracle tempfiles 1 If the tempfiles were not residing on the same file systems as the datafiles, the dbed_vmclonedb command displays WARNING and INFO messages similar to the following: WARNING: Not all tempfiles were included in snapshot for $ORACLE_SID, there is no snapshot volume for /clone_path/temp02.dbf. WARNING: Could not recreate tempfiles for $ORACLE_SID due to lack of free space.
Using Database FlashSnap for backup and off-host processing FlashSnap commands Resynchronizing the snapshot to your database When you have finished using a clone database or want to refresh it, you can resynchronize it with the original database. This is also known as refreshing the snapshot volume or merging the split snapshot image back to the current database image. After resynchronizing, the snapshot can be retaken for backup or decision-support purposes.
192 Using Database FlashSnap for backup and off-host processing FlashSnap commands Note: You must issue commands as an Oracle database administrator in the following procedure. To resynchronize the snapshot image ◆ Use the dbed_vmsnap command as follows: $ /opt/VRTS/bin/dbed_vmsnap -S ORACLE_SID -f SNAPPLAN -o resync In this example, the snapshot image is resynchronized with the primary database.
Using Database FlashSnap for backup and off-host processing FlashSnap commands ■ If the snapshot has not been taken and the snapshot plex (mirror) exists, remove the snapshot as follows: # vxsnap -g diskgroup rmmir volume 2 Remove the DCO and DCO volume: # vxsnap -g diskgroup unprepare volume 3 Remove the snapplan.
194 Using Database FlashSnap for backup and off-host processing FlashSnap commands
Chapter 11 Using Database Storage Checkpoints and Storage Rollback This chapter includes the following topics: ■ Using Storage Checkpoints and Storage Rollback for backup and restore ■ Determining space requirements for Storage Checkpoints ■ Storage Checkpoint Performance ■ Backing up and recovering the database using Storage Checkpoints ■ Guidelines for Oracle recovery ■ Database Storage Checkpoint Commands Using Storage Checkpoints and Storage Rollback for backup and restore Storage Checkpoi
196 Using Database Storage Checkpoints and Storage Rollback Using Storage Checkpoints and Storage Rollback for backup and restore Veritas NetBackup also makes use of Storage Checkpoints to provide a very efficient Oracle backup mechanism. About Storage Rollbacks Each Storage Checkpoint is a consistent, point-in-time image of a file system, and Storage Rollback is the restore facility for these on-disk backups.
Using Database Storage Checkpoints and Storage Rollback Using Storage Checkpoints and Storage Rollback for backup and restore You can set a quota to limit how much space a file system will give to all storage checkpoints, to prevent the checkpoints from consuming all free space. See the command dbed_ckptquota for more information. Storage Rollback restores a database, a tablespace, or datafiles on the primary file systems to the point-in-time image created during a Storage Checkpoint.
198 Using Database Storage Checkpoints and Storage Rollback Determining space requirements for Storage Checkpoints Determining space requirements for Storage Checkpoints To support Block-level Incremental (BLI) Backup and storage rollback, the file systems need extra disk space to store the Storage Checkpoints. The extra space needed depends on how the Storage Checkpoints are used.
Using Database Storage Checkpoints and Storage Rollback Storage Checkpoint Performance If you are restoring some of the files in the file system, you should first remove the data-full Storage Checkpoints that are no longer needed. If you have very limited free space on the file system, you may have to remove all data-full Storage Checkpoints in order for the restore to succeed.
200 Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints I/O associated with the primary file system. Therefore, performing database backup when the database is less active is recommended. Backing up and recovering the database using Storage Checkpoints Figure 11-1 below describes the general process for backing up and recovering the database using Storage Checkpoints.
Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints ■ Online ■ Offline ■ Instant Note: Instant Storage Checkpoint is not supported for Oracle RAC. To create a Storage Checkpoint with the online option, the database should be online and you must enable ARCHIVELOG mode for the database. Note: Refer to your Oracle documentation for information about enabling the archive log. For the offline option, the database should be offline.
202 Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints See “Creating Storage Checkpoints using dbed_ckptcreate” on page 212. See “Mounting Storage Checkpoints using dbed_ckptmount” on page 218. Storage Checkpoints can only be used to restore from logical errors (for example, a human error). Storage Checkpoints cannot be used to restore files due to a media failure, because all the data blocks are on the same physical device.
Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints To verify that a Storage Checkpoint is error-free 1 As oracle user, create and mount a Storage Checkpoint by issuing the following commands: $ /opt/VRTS/bin/dbed_ckptcreate -S PROD1 -H $ORACLE_HOME\ -o online Storage Checkpoint Checkpoint_1244130973 created.
204 Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints 3 Run the dbv tool against the datafile. For example: $ $ORACLE_HOME/bin/dbv file=/tmp/testckpt/oradata/\ PROD1/undotbs01.dbf DBVERIFY: Release 11.1.0.6.0 - Production on Thu Jun 4 21:35:03 2009 Copyright (c) 1982, 2007, Oracle. All rights reserved. DBVERIFY - Verification starting : FILE = /tmp/testckpt/oradata/PROD1\ /undotbs01.
Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints See “Creating Storage Checkpoints using dbed_ckptcreate” on page 212. See “Mounting Storage Checkpoints using dbed_ckptmount” on page 218. In the example procedure, all the database datafiles reside on one VxFS file system named /db01.
206 Using Database Storage Checkpoints and Storage Rollback Backing up and recovering the database using Storage Checkpoints Some database changes made after a Storage Checkpoint was taken may make it impossible to perform an incomplete recovery of the databases after Storage Rollback of an online or offline Storage Checkpoint using the current control files.
Using Database Storage Checkpoints and Storage Rollback Guidelines for Oracle recovery 6 Re-apply archive logs to the point before the table was deleted to recover the database to 4:00 p.m. Use one of the following commands: SQL> recover database until cancel SQL> recover database until change SQL> recover database until time 7 Open the database with the following command: SQL> alter database open resetlogs 8 Delete the Storage Checkpoint you created at 11:00 a.m.
208 Using Database Storage Checkpoints and Storage Rollback Guidelines for Oracle recovery stores all necessary database file information, log file information, the name of the database, the timestamp of database creation, and synchronization information, such as the Storage Checkpoint and log-sequence information needed for recovery. Rolling back the control file will result in an inconsistency between the physical database structure and the control file.
Using Database Storage Checkpoints and Storage Rollback Guidelines for Oracle recovery ■ To perform a complete media recovery: SQL> SET AUTORECOVERY ON; SQL> RECOVER DATABASE; ■ To perform an incomplete media recovery, use one of the following: SQL> RECOVER DATABASE UNTIL CANCEL; or SQL> RECOVER DATABASE UNTIL TIME ’yyyy-mm-dd:hh:mm:ss’; (You can confirm the time of error by checking the ../bdump/alert*.log file.
210 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Database Storage Checkpoint Commands The Storage Foundation for Databases (SFDB) tools provide a command line interface to many key operations. The command line interface enables you to incorporate command operations into scripts and other administrative processes. SFDB tools commands supported are located in the /opt/VRTS/bin directory.
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Table 11-1 Database Checkpoint commands (continued) Command Description dbed_ckptrollback Command that rolls back an Oracle instance to a Storage Checkpoint point-in-time image. See “Performing Storage Rollback using dbed_ckptrollback” on page 219. dbed_ckptremove Command that removes a Storage Checkpoint for an Oracle instance. See “Removing Storage Checkpoints using dbed_ckptremove” on page 221.
212 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Prerequisites ■ As root, you must run /opt/VRTSdbed/common/bin/sfua_db_config before creating the repository. It will set the owner and group of various directories needed for SFDB funtionality. ■ You must be logged on as the database administrator (typically, the user ID oracle).
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Prerequisites ■ You must be logged on as the database administrator (typically, the user ID oracle). ■ For best recoverability, always keep ARCHIVELOG mode enabled when you create Storage Checkpoints. Usage notes ■ dbed_ckptcreate stores Storage Checkpoint information in the SFDB repository. ■ See the dbed_ckptcreate(1M) manual page for more information.
214 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands To create an instant Storage Checkpoints ◆ Ensure that the database is online and use the dbed_ckptcreate command as follows: $ /opt/VRTS/bin/dbed_ckptcreate -S PROD \ -H /oracle/product/oracle -o instant Creating instant Storage Checkpoint of database PROD. Storage Checkpoint Checkpoint_971672051 created.
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands To display Database Checkpoints ◆ Use the dbed_ckptdisplay command as follows to display information for Storage Checkpoints created by SF Enterprise products: $ /opt/VRTS/bin/dbed_ckptdisplay -S PROD \ -H /oracle/product/ORA_HOME Storage Checkpoint Creation Time Checkpoint_975877759 Sun Apr 3 12:50:59 2005 Checkpoint_974428422_wr001Thu May 16 17:28:42 2005 Checkpoint_974428423 Thu May 16 17:28:42 2004 To displa
216 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands To display all Storage Checkpoints ◆ Use the dbed_ckptdisplay command as follows: $ /opt/VRTS/bin/dbed_ckptdisplay -S PROD \ -H /oracle/product/ORA_HOME -o all Storage Checkpoint Creation Time Checkpoint_971672042 Sun May 15 13:55:53 2005 Checkpoint_903937870 Fri May 13 22:51:10 2005 Checkpoint_901426272 Wed May 11 16:17:52 2005 NetBackup_incr_PROD_955133480 NBU NetBackup_full_PROD_9551329 52 NBU Status C+R
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Scheduling Storage Checkpoints using dbed_ckptcreate and cron You can use the dbed_ckptcreate command to schedule Storage Checkpoint creation in a cron job or other administrative script. Before scheduling Storage Checkpoints, the following conditions must be met: Prerequisites ■ Usage notes ■ You must be logged on as the database administrator (typically, the user ID oracle).
218 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands 30 23 1,15 * * /opt/VRTS/bin/dbed_ckptcreate -S PROD \ -H /oracle/product/ORA_HOME -o instant Note: Instant Storage Checkpoints are not supported for Oracle RAC. ■ To create a Storage Checkpoint at 1:00 a.m.
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands To mount Storage Checkpoints with the read/write option ◆ Use the dbed_ckptmount command as follows: $ /opt/VRTS/bin/dbed_ckptmount -S PROD -c Checkpoint_971672042 \ -m /tmp/ckpt_rw -o rw Creating Storage Checkpoint on /tmp/ckpt_rw/share/oradata with name Checkpoint_971672042_wr001 To mount Storage Checkpoints with the read only option ◆ Use the dbed_ckptmount command as follows: $ /opt/VRTS/bin/dbed_ckptmount -
220 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Before performing a Storage Rollback, the following conditions must be met: Prerequisites ■ Usage notes ■ You must be logged on as the database administrator. The dbed_ckptrollback command rolls an Oracle database back to a specified Storage Checkpoint. You can perform a Storage Rollback for the entire database, a specific tablespace, or list of datafiles.
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands To rollback datafiles to a Storage Checkpoint ◆ Use the dbed_ckptrollback command with the -F option as follows: $ /opt/VRTS/bin/dbed_ckptrollback -S PROD \ -H /oracle/product/ORA_HOME \ -F /share/oradata1/data01.dbf,/share/oradata2/index01.dbf \ -c Checkpoint_903937870 If the Oracle database is running, you must take the datafile offline before running this command.
222 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Cloning an existing database using a Storage Checkpoint must be done on the same host. You have the option to manually or automatically recover the database when using the dbed_clonedb command: ■ Manual (interactive) recovery, which requires using the -i option, of the clone database allows the user to control the degree of recovery by specifying which archive log files are to be replayed.
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Table 11-2 dbed_clonedb command options Option Description -S CLONE_SID Specifies the name of the new Oracle SID, which will be the name of the new database instance. -m MOUNT_POINT Indicates the new mount point of the Storage Checkpoint. -c CKPT_NAME Indicates the name of the Storage Checkpoint. -i Runs the command in interactive mode where you must respond to prompts by the system.
224 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands Copying initnew1.ora to /oracle/11gr1/dbs/initnew1.ora. About to start up new database and begin reconfiguration. Database new1 is being reconfigured. Did not see error regarding database name. Altering clone database archive log directory. Updating log_archive_dest in clone database init file. Found archive log destination at /snap_arch11r1/FLAS11r1. The latest archive log(s) must now be applied.
Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands About to start up new database and begin reconfiguration. Database new2 is being reconfigured. Did not see error regarding database name. Starting automatic database recovery. Shutting down clone database. Altering clone database archive log directory. Updating log_archive_dest in clone database init file. Found archive log destination at /snap_arch11r1/FLAS11r1. Mounting clone database.
226 Using Database Storage Checkpoints and Storage Rollback Database Storage Checkpoint Commands
Chapter 12 Backing up and restoring with Netbackup in an SFHA environment This chapter includes the following topics: ■ About Veritas NetBackup ■ About using Veritas NetBackup for backup and restore for Oracle ■ About using Veritas NetBackup to backup and restore Oracle Disk Manager files ■ Using Veritas NetBackup to backup and restore Quick I/O files for Oracle About Veritas NetBackup Veritas NetBackup provides backup, archive, and restore capabilities for database files and directories contained
228 Backing up and restoring with Netbackup in an SFHA environment About using Veritas NetBackup for backup and restore for Oracle Veritas NetBackup, while not a shipped component of Veritas Storage Foundation Enterprise products, can be purchased separately. How block-level incremental backup works Block-Level Incremental (BLI) Backup extends the capabilities of NetBackup to back up only changed data blocks of Oracle database files.
Backing up and restoring with Netbackup in an SFHA environment About using Veritas NetBackup to backup and restore Oracle Disk Manager files from any of the NetBackup clients. Client users can perform database backups and restores from their client systems on demand. About using Veritas NetBackup to backup and restore Oracle Disk Manager files Oracle allocates Oracle Disk Manager files with contiguous extent layouts for good database performance.
230 Backing up and restoring with Netbackup in an SFHA environment Using Veritas NetBackup to backup and restore Quick I/O files for Oracle $ ls -la /db01 total 2192 drwxr-xr-x 2 root root 96 Oct 20 17:39 . drwxr-xr-x 9 root root 8192 -rw-r--r-- 1 oracle dba 1048576 1 oracle dba 22 Oct 20 17:39 .. Oct 20 17:39 .dbfile lrwxrwxrwx Oct 20 17:39 dbfile ->\ .dbfile::cdev:vxfs: In the example above, you must include both the symbolic link dbfile and the hidden file .
Section 4 Tiering your storage ■ Chapter 13. Understanding storage tiering with SmartTier ■ Chapter 14. Configuring and administering SmartTier ■ Chapter 15.
232
Chapter 13 Understanding storage tiering with SmartTier This chapter includes the following topics: ■ About SmartTier ■ SmartTier building blocks ■ How SmartTier works ■ How SmartTier for Oracle works ■ SmartTier in a High Availability (HA) environment About SmartTier Note: SmartTier is the expanded and renamed feature previously known as Dynamic Storage Tiering (DST). SmartTier matches data storage with data usage requirements.
234 Understanding storage tiering with SmartTier SmartTier building blocks Tiered storage is the assignment of different types of data to different storage types to improve performance and reduce costs. With SmartTier, storage classes are used to designate which disks make up a particular tier. There are two common ways of defining storage classes: ■ Performance, or storage, cost class: The most-used class consists of fast, expensive disks.
Understanding storage tiering with SmartTier SmartTier building blocks disk array LUNs belonging to a single Veritas Volume Manager (VxVM) disk group. A multi-volume file system presents a single name space, making the existence of multiple volumes transparent to users and applications. Each volume retains a separate identity for administrative purposes, making it possible to control the locations to which individual files are directed.
236 Understanding storage tiering with SmartTier How SmartTier works Warning: Multiple tagging should be used carefully. A placement class is a SmartTier attribute of a given volume in a volume set of a multi-volume file system. This attribute is a character string, and is known as a volume tag. See the Veritas Volume Manager Administrator's Guide. How SmartTier works SmartTier is a VxFS feature that enables you to allocate file storage space from different storage tiers according to rules you create.
Understanding storage tiering with SmartTier How SmartTier works In a database environment, the access age rule can be applied to some files. However, some data files, for instance are updated every time they are accessed and hence access age rules cannot be used. SmartTier provides mechanisms to relocate portions of files as well as entire files to a secondary tier.
238 Understanding storage tiering with SmartTier How SmartTier for Oracle works How SmartTier for Oracle works In an Oracle database environment, the access age rule can be applied to archivelog files and Flashback files. Oracle updates the header of each datafile at every database checkpoint and hence access age rules cannot be used for datafiles. For a partitioned table, we can use the name base rule to relocate files belonging to a given partition, for instance last year, to the secondary storage tier.
Understanding storage tiering with SmartTier How SmartTier for Oracle works Figure 13-1 How Oracle stores database objects Database System tablespace Database tablespace Database file 2 Database file 1 Table Index Table Index Cluster Index Index Index Index Index Index Database file 3 Index Table Table Index Index Index Table Table Table Database objects may span files Drive 1 Drive 2 At the finest level of granularity, an Oracle database stores data in data blocks (also called lo
240 Understanding storage tiering with SmartTier How SmartTier for Oracle works tablespace, a segment can include extents from more than one file; that is, the segment can span datafiles. However, each extent can contain data from only one datafile. When a new extent is allocated for a segment, Oracle tries to spread (or stripe) extents among all datafiles in the tablespace at that time. When you run out of free data blocks in a tablespace, you can add additional datafiles.
Understanding storage tiering with SmartTier How SmartTier for Oracle works ■ Index segments: contain blocks for table indexes. It is important to database performance that I/O to these blocks are read/written at highest rate and hence should always be in the primary storage tier. Index segments move from one location to other in a tablespace/datafile and are not good candidates for relocating to secondary tier.
242 Understanding storage tiering with SmartTier How SmartTier for Oracle works ■ AWR file stats are available by default. No extra configuration is needed. ■ AWR file stats are the statistics generated by the database only. File stats from Veritas File System include both database transaction and other IO like backup/restore. ■ In a clustered Oracle RAC environment, AWR file stats include I/O from all the nodes. There is no need to collect from each node and sum it up.
Understanding storage tiering with SmartTier How SmartTier for Oracle works ■ Several extents are allocated from the same file such that 1MB of the datafile is used by extents. In other words, each table will have 1MB of storage allocated from a given datafile and all these extents are contiguous in the datafile. This makes using SmartTier for Oracle to tier storage at the file portion level practical.
244 Understanding storage tiering with SmartTier SmartTier in a High Availability (HA) environment to query the AWR and generate trend reports. You can use AWR to get file usage trends and relocate least used files to secondary storage tier. Advantages of using file statistics from AWR: ■ AWR file stats are available by default. No extra configuration is needed. ■ In a clustered environment, AWR file stats include IO from all the nodes. There is no need to collect from each node and sum it up.
Chapter 14 Configuring and administering SmartTier This chapter includes the following topics: ■ Configuring SmartTier for Oracle ■ SmartTier policy management ■ Running SmartTier for Oracle reports ■ Extent balancing in a database environment ■ Viewing SmartTier sub-file level reports ■ Administering SmartTier at the sub-file level Configuring SmartTier for Oracle To use SmartTier for Oracle, the following requirements must be met: ■ An Oracle database must be up and running.
246 Configuring and administering SmartTier Configuring SmartTier for Oracle ■ Classify, or tag volumes so that the tags indicate the quality of the underlying disk. ■ Display the free space on each class. ■ Add or remove volumes as necessary. Note: SmartTier for Oracle is the expanded and renamed feature known as Database Dynamic Storage Tiering (DBDST) in previous releases.
Configuring and administering SmartTier Configuring SmartTier for Oracle Set at least one of the parameters in maxclass, minclass, statinterval, sweeptime, sweepinterval, purgetime, or purgeinterval, to enable default values. Add at least one class to enable the default classes. Table 14-1 lists the options for the dbdst_admin command: Table 14-1 dbdst_admin command options Command option Description -S $ORACLE_SID Specifies the ORACLE_SID, which is the name of the Oracle instance.
248 Configuring and administering SmartTier Configuring SmartTier for Oracle Table 14-1 dbdst_admin command options (continued) Command option Description purgetime Time per day for the file purge to take place. Times are entered in 24-hour periods and should list hour: minute. For example, 8:30 AM is represented as 08:30 and 8:00 PM is represented as 20:00. Default value is 20:00. addclass Parameter that allows you to add a class to a database.
Configuring and administering SmartTier Configuring SmartTier for Oracle 249 setup-parameters maxclass=number,minclass=number,\ statinterval=minutes sweeptime=HH:MM,sweepinterval=days purgetime=HH:MM,purgeinterval=days storage_class operations addclass=classname:"description" rmclass=classname definechunk=classname:128k | 256k | 512k | 1m For example, to add a class called tier1 for database PROD, and to set up a purge interval of one, meaning that the file statistics will be gathered for one day and the
250 Configuring and administering SmartTier Configuring SmartTier for Oracle Note: You cannot remove the pre-defined storage classes (PRIMARY, SECONDARY, and BALANCE).
Configuring and administering SmartTier Configuring SmartTier for Oracle 251 Converting a Veritas File System (VxFS) to a VxFS multi-volume file system To convert your existing VxFS file system to a VxFS multi-volume file system, you must convert a single volume to a volume set. Converting a single volume to a volume set When you convert to a volume set using the dbdst_convert command, the original volume will be renamed to a new volume name. The mount device name will become the new volume set name.
252 Configuring and administering SmartTier Configuring SmartTier for Oracle For example, to convert the volume-based file system oradata to a SmartTier for Oracle-ready volume set file system on mount device /dev/vx/dsk/oradg/oradata, use the dbdst_convert command as follows: $ /opt/VRTS/bin/dbdst_convert -S PROD -M \ /dev/vx/dsk/oradg/oradata -v new_vol1,new_vol2 After conversion, you will have a volume set named oradata containing three volumes (oradata_b4vset, new_vol1, and new_vol2).
Configuring and administering SmartTier Configuring SmartTier for Oracle Table 14-2 dbdst_show_fs command options Command options Description -S $ORACLE_SID Specifies the ORACLE_SID, which is the name of the Oracle instance. -o volume Displays the free space on volumes in each class. -m Specifies the mount point. Before displaying the free space on a storage class, review the following information: Prerequisites ■ Make sure the file system is mounted. ■ See the dbdst_show_fs (1M) manual page.
254 Configuring and administering SmartTier Configuring SmartTier for Oracle $ dbdst_show_fs -S VRTS11r2 -m /data11r2 -o volume VOLUME NAME ----------- SIZE ---- USED ---- AVAILABLE --------- datavol-b4vset datavol1 datavol2 10240000 1024000 4608000 3585514 6654486 1024000 0 2347872 2260128 Adding new volumes to a storage class Use the dbdst_addvol command to add volumes to a volume set.
Configuring and administering SmartTier SmartTier policy management To remove a volume from a volume set Use the dbdst_rmvol command as follows: $ /opt/VRTS/bin/dbdst_rmvol -S $ORACLE_SID -M mount_device \ -v volume_name[,volume_name] For example: $/opt/VRTS/bin/dbdst_rmvol -S VRTS11r2 \ -M /dev/vx/dsk/dstdatadgot/datavol -v datavol6 SmartTier policy management You can choose to manually relocate files or tablespaces, or you can use a preset SmartTier policy.
256 Configuring and administering SmartTier SmartTier policy management Usage notes Multiple partitions cannot reside on the same tablespace. To relocate a file ■ Use the dbdst_file_move command as follows: $ /opt/VRTS/bin/dbdst_file_move -S $ORACLE_SID -o datafile \ -f listfile -c storage_class:days [-c storage_class:days] For example: $ /opt/VRTS/bin/dbdst_file_move -S VRTS11r2 -o datafile \ -f /tmp/external.
Configuring and administering SmartTier SmartTier policy management 257 Relocating table partitions Use the dbdst_partition_move to move table partitions. The command queries the database to validate the names of the table and partition. From this information, a list of datafiles is derived and a one-time move of the files to the desired class is executed.
258 Configuring and administering SmartTier SmartTier policy management Table 14-4 dbdst_present_policy command options Command option Description -d directory Indicates the directory on which the placement policy will be applied. -e Enforces the file system of the specified directory. Use this option if there was an error in the previous enforcement that has been corrected and needs to be enforced again. -R Removes all pattern-based placement policies related to this directory.
Configuring and administering SmartTier Running SmartTier for Oracle reports To create a preset policy ◆ Use the dbdst_preset_policy command as follows: $ dbdst_preset_policy -S oracle_sid -d directory \ [ -e | -R | -l | -P pattern_spec | -f pattern_file ] [-E] where pattern_spec has the format of "class=pattern,pattern,...[:class=pattern,pattern,...]" For example: $ /opt/VRTS/bin/dbdst_preset_policy -S VRTS11r2 \ -d /data11r2/VRTS11r2 -P "MEDIUM=*.dbf:FAST=*.
260 Configuring and administering SmartTier Extent balancing in a database environment Directory=/dev/vx/dsk/dstdatadg09/datavol : VRTS11r1 Rule Description = PRIMARY=MEDIUM=*.log,undo*.
Configuring and administering SmartTier Extent balancing in a database environment system increases over time, additional space in the form of new disks must be added. To increase space, you could perform a volume relayout using the command.
262 Configuring and administering SmartTier Extent balancing in a database environment ■ Volumes are removed from the volume set or from the policy, and the extents for a file residing on a removed volume need to be moved to other volumes in the policy. ■ An extent balancing policy is assigned to a file and its extents have to be reorganized to meet the chunk size requirements defined in the policy.
Configuring and administering SmartTier Extent balancing in a database environment $ /opt/VRTS/bin/dbdst_classify -S $ORACLE_SID \ -M /dev/vx/dsk/oradg/ora_vset -v vol1:GOLD,vol2:GOLD,vol3:GOLD For example: $ /opt/VRTS/bin/dbdst_classify -S VRTS11r2 \ -M /dev/vx/dsk/dstdatadgot/datavol -v datavol1:FAST,datavol2:MEDIUM It is important to note that, an MVFS can have multiple storage tiers and that each tier may have a different chunk size.
264 Configuring and administering SmartTier Viewing SmartTier sub-file level reports $ /opt/VRTS/bin/dbdst_show_fs -S $ORACLE_SID -m /oradata For example: $ /opt/VRTS/bin/dbdst_show_fs -S VRTS11r2 -m /data11r2 -o volume VOLUME NAME ----------datavol-b4vset datavol1 datavol2 SIZE ---10240000 1024000 4608000 USED ---3585514 1024000 2347872 AVAILABLE --------6654486 0 2260128 TAG --PRIMARY FAST MEDIUM When the GOLD or SILVER tier requires more space, we could add extra space by adding new volumes to th
Configuring and administering SmartTier Viewing SmartTier sub-file level reports 265 table/index extent resides. The reports provide information for decisions to move the database objects within different storage clases of the multi-volume filesystem. An Oracle tablespace is usually constructed of several datafiles. A database object such as a table or an index has extents allocated from multiple datafiles. A given datafile usually contains extents from multiple database objects.
266 Configuring and administering SmartTier Administering SmartTier at the sub-file level Table 14-5 dbdst_obj_view command options (continued) Command option Description -t table name Name of the table for which view report needs to be generated. -i index name Name of the index for which view report needs to be generated. -p partition name Name of the partition for which view report needs to be generated. -s start-extent Specifies the starting extent of the table/index.
Configuring and administering SmartTier Administering SmartTier at the sub-file level queries Oracle dba_extents catalog table and for each extent gets file offest and lengh in bytes. This command passes these offset/length information to VxFS low level SmartTier commands to move the database extents to desired storage class.
268 Configuring and administering SmartTier Administering SmartTier at the sub-file level Table 14-6 dbdst_obj_move command options (continued) Command option Description -p partition name Name of the partition which must be relocated. More than one partition can co-exist in the same tablespace. -c storage_class Specifies the storage class to which the table or index extents will be moved. -s start_extent Specifies the starting extent of the table or index. The default starting extent is zero.
Chapter 15 SmartTier for Oracle use cases This chapter includes the following topics: ■ SmartTier for Oracle file-based use cases ■ SmartTier for Oracle sub-file use cases SmartTier for Oracle file-based use cases The following file-based use cases are supported for SmartTier for Oracle: ■ Migrating partitioned data and tablespaces ■ Scheduling the relocation of archive and Flashback logs Migrating partitioned data and tablespaces Perhaps the simplest application of multi-tier storage to databases
270 SmartTier for Oracle use cases SmartTier for Oracle file-based use cases For example, sales are mostly catalog-driven for a large retailer specializing in sports equipment. Product details are saved in a large database and the product table is partitioned based on type of activity. Some of the products are seasonal and do not sell well at other times. For example, very few snow skis are sold during the summer. To achieve season-based migration, see the following example.
SmartTier for Oracle use cases SmartTier for Oracle file-based use cases To move summer data to slower storage and winter data to faster storage at the beginning of winter ◆ Use the dbdst_partition_move command as follows: $ /opt/VRTS/bin/dbdst_partition_move -S PROD -T product_tab \ -p winter -c fast_storage $ /opt/VRTS/bin/dbdst_partition_move -S PROD -T product_tab \ -p summer -c slow_storage These commands relocate the files that comprise the winter partition of the product_tab table to placement cla
272 SmartTier for Oracle use cases SmartTier for Oracle file-based use cases Similarly, Veritas Storage Foundation for DB Flashback technology creates logs that can be used for quick recovery from database corruption by restoring a database to its state at a previous time. Flashback logs are normally kept for a shorter period than archived database logs. If used at all, they are typically used within a few hours of creation. Two or three days are a typical Flashback log lifetime.
SmartTier for Oracle use cases SmartTier for Oracle file-based use cases Figure 15-1 273 Database storage configuration suitable for automatic relocation of archive and Flashback logs Volume Set New placement class oralog Medium placement class Clarion_v1 emc_v1 Original database Added top-tier volume volume Old placement class Clarion_v1 Added mid-tier Added low-tier volume volume The file system used by the production database in this example originally resides on the single volume oralog, wh
274 SmartTier for Oracle use cases SmartTier for Oracle sub-file use cases To classify volumes into storage classes ◆ Use the dbdst_classify command as follows: $ /opt/VRTS/bin/dbdst_classify -S PROD \ -M /dev/vx/dsk/oradg/oralog -v emc_v1:NEW $ /opt/VRTS/bin/dbdst_classify -S PROD \ -M /dev/vx/dsk/oradg/oralog -v clarion_v1:MEDIUM $ /opt/VRTS/bin/dbdst_classify -S PROD \ -M /dev/vx/dsk/oradg/oralog -v jbod_v1:OLD Once the volumes are configured, an administrator can define file placement policy rules t
SmartTier for Oracle use cases SmartTier for Oracle sub-file use cases ■ Relocating old table data to a lower cost tier Using AWR statistics to identify sub-file objects for potential relocation You can use Oracle's Automatic Workload Repository (AWR) statistics to identify sub-file objects for potential relocation by identifying key properties such as activity levels. The Oracle database collects these statistics for a variety of purposes, including making self-management decisions.
276 SmartTier for Oracle use cases SmartTier for Oracle sub-file use cases To generate an HTML or text report for a range of snapshot IDs 1 Run the awrrpt.sql script at the SQL prompt: SQL> @$ORACLE_HOME/rdbms/admin/awrrpt.sql 2 Specify whether you want an HTML or a text report. Enter value for report_type: text 3 Specify the number of days for which you want to list snapshot IDs.
SmartTier for Oracle use cases SmartTier for Oracle sub-file use cases ITEM_ID and ITEM from the sample segments reported above are the two most likely candidates for relocation to a higher performance tier. The commands to relocate them are: $ dbdst_obj_move -S $ORACLE_SID -H $ORACLE_HOME \ -i ITEM_ID -c SSD_TIER $ dbdst_obj_move -S $ORACLE_SID -H $ORACLE_HOME \ -t ITEM -c SSD_TIER For more on using the dbdst_obj_move command: See “Administering SmartTier at the sub-file level” on page 266.
278 SmartTier for Oracle use cases SmartTier for Oracle sub-file use cases See “Administering SmartTier at the sub-file level” on page 266. Relocating old table data to a lower cost or secondary tier In some databases such as TELCO applications, call detail records (CDR) accumulate very quickly. For regulatory purposes, these records must be saved for several years, causing the size of the database to grow at an enormous rate.
Section 5 Deploying SFDB tools in a replicated environment ■ Chapter 16.
280
Chapter 16 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment This chapter includes the following topics: ■ About deploying SF Databases tools with VVR ■ Using ODM, Cached ODM, Quick IO, and Cached IO for the Oracle database in a VVR environment ■ Using Storage Foundation for Databases (SFDB) tools in a VVR environment ■ About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard About deploying SF Databases tools with VVR Storage Foundatio
282 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment About deploying SF Databases tools with VVR ■ Performing a rollback of the database from a given filesystem checkpoint ■ Performing storage tiering using SmartTier for Oracle Veritas Volume Replicator (VVR) is an option of Veritas Volume Manager (VxVM) that works as a fully integrated component of VxVM.
Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment Using ODM, Cached ODM, Quick IO, and Cached IO for the Oracle database in a VVR environment ■ Storage configuration ■ Scheduled tasks ■ Storage statistics Storage Foundation for Databases (SFDB) tools best practices in a VVR replication environment The typical replication environment for Storage Foundation Enterprise products includes: ■ The volume and volumeset (vset) configuration parameters such as size and the nu
284 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment Using Storage Foundation for Databases (SFDB) tools in a VVR environment ■ 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.
Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment Using Storage Foundation for Databases (SFDB) tools in a VVR environment 5 Run the SFDB commands as needed for your tasks. 6 After finishing your SFDB tasks: 7 ■ Shut down the database. ■ Unmount the volumes. Resume VVR replication. Adding a virtual hostname after a DR failover After a DR failover, you will need to add a virtual hostname to the SFDB repository.
286 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment Using Storage Foundation for Databases (SFDB) tools in a VVR environment $ dbed_update -S $ORACLE_SID -H $ORACLE_HOME \ -o rename,old_node=dblxxeon04,new_node=dblxrep Note: The hostname should be exactly same as that listed by dbed_update -o list.
Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment Using Storage Foundation for Databases (SFDB) tools in a VVR environment 6 List checkpoints using dbed_ckptdisplay and rollback using dbed_ckptrollback into appropriate checkpoint. 7 After rollback, start Oracle and let it recover. This procedure assumes archive logs are also replicated and available for oracle recovery.
288 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment Using Storage Foundation for Databases (SFDB) tools in a VVR environment 11 Unmount the database file systems. 12 Restart VVR replication. Note: VVR replication will not start if you have not unmounted both the checkpoint file system and the database files system. Using Database FlashSnap in a VVR environment Database Flashsnap is the most popular feature of the SFDB tools and it requires the SFDB repository.
Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard Using SmartTier for Oracle in a VVR environment The volume tags are not replicated via VVR. This means we do not have same storage class information at the primary and remote sites. But, we do have same volume structure at both sites. SmartTier for Oracle policies are part of File System metadata and hence get replicated to the remote site.
290 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard ■ dbed_ckptcreate ■ dbed_ckptdisplay ■ dbed_ckptmount ■ dbed_ckptumount ■ dbed_ckptremove ■ dbed_ckptrollback ■ dbed_clonedb Flashsnap ■ dbed_vmchecksnap ■ dbed_vmsnap (no reverse resync) ■ dbed_vmclonedb Cloning a standby read-write access database with Oracle Data Guard Physical standby databases are read-only dat
Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard 5 Start redo log apply. For example: SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT; 6 Clone the snapshot. For more about using Database Flashsnap: See “Planning to use Database FlashSnap” on page 129.
292 Deploying Storage Foundation for Databases (SFDB) tools in a replicated environment About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard
Section 6 Troubleshooting SFDB tools ■ Chapter 17.
294
Chapter 17 Troubleshooting SFDB tools This chapter includes the following topics: ■ About troubleshooting Storage Foundation for Databases (SFDB) tools ■ About the vxdbd daemon ■ Troubleshooting Database FlashSnap ■ Troubleshooting SmartTier for Oracle ■ Upgrading Veritas Storage Foundation for Databases (SFDB) tools from 5.0MP2 to 5.1SP1 (2003131) ■ Upgrading Veritas Storage Foundation for Databases (SFDB) tools from 5.0.x to 5.1SP1 (2184482) ■ Relinking ODM after upgrading from 5.0.
296 Troubleshooting SFDB tools About troubleshooting Storage Foundation for Databases (SFDB) tools indications point to a component product or to Oracle as the source of a problem, it may be necessary to refer to the appropriate documentation to resolve it.
Troubleshooting SFDB tools About the vxdbd daemon About the vxdbd daemon The vxdbd daemon handles communication to and from the Veritas Storage Foundation product software. By default, vxdbd communicates with product over port number 3233. If there are conflicts with this port or other port-related problems, you can change the port by changing the VXDBD_SOCKET setting located in the /etc/vx/vxdbed/admin.properties file. Normally the vxdbd daemon starts automatically when the host boots up.
298 Troubleshooting SFDB tools Troubleshooting Database FlashSnap To change the communications port used by the vxdbd daemon 1 As the root user, stop the vxdbd daemon: /opt/VRTSdbed/common/bin/vxdbdctrl stop 2 In the /etc/vx/vxdbed/admin.
Troubleshooting SFDB tools Troubleshooting SmartTier for Oracle /var/vx/vxdba/logs/vxsnapadm_50.log Troubleshooting SmartTier for Oracle If the SmartTier for Oracle commands fail as in the following example, review the tsdb_debug.log. The tsdb_debug.log is located at: /var/vx/vxdba/logs/tsdb_debug.log For example, when the following message appears after issuing a dbdst_addvol command review the tsdb_debug.
300 Troubleshooting SFDB tools Upgrading Veritas Storage Foundation for Databases (SFDB) tools from 5.0MP2 to 5.1SP1 (2003131) ^^^^ /var/vx/vxdba/logs/tsdb_debug.log Can not add to data1vol, ERR 1 ERROR:1 Upgrading Veritas Storage Foundation for Databases (SFDB) tools from 5.0MP2 to 5.1SP1 (2003131) While upgrading from 50mp2 to 51SP1 the following error message could be seen when running sfua_rept_migrate: # /opt/VRTSdbed/migrate/sfua_rept_migrate Mounting SFUA Sybase ASA repository.
Troubleshooting SFDB tools Relinking ODM after upgrading from 5.0.x sfua_rept_upgrade is run, it is unable to find the S*vxdbms3 startup script and gives the error message: /sbin/rc3.d/S*vxdbms3 not found SFORA sfua_rept_migrate ERROR V-81-3558 File: is missing. SFORA sfua_rept_migrate ERROR V-81-9160 Failed to mount repository. Workaround Before running sfua_rept_migrate, rename the startup script NO_S*vxdbms3 to S*vxdbms3. Relinking ODM after upgrading from 5.0.
302 Troubleshooting SFDB tools Upgrading in an HP Serviceguard environment (2116455)
Section 7 Reference ■ Appendix A. Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager ■ Appendix B. Sample configuration files for clustered deployments ■ Appendix C. Database FlashSnap status information ■ Appendix D.
304
Appendix A Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager This appendix includes the following topics: ■ About the Storage Foundation plug-in for Oracle Enterprise Manager ■ Requirements for the Storage Foundation Plug-in for OEM ■ Deploying the Storage Foundation Plug-in for OEM ■ Adding instances for monitoring in the Storage Foundation Plug-in for OEM ■ Viewing Storage Foundation Plug-in for OEM reports ■ Troubleshooting the Storage Foundation plug-in
306 Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Requirements for the Storage Foundation Plug-in for OEM ■ VxFS properties ■ VxVM volume information ■ LUN information for database objects such as tablespace, redo logs, controlfile, datafiles Requirements for the Storage Foundation Plug-in for OEM Storage Foundation and High Availability product requirements are included in: ■ Veritas Storage Foundation™ Release Notes ■ Veritas Storage Foundation™ for Clus
Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Deploying the Storage Foundation Plug-in for OEM Prerequisites for the Storage Foundation Plug-in for OEM The following prerequisites must be installed before you can deploy the plug-in: ■ Oracle Enterprise Manager Grid Control 10g Release 2 or higher system and Agent ■ The Symantec Plug-in can only be deployed on UNIX Enterprise Manager Agents Supported configurations for the Storage Foundation Plug-in for OEM TheSt
308 Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Adding instances for monitoring in the Storage Foundation Plug-in for OEM To deploy the Storage Foundation Plug-in for OEM 1 Get the symantec_storage.jar file from /opt/VRTSdbed/.dba directory or download from the Symantec website. 2 Log in to Enterprise Manager Grid Control as a Super Administrator.
Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Adding instances for monitoring in the Storage Foundation Plug-in for OEM To add an instance for monitoring in the Storage Foundation Plug-in for OEM (symantec_storage) 1 In the Agent home page, select the symantec_storage target type from the Add drop-down list, then click GO. The Add Symantec Storage page appears as below.
310 Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Viewing Storage Foundation Plug-in for OEM reports Figure A-2 Storage Foundation Plug-in home page Viewing Storage Foundation Plug-in for OEM reports Viewing reports in the storage plug-in for OEM 1 Before displaying reports in Oracle Enterprise Manager, run dbed_update. 2 In the Storage Foundation Plug-in home page, select the Reports page.
Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Viewing Storage Foundation Plug-in for OEM reports Figure A-3 Reports overview page On the Tablespace Report page, the tablespace name is mapped to VxFS mount point, mount properties with volume usage in readable form.
312 Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Viewing Storage Foundation Plug-in for OEM reports The Datafile report maps the datafile and its tablespace to Symantec volumes & file systems with detailed property information and the LUNs being used by the volume containing the datafile. Figure A-5 Datafile report The controlfile, tempfile, and redo log reports are similar to the Datafile Report.
Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Troubleshooting the Storage Foundation plug-in for OEM Figure A-7 Volume Statistics Hourly Report Troubleshooting the Storage Foundation plug-in for OEM To troubleshoot a Symantec OEM plug-in problem, you must determine which component is causing the difficulty. It could be the agent or the Oracle Management Server (OMS).
314 Deploying Storage Foundation for Databases (SFDB) tools with Oracle Enterprise Manager Troubleshooting the Storage Foundation plug-in for OEM 5 From the EMD_URL, change /emd/main to /emd/browser/main and go to that URL. You should see all the targets that this agent is monitoring, including the Symantec Storage target you've added. 6 Selecting any target will display the list of metrics. Selecting any metric displayed should run the corresponding monitoring script and display a table of results.
Appendix B Sample configuration files for clustered deployments This appendix includes the following topics: ■ About sample configuration files ■ Sample configuration file for Storage Foundation for High Availability ■ Sample configuration file for Storage Foundation for Clustered File System HA ■ Sample configuration file for Storage Foundation for Oracle RAC About sample configuration files The sample configuration files illustrate several deployment scenarios: ■ Storage Foundation for High Ava
316 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for High Availability Sample configuration file for Storage Foundation for High Availability include include include include include "OracleASMTypes.cf" "types.cf" "Db2udbTypes.cf" "OracleTypes.cf" "SybaseTypes.
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for High Availability MountPoint = "/oraarch" BlockDevice = "/dev/vx/dsk/oradatadg/oraarchvol" FSType = vxfs FsckOpt = "-n" ) Mount ora_bin_mnt ( MountPoint = "/opt/oracle/orahome" BlockDevice = "/dev/vx/dsk/qorasrc/orasrc10g" FSType = vxfs FsckOpt = "-n" ) Mount ora_data1_mnt ( MountPoint = "/oradata" BlockDevice = "/dev/vx/dsk/oradatadg/oradatavol" FSType = vxfs FsckOpt = "-n" ) NIC Ora_NIC ( Device = la
318 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Clustered File System HA // // // // // // // // // // // // // // // // // // // // // // group Oracle_Group { IP Ora_IP { NIC Ora_NIC } Oracle Ora_Oracle { Mount ora_arch1_mnt { DiskGroup DG-oradatadg } Mount ora_bin_mnt { DiskGroup DG-orabindg } Mount ora_data1_mnt { DiskGroup DG-oradatadg } } } Sample configuration file for Storage Foundation for Clustered File System HA include include incl
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Clustered File System HA system system2 ( ) group Oracle_Group ( SystemList = { system1 = 0, system2 = 1 } AutoStartList = { system1 } ) IP Ora_IP ( Device = lan0 Address = "10.200.117.243" NetMask = "255.255.255.0" ) NIC Ora_NIC ( Device = lan0 ) Oracle Ora_Oracle ( Sid = ora11g Owner = oracle Home = "/opt/oracle/orahome" Pfile = "/opt/oracle/orahome/dbs/initora11g.
320 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Clustered File System HA // } group cvm ( SystemList = { system1 = 0, system2 = 1 } AutoFailOver = 0 Parallel = 1 AutoStartList = { system1, system2 } ) CFSMount oraarch_mnt ( Critical = 0 MountPoint = "/oraarch" BlockDevice = "/dev/vx/dsk/oradatadg/oraarchvol" ) CFSMount orabin_mnt ( Critical = 0 MountPoint = "/ora11" BlockDevice = "/dev/vx/dsk/ora11bin/ora11vol" ) CFSMount oradata2_mnt ( Criti
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Clustered File System HA CVMCluster cvm_clus ( CVMClustName = cluster1 CVMNodeId = { system1 = 0, system2 = 1 } CVMTransport = gab CVMTimeout = 200 ) CVMVolDg orabin_voldg ( CVMDiskGroup = orabindg CVMVolume = { oracle_volume } CVMActivation = sw ) CVMVolDg oradata2_voldg ( CVMDiskGroup = oradatadg2 CVMVolume = { oradatavol2, oraredovol } CVMActivation = sw ) CVMVolDg oradata_voldg ( CVMDiskGroup = or
322 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Clustered File System HA oraredo_mnt requires oradata2_voldg oraredo_mnt requires vxfsckd vxfsckd requires cvm_clus // resource dependency tree // // group cvm // { // CFSMount oraarch_mnt // { // CVMVolDg oradata_voldg // { // CVMCluster cvm_clus // { // CVMVxconfigd cvm_vxconfigd // } // } // CFSfsckd vxfsckd // { // CVMCluster cvm_clus // { // CVMVxconfigd cvm_vxconfigd // } // } // } // CFSMo
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Clustered File System HA // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // // CFSMount oradata2_mnt { CVMVolDg oradata2_voldg { CVMCluster cvm_clus { CVMVxconfigd cvm_vxconfigd } } } CVMVolDg orabin_voldg { CVMCluster cvm_clus { CVMVxconfigd cvm_vxconfigd } } CFSMount oradata2_mnt { CVMVolDg oradata2_voldg { CVMCluster cvm_clu
324 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC // // // // // // // // // // // // // // // // // // // // // // // // // // CFSfsckd vxfsckd { CVMCluster cvm_clus { CVMVxconfigd cvm_vxconfigd } } } CFSMount oraredo_mnt { CVMVolDg oradata2_voldg { CVMCluster cvm_clus { CVMVxconfigd cvm_vxconfigd } } CFSfsckd vxfsckd { CVMCluster cvm_clus { CVMVxconfigd cvm_vxconfigd } } } } Sample configuration file for Storage Foundation for Orac
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC "root@sxsvm03" = 0 } Administrators = { admin, "root@sxsvm02", "root@sxsvm03" } SecureClus = 1 UseFence = SCSI3 HacliUserLevel = COMMANDROOT ) system system1 ( ) system system2 ( ) group VxSS ( SystemList = { system1 = 0, system2 = 1 } Parallel = 1 AutoStartList = { system1, system2 } OnlineRetryLimit = 3 OnlineRetryInterval = 120 ) Phantom phantom_vxss ( ) ProcessOnOnly vxatd ( IgnoreArgs =
326 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC AutoFailOver = 0 Parallel = 1 AutoStartList = { system1, system2 } ) Application cssd ( Critical = 0 StartProgram = "/opt/VRTSvcs/rac/bin/cssd-online" StopProgram = "/opt/VRTSvcs/rac/bin/cssd-offline" CleanProgram = "/opt/VRTSvcs/rac/bin/cssd-clean" MonitorProgram = "/opt/VRTSvcs/rac/bin/cssd-monitor" ) CFSMount ocrmnt ( Critical = 0 MountPoint = "/ocr_vote" BlockDevice = "/dev/vx/dsk/o
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC Device @system1 = { lan1 = 0, lan2 = 1 } Device @system2 = { lan1 = 0, lan2 = 1 } Address @system1 = "192.168.12.1" Address @system2 = "192.168.12.2" NetMask = "255.255.240.
328 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC group ora_db ( SystemList = { system1 = 0, system2 = 1 } AutoStart = 0 AutoFailOver = 0 Parallel = 1 AutoStartList = { system1, system2 } ) CFSMount archive_mnt ( Critical = 0 MountPoint = "/oraarchive" BlockDevice = "/dev/vx/dsk/oradg/archivevol" ) CFSMount ora_data_mnt ( Critical = 0 MountPoint = "/oradata" BlockDevice = "/dev/vx/dsk/oradg/oradatavol" ) CVMVolDg ora_data_voldg ( Criti
Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC ora_data_mnt requires ora_data_voldg // resource dependency tree // // group ora_db // { // Oracle ORACLE // { // CFSMount archive_mnt // { // CVMVolDg ora_data_voldg // } // CFSMount ora_data_mnt // { // CVMVolDg ora_data_voldg // } // } // } 329
330 Sample configuration files for clustered deployments Sample configuration file for Storage Foundation for Oracle RAC
Appendix C Database FlashSnap status information This appendix includes the following topics: ■ About Database FlashSnap status information ■ Database FlashSnap Snapshot status information from the CLI About Database FlashSnap status information Veritas Database FlashSnap functionality provides the following information for the various snapplan stages and snapshot procedures: ■ Snapshot status information ■ Snapshot database status information Database FlashSnap Snapshot status information from th
332 Database FlashSnap status information Database FlashSnap Snapshot status information from the CLI Snapshot status information from the CLI Table C-1 shows detailed information about each snapshot status (SNAP_STATUS) value. Note: Database FlashSnap reverse resynchronization is not supported for Oracle RAC.
Database FlashSnap status information Database FlashSnap Snapshot status information from the CLI Table C-1 Snapshot status information from the CLI (continued) SNAP_STATUS Completed operations resync_vol_start dbed_vmsnap -o resync Re-run dbed_vmsnap -o (failed) resync resync_vol_end Allowed operations snapshot_dg_start snapshot_dg_end resync_start dbed_vmsnap -o resync Contact your system administrator for help.
334 Database FlashSnap status information Database FlashSnap Snapshot status information from the CLI Table C-1 Snapshot status information from the CLI (continued) SNAP_STATUS Completed operations Allowed operations restartdb_start dbed_vmclonedb -o restartdb (failed) ■ dbed_vmclonedb -o umount ■ Start the snapshot database manually.
Database FlashSnap status information Database FlashSnap Snapshot status information from the CLI Snapshot database status information from the CLI To view snapshot database status information from the command line, use the dbed_vmchecksnap command with the -o list option to list all available snapplans for a specified database. Snapshot database status information is displayed in the command output under the column heading DB_STATUS.
336 Database FlashSnap status information Database FlashSnap Snapshot status information from the CLI
Appendix D Using third party software to back up files This appendix includes the following topics: ■ About using third party software to back up files ■ Using third party software to back up files About using third party software to back up files Storage Foundation Enterprise products support the use of third party software for backing up files. However, Quick I/O is not supported for Storage Foundation Enterprise products.
338 Using third party software to back up files Using third party software to back up files If you are using RMAN's “proxy copy” backup method with a backup software other than NetBackup, the extent attributes may not be backed up. To ensure the restored datafiles have proper extent layouts, preallocate the lost datafiles using the odmmkfile command. This command preallocates contiguous space for files prior to restoring them.
Index A absolute path names using with Quick I/O 95 absolute pathnames use with symbolic links 92 accessing Quick I/O files with symbolic links 92 allocating file space 89 analyzing I/O statistics 115 archiving using NetBackup 227 autoextend using with Quick I/O files 104 automatic backups 227 B backing up using NetBackup 227 using Storage Checkpoints 200 using Storage Checkpoints and Storage Rollback 195 backing up a database 177 benefits of Quick I/O 57 BLI Backup.
340 Index creating (continued) symbolic links to access Quick I/O files 88 cron 217 scheduling Storage Checkpoints 217 crontab file 217 cross-platform data migration 19 customizing Cached Quick I/O 117 D database specifying type for Quick I/O 94 Database Checkpoint 19 Database FlashSnap 19 backing up databases 177 copying a snapplan 171 creating a snapshot 174 creating a snapshot mirror 133 dbed_vmchecksnap 171 dbed_vmclonedb 177 dbed_vmsnap 174 dbed_vmsnap -o resync 191 displaying a snapplan 171 host an
Index N NetBackup overview 227 NetBackup BLI Extension overview 228 O OMF 60 working with Oracle Disk Manager 61 Oracle autoextend feature 104 Oracle datafile header size 88 Oracle Disk Manager 57 benefits 58 converting Quick I/O files 69 disabling 73 migrating files to 69 preparing existing databases for use with 68 restoring files using NetBackup 229, 337 Oracle Enterprise Manager (OEM) 19 Oracle Managed Files 60 working with Oracle Disk Manager 61 Oracle tempfiles recreating 189 P persistence for Cach
342 Index snapshot volumes (continued) mounting 179 removing 192 resynchronizing 191 snapshots creating 174 sparse files 94, 98–99 Storage Checkpoints 195–196 backing up and recovering 200 backing up and recovering databases 200 creating 212 determining space requirements 198 displaying 214 performance 199 removing 221 scheduling 217 unmounting 219 using the CLI 210 verifying 201 Storage Rollback 196, 219 guidelines for recovery 207 symbolic links advantages and disadvantages 91 to access Quick I/O files
