Veritas InfoScale™ 7.4 Solutions Guide - Solaris
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Section III. Improving database performance
- Overview of database accelerators
- Improving database performance with Veritas Quick I/O
- About Quick I/O
- Improving database performance with Veritas Cached Quick I/O
- Improving database performance with Veritas Concurrent I/O
- Section IV. Using point-in-time copies
- Understanding point-in-time copy methods
- Backing up and recovering
- Preserving multiple point-in-time copies
- Online database backups
- Backing up on an off-host cluster file system
- Database recovery using Storage Checkpoints
- Backing up and recovering in a NetBackup environment
- Off-host processing
- Creating and refreshing test environments
- Creating point-in-time copies of files
- Section V. Maximizing storage utilization
- Optimizing storage tiering with SmartTier
- Optimizing storage with Flexible Storage Sharing
- Optimizing storage tiering with SmartTier
- Section VI. Migrating data
- Understanding data migration
- Offline migration from Solaris Volume Manager to Veritas Volume Manager
- How Solaris Volume Manager objects are mapped to VxVM objects
- Overview of the conversion process
- Planning the conversion
- Preparing a Solaris Volume Manager configuration for conversion
- Setting up a Solaris Volume Manager configuration for conversion
- Converting from the Solaris Volume Manager software to VxVM
- Post conversion tasks
- Online migration of a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v3
- VxFS features not available during online migration
- Migrating storage arrays
- Migrating data between platforms
- Overview of the Cross-Platform Data Sharing (CDS) feature
- CDS disk format and disk groups
- Setting up your system to use Cross-platform Data Sharing (CDS)
- Maintaining your system
- Disk tasks
- Disk group tasks
- Displaying information
- File system considerations
- Specifying the migration target
- Using the fscdsadm command
- Maintaining the list of target operating systems
- Migrating a file system on an ongoing basis
- Converting the byte order of a file system
- Migrating from Oracle ASM to Veritas File System
- Section VII. Veritas InfoScale 4K sector device support solution
Relocating old archive logs to tier two storage using SmartTier
A busy database can generate few hundred gigabytes of archivelogs per day. Restoring these archive logs from tape backup is not ideal because it increases database recovery time. Regulatory requirements could mandate that these archive logs be preserved for several weeks.
To save storage costs, you can relocate archive logs older than two days (for example) into tier two storage. To achieve this you must create a policy file, for example, archive_policy.xml.
Note:
The relocating archive logs use case applies for Sybase environments.
To relocate archive logs that are more than two days old to Tier-2
- Create a policy file. A sample XML policy file is provided below.
<?xml version="1.0"?> <!DOCTYPE PLACEMENT_POLICY SYSTEM "/opt/VRTSvxfs/etc\ /placement_policy.dtd"> <PLACEMENT_POLICY Version="5.0" Name="access_age_based"> <RULE Flags="data" Name="Key-Files-Rule"> <COMMENT> This rule deals with key files such as archive logs. </COMMENT>
<SELECT Flags="Data"> <COMMENT> You want all files. So choose pattern as '*' </COMMENT> <PATTERN> * </PATTERN> </SELECT>
<CREATE> <ON> <DESTINATION> <CLASS> tier1 </CLASS> </DESTINATION> </ON> </CREATE>
<RELOCATE> <TO> <DESTINATION> <CLASS> tier2 </CLASS> </DESTINATION> </TO> <WHEN> <ACCAGE Units="days"> <MIN Flags="gt">2</MIN> </ACCAGE> </WHEN> </RELOCATE>
</RULE> </PLACEMENT_POLICY>
Notice the ACCAGE units in the WHEN clause.
- To locate additional sample policy files, go to
/opt/VRTSvxfs/etc
.The access age-based policy is appropriate for this use case. Pay attention to the CREATE ON and RELOCATE TO sections of the XML file.
To apply a policy file
- As root, validate archive_policy.xml
# fsppadm validate /DBarch archive_policy.xml
- If the validation process is not successful, correct the problem. Validate archive_policy.xml successfully before proceeding.
- Assign the policy to /DBarch filesystem
# fsppadm assign /DBarch archive_policy.xml
- Enforce the policy. The relocation of two day old archive logs happens when the enforcement step is performed. The policy enforcements must be done every day to relocate aged archive logs. This enforcement can be performed on demand as needed or by using a cron- like scheduler.
# fsppadm enforce /DBarch