HP 12000 HP VLS Solutions Guide Design Guidelines for Virtual Library Systems - Page 147

Firmware Version 6.0, TSM Useful Queries

Get HP 12000 PDF manuals and user guides View all HP 12000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 147 highlights

• 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. • Reclamation: Limit the number of concurrent reclamation jobs per pool to one. TSM reclamation is the process of reclaiming space on sequential access storage pool volumes. Space becomes reclaimable when files expire or are deleted (as identified by expiration processing). Reclamation processing consolidates the remaining active data from multiple sequential access volumes onto fewer volumes. Reclaimed cartridges, those which were the source of reclaimed data, are essentially untouched by reclamation but are made available (scratched) for later reuse. The TSM reclaimed data is copied to a new cartridge, but none of this data will be deduplicated. The TSM reclaimed data is shown in the user interface as "Disabled, Unsupported and Overhead Data" on the System Capacity screen (System > Chassis > Deduplication > System Capacity). The TSM default reclamation threshold should be set to at least 90% or higher. If you run reclamation, reclaimed backups are expanded and subsequent backups are not deduplicated against them. For example, with the default reclamation threshold at 90%, 10% of the data will not be deduplicated. You should run reclamation outside of the backup window because it reduces processing bandwidth. The reclamation process is very device-intensive and requires at least two available drives in the library (to read and to write). You must increase the amount of available capacity for the retention period of the reclaimed backup data. Firmware Version 6.0 Mount retention: Changing the mount retention is now optional, and can be left at the default 60 minutes (it will just delay the start of deduplication). For optimum behavior you can change the mount retention to five minutes for your server configuration. 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 stgpool_name in (select stgpool_name from stgpools where pooltype='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 pooltype='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 IBM TSM 147

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
•
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.
•
Reclamation:
Limit the number of concurrent reclamation jobs per pool to one.
TSM reclamation
is the process of reclaiming space on sequential access storage pool volumes. Space becomes
reclaimable when files expire or are deleted (as identified by expiration processing).
Reclamation processing consolidates the remaining active data from multiple sequential access
volumes onto fewer volumes.
Reclaimed cartridges, those which were the source of reclaimed data, are essentially untouched
by reclamation but are made available (scratched) for later reuse. The TSM reclaimed data
is copied to a new cartridge, but none of this data will be deduplicated. The TSM reclaimed
data is shown in the user interface as “Disabled, Unsupported and Overhead Data” on the
System Capacity
screen (
System
>
Chassis
>
Deduplication
>
System Capacity
).
The TSM default reclamation threshold should be set to at least 90% or higher. If you run
reclamation, reclaimed backups are expanded and subsequent backups are not deduplicated
against them. For example, with the default reclamation threshold at 90%, 10% of the data
will not be deduplicated.
You should run reclamation outside of the backup window because it reduces processing
bandwidth. The reclamation process is very device-intensive and requires at least two available
drives in the library (to read and to write). You must increase the amount of available capacity
for the retention period of the reclaimed backup data.
Firmware Version 6.0
Mount retention: Changing the mount retention is now optional, and can be left at the default 60
minutes (it will just delay the start of deduplication). For optimum behavior you can change the
mount retention to five minutes for your server configuration.
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
stgpool_name in (select stgpool_name from stgpools where
pooltype='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
pooltype='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
IBM TSM
147