Jeremy, Sorry it took so long for me to respond.
On Wed, 21 Jan 2004, Jeremy Rumpf wrote: [snip...] > From the TMS docs: Thanks! I asked out TSM folks here too, they came by with the manual. :) Slight difference, we use the backup / restore portion of TSM on our mail servers. It has the same paragraphs as the archive. :) [snip...] > So if you are using SSI, it seems that TSM will work the hard link magic for > you. And if it can't, it'll put down individual non-linked copies of the > files. This still could also lead to the situation where a selective restore > could end up utilizing more disk than the original files/links, but it looks > as if TSM tries harder than most to resolve things. Yes, it sounds like TSM will do the right thing. > Out of curiosity, how long does TSM take to run vs. the amount of mail data > you have? I've used TSM before, just not in this arena. We have a total of 12 spools on 4 different backend servers. The backups of the spools run concurrently, 3 per server, and TSM takes approx. 1 hour to backup the spools. Here is a sample report of 1 spool. Reporting imap.spool.07.log 01/22/04 23:02:38 01/22/04 23:02:38 Total number of objects inspected: 1,099,339 01/22/04 23:02:38 Total number of objects backed up: 25,000 01/22/04 23:02:38 Total number of objects updated: 0 01/22/04 23:02:38 Total number of objects rebound: 0 01/22/04 23:02:38 Total number of objects deleted: 0 01/22/04 23:02:38 Total number of objects expired: 15,234 01/22/04 23:02:38 Total number of objects failed: 8 01/22/04 23:02:38 Total number of bytes transferred: 1,014.87 MB 01/22/04 23:02:38 Data transfer time: 138.83 sec 01/22/04 23:02:38 Network data transfer rate: 7,485.20 KB/sec 01/22/04 23:02:38 Aggregate data transfer rate: 276.65 KB/sec 01/22/04 23:02:38 Objects compressed by: 0% 01/22/04 23:02:38 Elapsed processing time: 01:02:36 01/22/04:23:02:38 Dump of /ssa/imap/spool/07 completed. - Bill
