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

Firmware Version 3.4

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

The more data you collocate, the fewer tape mounts are required during restores. The downside is that you will significantly increase the amount of tapes you use. Deduplication does not support co-location because this feature is unnecessary when using a disk-based backup solution. • NDMP backup: Deduplication does not currently support LAN-free NDMP with TSM. This means you can only backup an NDMP filer over the LAN to the VLS. • Oracle RMAN Scripting: See Oracle RMAN Scripting for details. • Virtual volumes: TSM allows one TSM server to store its data on another TSM server. The TSM server that sends the data to be stored on the other server is the source server, and the server that stores the received data is the target server. With virtual volumes, the source server treats the target server like a tape library, and the target server treats the source server as a special type of client node. Deduplication does not support TSM virtual volumes. Firmware Version 3.4 • Incremental forever: The TSM (Tivoli Storage Manager) "incremental forever" scheme of backups are all effectively treated as full backups by the deduplication, so every new backup is compared against the previous backup. With file server backups that contain just the modified files, this may result in lower deduplication ratios because most or all of the new backup data is unique, but database backups (which are normally the entire database every time) will give normal deduplication ratios. • Mount retention: You must set the mount retention to 0 (zero) for your server configuration as follows: dsmadmc -id=admin -pass=admin update devclass mountret=0 Substitute the password for "admin" above with your TSM server admin password. • Management classes: To assign a management class other than the default to all files, use an include statement in your client systems options file, or by using an include-exclude file specified by the "inclexcl" option. To specify your own default management class for files that are not explicitly included, specify the following as the first include or exclude option defined: For non-Windows hosts (such as HPUX, Linux, and AIX), add the following to the dsm.sys file for the appropriate directories being backed up: ◦ This will backup all directories and files under /backup/: include /backup/.../* mgmt_class_name ◦ This will backup all directories and files under /: include /.../* mgmt_class_name For Windows hosts, to specify a management class named mgmt_class_name for all files to which you do not explicitly assign a management class, add the following to the dsm.opt file for Windows systems for the appropriate volumes/directories being backed up: ◦ This will backup all directories and files under e:\backup: include e:\backup\...\* mgmt_class_name ◦ This will backup all directories and files under e:\: include e:\...\* mgmt_class_name ◦ This will backup all directories and files under d:\: include d:\...\* mgmt_class_name The management class names are not case-sensitive. 146 VLS Configuration and Backup Application Guidelines

  • 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 more data you collocate, the fewer tape mounts are required during restores. The downside
is that you will significantly increase the amount of tapes you use.
Deduplication
does not
support co-location because this feature is unnecessary when using a
disk-based backup solution.
•
NDMP backup: Deduplication
does not
currently support LAN-free NDMP with TSM. This
means you can only backup an NDMP filer over the LAN to the VLS.
•
Oracle RMAN Scripting: See
Oracle RMAN Scripting
for details.
•
Virtual volumes: TSM allows one TSM server to store its data on another TSM server. The TSM
server that sends the data to be stored on the other server is the source server, and the server
that stores the received data is the target server. With virtual volumes, the source server treats
the target server like a tape library, and the target server treats the source server as a special
type of client node.
Deduplication does
not
support TSM virtual volumes.
Firmware Version 3.4
•
Incremental forever: The TSM (Tivoli Storage Manager) "incremental forever" scheme of
backups are all effectively treated as full backups by the deduplication, so every new backup
is compared against the previous backup. With file server backups that contain just the modified
files, this may result in lower deduplication ratios because most or all of the new backup data
is unique, but database backups (which are normally the entire database every time) will give
normal deduplication ratios.
•
Mount retention: You must set the mount retention to 0 (zero) for your server configuration as
follows:
dsmadmc -id=admin -pass=admin update devclass <vtlclass> mountret=0
Substitute the password for “admin” above with your TSM server admin password.
•
Management classes: To assign a management class other than the default to all files, use an
include statement in your client systems options file, or by using an include-exclude file specified
by the “inclexcl” option. To specify your own default management class for files that are not
explicitly included, specify the following as the first include or exclude option defined:
For non-Windows hosts (such as HPUX, Linux, and AIX), add the following to the
dsm.sys
file for the appropriate directories being backed up:
◦
This will backup all directories and files under
/backup/
:
include /backup/.../* mgmt_class_name
◦
This will backup all directories and files under
/
:
include /.../* mgmt_class_name
For Windows hosts, to specify a management class named
mgmt_class_name
for all files
to which you do not explicitly assign a management class, add the following to the
dsm.opt
file for Windows systems for the appropriate volumes/directories being backed up:
◦
This will backup all directories and files under
e:\backup
:
include e:\backup\...\* mgmt_class_name
◦
This will backup all directories and files under
e:\
:
include e:\...\* mgmt_class_name
◦
This will backup all directories and files under
d:\
:
include d:\...\* mgmt_class_name
The management class names are not case-sensitive.
146
VLS Configuration and Backup Application Guidelines