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

Fully-optimized RMAN Configuration for TSM

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 153 highlights

The deduplication-optimized RMAN settings: FORMAT 'df.%d.%f.' for each data file FILESPERSET 1 MAXOPENFILES default Number of channels does not impact deduplication performance, but does impact backup performance so consider increasing the number of channels while maintaining concurrency at 1) CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F'; Compression off Encryption off Fully-optimized RMAN Configuration for TSM For larger or more complex Oracle (version 10 or higher) databases, the following RMAN changes can be used to provide fully optimized deduplication for TSM with firmware version 3.4 and higher, though the required changes are simplified for version 6.0 and higher. For version 3.4 with TSM, to get optimum Oracle deduplication you can customize your RMAN scripts to add the additional FORMAT information (for data files use FORMAT 'df.%d.%f.'), but with version 6.0 and higher this FORMAT change is no longer required. With both versions 3.4 and 6.0, you must still disable multiplexing. The deduplication-optimized RMAN settings: Version 3.4 only: FORMAT 'df.%d.%f.' for each data file Versions 3.4 and 6.0: FILESPERSET 1 (optional on version 6.0 but if you set this to greater than 1 you must set MAXOPENFILES to 1 MAXOPENFILES default Number of Channels defined in RMAN must equal the maximum number of mount points as defined for your system CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F'; Compression off Encryption off Oracle RMAN Scripting 153

  • 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
The deduplication-optimized RMAN settings:
FORMAT 'df.%d.%f.<other_identifiers>'
for each data file
FILESPERSET 1
MAXOPENFILES default
Number of channels does not impact deduplication performance, but does impact backup
performance so consider increasing the number of channels while maintaining concurrency at 1)
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE
‘
SBT_TAPE
’
TO
‘
%F
’
;
Compression off
Encryption off
Fully-optimized RMAN Configuration for TSM
For larger or more complex Oracle (version 10 or higher) databases, the following RMAN changes
can be used to provide fully optimized deduplication for TSM with firmware version 3.4 and higher,
though the required changes are simplified for version 6.0 and higher. For version 3.4 with TSM,
to get optimum Oracle deduplication you can customize your RMAN scripts to add the additional
FORMAT information (for data files use
FORMAT 'df.%d.%f.<other_identifiers>'
), but
with version 6.0 and higher this FORMAT change is no longer required. With both versions 3.4
and 6.0, you must still disable multiplexing.
The deduplication-optimized RMAN settings:
Version 3.4 only:
FORMAT 'df.%d.%f.<other_identifiers>'
for each data file
Versions 3.4 and 6.0:
FILESPERSET 1
(optional on version 6.0 but if you set this to greater than 1 you must set
MAXOPENFILES to 1
MAXOPENFILES default
Number of Channels defined in RMAN must equal the maximum number of mount points as defined
for your system
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE
‘
SBT_TAPE
’
TO
‘
%F
’
;
Compression off
Encryption off
Oracle RMAN Scripting
153