Please enter search query.
Search <book_title>...
Veritas InfoScale™ 8.0.2 Storage and Availability Management for Oracle Databases - AIX, Linux, Solaris
Last Published:
2023-06-12
Product(s):
InfoScale & Storage Foundation (8.0.2)
Platform: AIX,Linux,Solaris
- Section I. Storage Foundation High Availability (SFHA) management solutions for Oracle databases
- Overview of Storage Foundation for Databases
- About Veritas File System
- Overview of Storage Foundation for Databases
- Section II. Deploying Oracle with Veritas InfoScale products
- Deployment options for Oracle in a Storage Foundation environment
- Deploying Oracle with Storage Foundation
- Setting up disk group for deploying Oracle
- Creating volumes for deploying Oracle
- Creating VxFS file system for deploying Oracle
- Deploying Oracle in an off-host configuration with Storage Foundation
- Deploying Oracle with High Availability
- Deploying Oracle with Volume Replicator (VVR) for disaster recovery
- Deployment options for Oracle in a Storage Foundation environment
- Section III. Configuring Storage Foundation for Database (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Configuring the Storage Foundation for Databases (SFDB) tools repository
- Configuring authentication for Storage Foundation for Databases (SFDB) tools
- Configuring and managing the Storage Foundation for Databases repository database
- Section IV. Improving Oracle database performance
- About database accelerators
- Improving database performance with Veritas Extension for Oracle Disk Manager
- About Oracle Disk Manager in the Veritas InfoScale products environment
- Improving database performance with Veritas Cached Oracle Disk Manager
- About Cached ODM in SFHA environment
- Configuring Cached ODM in SFHA environment
- Administering Cached ODM settings with Cached ODM Advisor in SFHA environment
- Generating reports of candidate datafiles by using Cached ODM Advisor in SFHA environment
- Generating summary reports of historical activity by using Cached ODM Advisor in SFHA environment
- Generating reports of candidate datafiles by using Cached ODM Advisor in SFHA environment
- Improving database performance with Quick I/O
- About Quick I/O
- Improving database performance with Cached Quick I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Volume-level snapshots
- About Reverse Resynchronization in volume-level snapshots (FlashSnap)
- Storage Checkpoints
- About FileSnaps
- Considerations for Oracle point-in-time copies
- Administering third-mirror break-off snapshots
- Administering space-optimized snapshots
- Creating a clone of an Oracle database by using space-optimized snapshots
- Administering Storage Checkpoints
- Database Storage Checkpoints for recovery
- Administering FileSnap snapshots
- Backing up and restoring with Netbackup in an SFHA environment
- Understanding point-in-time copy methods
- Section VI. Optimizing storage costs for Oracle
- Understanding storage tiering with SmartTier
- Configuring and administering SmartTier
- Configuring SmartTier for Oracle
- Optimizing database storage using SmartTier for Oracle
- Extent balancing in a database environment using SmartTier for Oracle
- Configuring SmartTier for Oracle
- SmartTier use cases for Oracle
- Compressing files and databases to optimize storage costs
- Using the Compression Advisor tool
- Section VII. Managing Oracle disaster recovery
- Section VIII. Storage Foundation for Databases administrative reference
- Storage Foundation for Databases command reference
- Tuning for Storage Foundation for Databases
- About tuning Veritas Volume Manager (VxVM)
- About tuning VxFS
- About tuning Oracle databases
- About tuning Solaris for Oracle
- Troubleshooting SFDB tools
- About troubleshooting Storage Foundation for Databases (SFDB) tools
- About the vxdbd daemon
- Resources for troubleshooting SFDB tools
- Manual recovery of Oracle database
- Storage Foundation for Databases command reference for the releases prior to 6.0
- Preparing storage for Database FlashSnap
- About creating database snapshots
- FlashSnap commands
- Creating a snapplan (dbed_vmchecksnap)
- Validating a snapplan (dbed_vmchecksnap)
- Displaying, copying, and removing a snapplan (dbed_vmchecksnap)
- Creating a snapshot (dbed_vmsnap)
- Backing up the database from snapshot volumes (dbed_vmclonedb)
- Cloning a database (dbed_vmclonedb)
- Guidelines for Oracle recovery
- Database Storage Checkpoint Commands
- Section IX. Reference
- Appendix A. VCS Oracle agents
- Appendix B. Sample configuration files for clustered deployments
- Appendix C. Database FlashSnap status information
- Appendix D. Using third party software to back up files
Example procedure to upgrade existing volumes to use Veritas Volume Manager 8.0.2
Note:
You must be logged in as superuser (root) to issue the commands in the following procedure.
In this example, the volume, data_vol, is upgraded to make use of VxVM 8.0.2 features.
To upgrade an existing volume created with an earlier version of VxVM
- Upgrade the disk group, PRODdg.
# vxdg upgrade PRODdg
- Remove the DRL plexes or subdisks belonging to an earlier version of VxVM from the volume to be upgraded.
# vxassist -g PRODdg remove log data_vol logtype=drl
- Reattach any snapshot volume back to the primary volume to be upgraded.
# vxsnap -g PRODdg snapback SNAP-data_vol
- Turn off FastResync on the volume to be upgraded.
# vxvol -g PRODdg set fastresync=off data_vol
- Disassociate and remove any older DCO object and DCO volumes.
# vxassist -g PRODdg remove log data_vol logtype=dco
- Upgrade the volume by associating a new DCO object and DCO volume.
# vxsnap -g PRODdg prepare data_vol alloc="PRODdg01,PRODdg02"
- View the existing DCO plexes and plex state.
Scenario 1
In this scenario, there are enough DCO plexes for the data plexes. Also, no data plex is associated with a DCO plex.
# vxprint -g PRODdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg PRODdg PRODdg - - - - - - dm PRODdg01 c1t2d0s2 - 35358848 - - - - dm PRODdg02 c1t3d0s2 - 17674896 - - - - dm PRODdg03 c1t1d0s2 - 17674896 - - - -
v data_vol fsgen ENABLED 4194304 - ACTIVE - - pl data_vol-01 data_vol ENABLED 4194304 - ACTIVE - - sd PRODdg01-01 data_vol-01 ENABLED 4194304 0 - - - pl data_vol-04 data_vol ENABLED 4194304 - SNAPDONE - - sd PRODdg02-03 data_vol-04 ENABLED 4194304 0 - - - dc data_vol_dco data_vol - - - - - - v data_vol_dcl gen ENABLED 560 - ACTIVE - - pl data_vol_dcl-01 data_vol_dcl ENABLED 560 - ACTIVE - - sd PRODdg01-02 data_vol_dcl-01 ENABLED 560 0 - - - pl data_vol_dcl-02 data_vol_dcl ENABLED 560 - ACTIVE - - sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 0 - - -
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.
# vxplex -g PRODdg -o dcoplex=data_vol_dcl-02 \ convert state=SNAPDONE data_vol-04 # vxprint -g PRODdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg PRODdg PRODdg - - - - - - dm PRODdg01 c1t2d0s2 - 35358848 - - - - dm PRODdg02 c1t3d0s2 - 17674896 - - - - dm PRODdg03 c1t1d0s2 - 17674896 - - - -
pl data_vol-03 - DISABLED 4194304 - - - - sd PRODdg02-01 data_vol-03 ENABLED 4194304 0 - - - v data_vol fsgen ENABLED 4194304 - ACTIVE - - pl data_vol-01 data_vol ENABLED 4194304 - ACTIVE - - sd PRODdg01-01 data_vol-01 ENABLED 4194304 0 - - - pl data_vol-04 data_vol ENABLED 4194304 - SNAPDONE - - sd PRODdg02-03 data_vol-04 ENABLED 4194304 0 - - - dc data_vol_dco data_vol - - - - - - v data_vol_dcl gen ENABLED 560 - ACTIVE - - pl data_vol_dcl-01 data_vol_dcl ENABLED 560 - ACTIVE - - sd PRODdg01-02 data_vol_dcl-01 ENABLED 560 0 - - - pl data_vol_dcl-02 data_vol_dcl DISABLED 560 - DCOSNP - - sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 0 - - -
Scenario 2
In this scenario, there are fewer DCO plexes than data plexes.
# vxprint -g PRODdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg PRODdg PRODdg - - - - - - dm PRODdg01 c1t2d0s2 - 35358848 - - - - dm PRODdg02 c1t3d0s2 - 17674896 - - - - dm PRODdg03 c1t1d0s2 - 17674896 - - - -
pl data_vol-03 - DISABLED 4194304 - - - - sd PRODdg02-01 data_vol-03 ENABLED 4194304 0 - - - v data_vol fsgen ENABLED 4194304 - ACTIVE - - pl data_vol-01 data_vol ENABLED 4194304 - ACTIVE - - sd PRODdg01-01 data_vol-01 ENABLED 4194304 0 - - - pl data_vol-04 data_vol ENABLED 4194304 - ACTIVE - - sd PRODdg02-03 data_vol-04 ENABLED 4194304 0 - - - dc data_vol_dco data_vol - - - - - - v data_vol_dcl gen ENABLED 560 - ACTIVE - - pl data_vol_dcl-01 data_vol_dcl ENABLED 560 - ACTIVE - - 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.
# vxplex -g PRODdg -o dcoplex=data_vol_dcl-02 \ convert state=SNAPDONE data_vol-04
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0 dg PRODdg PRODdg - - - - - - dm PRODdg01 c1t2d0s2 - 35358848 - - - - dm PRODdg02 c1t3d0s2 - 17674896 - - - - dm PRODdg03 c1t1d0s2 - 17674896 - - - -
pl data_vol-03 - DISABLED 4194304 - - - - v data_vol fsgen ENABLED 4194304 - ACTIVE - - pl data_vol-01 data_vol ENABLED 4194304 - ACTIVE - - sd PRODdg01-01 data_vol-01 ENABLED 4194304 0 - - - pl data_vol-04 data_vol ENABLED 4194304 - SNAPDONE - - sd PRODdg02-03 data_vol-04 ENABLED 4194304 0 - - - dc data_vol_dco data_vol - - - - - - v data_vol_dcl gen ENABLED 560 - ACTIVE - - pl data_vol_dcl-01 data_vol_dcl ENABLED 560 - ACTIVE - - sd PRODdg01-02 data_vol_dcl-01 ENABLED 560 0 - - - pl data_vol_dcl-02 data_vol_dcl DISABLED 560 - DCOSNP - - sd PRODdg02-02 data_vol_dcl-02 ENABLED 560 0 - - -