Think about it this way, each file that is backed up or archived has an
impact to the TSM db. Similarly an image has the same impact to the
database as a file. So rather than having 50,000,000+ entries into the
database (one for each file), you only have one entry for the entire
image. The image impact to the database is negligible at best. Another
plus is the speed of the image process, in my operation it takes about
1/5 of the time to image compared to backup. As far as storage it
obviously needs to go to a primary pool, tape or otherwise. Assuming you
only need one copy the ideal situation would be a primary tape pool with
no copy pool. 


~Rick


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
sanman2010
Sent: Thursday, November 04, 2010 2:25 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM Archiving 50tb data with millions of files

Thanks Rick, i was going to try an image backup, but was unsure of the
impact to the db, would you recommend straight to LT05 or diskpool first
then migrate to tape, since these are going to be kept for long term
storage?

B.

+----------------------------------------------------------------------
|This was sent by largo_inc AT yahoo DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------