Iain,
We have some very large volumes (1TB+) that have 10s of millions
of files. If we were to back them up using NDMP at the volume level, it
would take a long time and create a HUGE table of contents. TOCs for
NDMP are not kept in the database, but in a special disk pool. When you
want to restore an individual file from an NDMP, TSM has to read in that
TOC, which could take a long long time with these very large volumes.
By being able to go down to the q-tree level, we divide the
large volume into more reasonable chunks so that the NDMP backups don't
take as long and the TOCs may actually load in a reasonable time.
Ben
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Iain Barnetson
Sent: Tuesday, March 22, 2005 2:07 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3 new goody
Ben,
I'm kinda new to TSM & NetApp and I'm wondering what the advantages of
doing Qtree level backups are?
I do a NDMP backup of the filers complete which still allows me restore
right down to specific files.
Regards,
Iain Barnetson
IT Systems Administrator
UKN Infrastructure Operations
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Ben Bullock
Sent: 21 March 2005 16:30
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3 new goody
FYI...
I'm currently testing this new feature. The 'virtualfsmapping'
works great on normal NetApp qtrees. It's really the feature we have
been waiting for to go to NDMP with our filers and in testing we can get
NDMP backups at the qtree level or even lower.
The issue we are currently working through with support is that
this feature does not seem to work on our Snapmirrored volumes.
i.e. We have 11 NetApp filers that we snapmirror to a monster
R200 offsite for DR purposes. We are attempting to do NDMP backups off
of the snapmirrored volumes (using the virtualfsmapping to get Q-tree
level backups). We would much rather run the backups off the R200 than
the production filers.
TSM seems to be able to get the qtree backed up, but it fails to get a
TOC, which we really need.
We are still not sure it is a TSM or a NetApp problem, but I am
getting proficient in running both TSM and NetApp traces. ;-)
Ben
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Stapleton, Mark
Sent: Monday, March 21, 2005 9:17 AM
To: ADSM-L@VM.MARIST.EDU
Subject: TSM 5.3 new goody
(from the Windows Administrator's Guide, page 87)
Directory-Level Backup and Restore
If you have a large NAS file system, initiating a backup on a directory
level will reduce backup and restore times and provide more flexibility
in configuring your NAS backups. By defining virtual file spaces, a file
system backup can be partitioned among several NDMP backup operations
and multiple tape drives. You can also use different backup schedules to
back up sub-trees of a file system.
The virtual file space name cannot be identical to any file system on
the NAS node. If a file system is created on the NAS device with the
same name as a virtual file system, a name conflict will occur on the
Tivoli Storage Manager server when the new file space is backed up. See
the Administrator's Reference for more information about virtual file
space mapping commands.
Note: Virtual file space mappings are only supported for NAS nodes.
--
Mark Stapleton ([EMAIL PROTECTED])
Office 262.521.5627
