Shawn,
   We are in the same boat - 30TB of user data on NetApp and required to
keep all daily backups for 7+ years.  NDMP proved to be too much hassle
- it is not incremental it is differential requiring periodic full
backups.  I have 2 TSM servers pretty much dedicated to these backups -
not for the data throughput but for DB size - one is 75G and the other
is 300G (bad form I know, no comments please...)

We have a few virus scanning machines which also perform backups of the
individual CIFS shares - some using snapdiff some not.  Recover of
individual files is very straightforward.  Large scale recovery - i.e.
multiple filesystems or the entire filer is not really an option from
TSM due to RTO limits.  We use a combination of snapshots and mirroring
for these DR type of scenarios (actually practice a full failover and
failback twice a year also - successfully!)


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
Shawn Drew
Sent: Wednesday, March 09, 2011 1:46 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Long term archiving solutions for file servers

We have a weekly archive requirement for our Netapp file servers and are
using TSM NDMP for this.  My opinion is this is one of those "misusing
backups as an archive" situations and I want to change this.

We are looking at 100-150TB a week with LONG term retention and I'm not
sure what options are available.  I first considered using the snapdiff
option, which would give us the ability to spin off new TSM instances as
needed and enable TSM incremental backups.  But it seems to be there
should be a better method, I just don't know what it is.

Any other options out there?

Regards,
Shawn
________________________________________________
Shawn Drew


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in
error,
please delete it and immediately notify the sender. Any use not in
accord
with its purpose, any dissemination or disclosure, either whole or
partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall
(will)
not therefore be liable for the message if modified. Please note that
certain
functions and services for BNP Paribas may be performed by BNP Paribas
RCC, Inc.

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.