Tsm Useful Queries - HP StorageWorks 12000 - Virtual Library System EVA Gateway Manual

• Disable multiplexing in Oracle RMAN backups: In the VLS firmware version 3.3.0 (or higher) the
scripting requirements for Oracle data files have been relaxed, so it is no longer mandatory to
assign prefix naming conventions to Oracle data files to make sure the data is properly deduplic-
ated. The minimum requirement for RMAN to deduplicate efficiently is to disable multiplexing
(where you have multiple RMAN streams concurrently writing to the same drive). You can disable
multiplexing by setting FILESPERSET=1 for each database backup in the RMAN scripts (not
needed for archive logs or control files). You can define additional channels to increase the number
of parallel backup processes running with FILESPERSET=1 to generate the same RMAN perform-
ance as before, so that each stream goes to a different virtual tape drive. The RMAN script defines
the number of channels configured (drive mounts). The number of channels must be equal to the
client node's maximum number of mount points.
The following RMAN settings will not deduplicate because they always generate totally unique
data every backup:
• Incremental backups
• RMAN compressed backups
• RMAN encryption
NOTE:
If you had previously configured the prefix naming conventions in your Oracle RMAN scripts, this
will continue to deduplicate efficiently with the firmware version 3.3.0 (or higher), but you should
ensure that multiplexing is disabled as well. If you wish to remove the prefix naming conventions,
you will need to rename the backup job name in NetBackup. (New backup jobs will not deduplicate
against the previous jobs with the different job name.)
• TSM image files: TSM image file backups will only deduplicate if the differencing algorithm for
the corresponding policy is set to Backup-level. If the policy for these files is set to File-level, these
files will not be deduplicated. To simplify configuration, define a specific management class for
TSM image backups and configure that class in the VLS GUI for a backup-level deduplication
policy.

TSM Useful Queries

The following calls can help you better understand the current TSM environment and help with sizing
the virtual library:
• This select statement will list all primary storage pools that are not DISK and show the amount of
backup data in those pools:
select node_name, stgpool_name, physical_mb from occupancy where stg-
pool_name in (select stgpool_name from stgpools where pool-
type='PRIMARY'and devclass<>'DISK') and type='Bkup'
• This select statement will show the totaled sizes listed in the output from the previous select statement:
select sum(physical_mb) as "Primary Pool Storage (MB)" from occupancy
where stgpool_name in (select stgpool_name from stgpools where pool-
type='PRIMARY' and devclass<>'DISK') and type='Bkup'
• Display GB's data backed up broken down by "nodename" for a 7 day period:
select entity, cast(float(sum(bytes))/1024/1024/1024 as dec(8,4)) as
"Backed up data in GB" from summary where activity='BACKUP' and
start_time>timestamp(current_date)-(7)days group by entity
• Display backup totals in TB's for a 7 day period:
HP StorageWorks VLS and D2D Solutions Guide 203