InfoScale™ 9.0 Storage and Availability Management for DB2 Databases - AIX, Linux
- Section I. Storage Foundation High Availability (SFHA) management solutions for DB2 databases
- Overview of Storage Foundation for Databases
- About Veritas File System
- Overview of Storage Foundation for Databases
- Section II. Deploying DB2 with InfoScale products
- Deployment options for DB2 in a Storage Foundation environment
- Deploying DB2 with Storage Foundation
- Deploying DB2 in an off-host configuration with Storage Foundation
- Deploying DB2 with High Availability
- Deployment options for DB2 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 DB2 database performance
- About database accelerators
- Improving database performance with Quick I/O
- About Quick I/O
- Improving DB2 database performance with Veritas Concurrent I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Volume-level snapshots
- Storage Checkpoints
- Considerations for DB2 point-in-time copies
- Administering third-mirror break-off snapshots
- Administering Storage Checkpoints
- Database Storage Checkpoints for recovery
- Backing up and restoring with Netbackup in an SFHA environment
- Understanding point-in-time copy methods
- Section VI. Optimizing storage costs for DB2
- Section VII. Storage Foundation for Databases administrative reference
- Storage Foundation for Databases command reference
- Tuning for Storage Foundation for Databases
- Troubleshooting SFDB tools
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 DB2 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