Ken,
   If the N-series is providing CIFs shares, you should consider backing
up with a windows server mounting the shares and then using the
"-snapdiff" option in TSM V6 client.  This greatly simplifies recovery
as it is nearly identical to regular client recoveries.

   NDMP backups are full/differential and do not take advantage of the
incremental forever philosophy of TSM.  If you are using LUNs mounted to
a database server running DB2 or Oracle you may want to look into TDP
for Snapshot Devices/TSM for Advanced Copy Services.


   With NDPM backups, you must specify a specific file name to backup.
Wildcards are not accepted.  If you take a snapshot you must create the
virtualfsmapping to that specific snapshot name.
E.g.
define virtualfsmapping netapp1 /exc1_sg1_logs.snap__recent
/vol/exc1_sg1_logs /.snapshot/exchsnap__recent
*Note the full path name to the snapshot file "exchsnap__recent" in the
virtualfsmapping.   This file MUST exist in order to perform a backup.

I think you would have difficulty backing up the non-qtree portion of a
volume because this would imply a top level backup which would contain
the sub level q-trees by default.  You may be able to specify the volume
and use exclude statements to ignore the q-trees.  It looks like it can
get pretty messy on the restore though.

You probably also want file level recovery so be sure to define a TOC
storage pool for the NDMP backup

Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Mueller, Ken
Sent: Tuesday, June 16, 2009 1:06 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] NDMP backup of non-qtree data

We have an IBM N-Series 6040 (a thinly veiled NetApp 3140) that amoung
other things contains several large volumes (2TB, 35 million files).
These volumes have qtrees defined for the larger top-level directories.
There are numerous other small top-level directories that are not in
qtrees.

We are running TSM 5.5.2.0 and using the Filer->TSM->Library method of
NDMP backup (storing the backups in TSM native storage pools).

It is not practical to backup the entire volume in one shot, but backing
up the individual qtrees via BACKUP NODE is manageable.  The problem
that I have is how to specify backing up the non-qtree portion of the
volume.  The NetApp commands use a trailing dash after the volume name
to indicate non-qtree data (ie:  /vol/xyz/-  ) however BACKUP NODE
complains of an invalid parameter when I use that convention.  I tried
setting up a virtualfsmapping with the trailing dash and it is accepted
for the mapping, however the subsequent BACKUP NODE process fails after
it starts with an ANR9999D catchall: "Error beginning NDMP backup -
illegal arguements.Check that the filespace/path '/vol/xyz/-' exists."

Anybody backing up these filers at the qtree level?  How do you handle
the non-qtree data?

We're new to the whole NDMP world - seems a few steps back from what TSM
can do natively.  Any sage advice is welcome!

-Ken Mueller

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.