InfoScale™ 9.0 Solutions Guide - Linux
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Section III. Stack-level migration to IPv6 or dual stack
- Section IV. Improving database performance
- Overview of database accelerators
- Improving database performance with Veritas Concurrent I/O
- Improving database performance with atomic write I/O
- Section V. 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 VI. Maximizing storage utilization
- Optimizing storage tiering with SmartTier
- Optimizing storage with Flexible Storage Sharing
- Optimizing storage tiering with SmartTier
- Section VII. Migrating data
- Understanding data migration
- Offline migration from LVM to VxVM
- Offline conversion of native file system to VxFS
- Online migration of a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v4
- 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 VIII. Veritas InfoScale 4K sector device support solution
- Section IX. REST API support
- Support for configurations and operations using REST APIs
- Support for configurations and operations using REST APIs
- Section X. Reference
Relocating active indexes to premium storage
The database transaction rate depends upon how fast indexes can be accessed. If Indexes reside on slow storage, the database transaction rate suffers. Tier-0 storage is generally too expensive to be practical to relocate the entire table data to Tier-0. Indexes are generally much smaller in size and are created to improve the database transaction rate, hence it is more practical to relocate active indexes to Tier-0 storage. Using SmartTier you can move active indexes to Tier-0 storage.
For the following telephone company database example procedure, assume the call_details table has an index call_idx on the column customer_id.
To prepare to relocate call_idx to Tier-0 storage for DB2
- Find the tablespace where call_idx resides.
$ db2inst1$ db2 connect to PROD $ db2inst1$ db2 select index_tbspace from syscat.tables \ where tabname='call_details'
- In this example, the index is in tablespace tbs_call_idx. To get the tablespace id for tbs_call_idx and the list of containers:
$ db2inst1$ db2 list tablespaces
Note the tablespace id for tbs_call_idx.
- List the containers and record the filenames in the tabelspace tbs_call_idx.
$ db2inst1$ db2 list tablespace containers for <tablespace-id>
- Store the files in index_files.txt.
# cat index_files.txt /DB2data/NODE0000/IDX/call1.idx /DB2data/NODE0000/IDX/call2.idx /DB2data/NODE0000/IDX/call3.idx
To prepare to relocate call_idx to premium storage for Sybase
- Obtain a list of datafiles for the call_idx segment.
$ sybsadmin$ sp_helpsegment call_idx
- Note down the device names for the segment call_idx.
- For each device name use the sp_helpdevice system procedure to get the physical pathname of the datafile.
sybsadmin$ sp_helpdevice <device name>
- Save all the datafile path names in index_files.txt.
# cat index_files.txt /SYBdata/NODE0000/IDX/call1.idx /SYBdata/NODE0000/IDX/call2.idx /SYBdata/NODE0000/IDX/call3.idx
To relocate call_idx to Tier-0 storage
- Prepare the policy index_policy.xml.
Example policy:
<?xml version="1.0"?> <!DOCTYPE PLACEMENT_POLICY SYSTEM "/opt/VRTSvxfs/etc/\ placement_policy.dtd"> <PLACEMENT_POLICY Version="5.0" Name="selected files"> <RULE Flags="data" Name="Key-Files-Rule"> <COMMENT> This rule deals with key important files. </COMMENT>
<SELECT Flags="Data"> <DIRECTORY Flags="nonrecursive" > NODE0000</DIRECTORY> <PATTERN> call*.idx </PATTERN> </SELECT>
<RELOCATE> <COMMENT> Note that there is no WHEN clause. </COMMENT> <TO> <DESTINATION> <CLASS> tier0 </CLASS> </DESTINATION> </TO> </RELOCATE>
</RULE> </PLACEMENT_POLICY>
- Assign and enforce the policy.
# fsppadm validate /DBdata index_policy.xml # fsppadm assign /DBdata index_policy.xml # fsppadm enforce /DBdata