Not really answering your question (sorry), but have you thought about client side de-dupe and backing up to a TSM instance in your main DC?
For something that small, I'd look to a local TSM server as a last resort. Steven On 22 March 2012 16:29, Bob Levad <[email protected]> wrote: > Greetings! > > I'm looking at building a very small TSM environment to support a remote > site. > > Since there are only a couple of terabytes of data and the change rate > should be only a few hundred gig per day, what I'm thinking of is a TSM > server with about 5TB of internal storage for onsite deduped file pools. > > For offsite, I want to use bare SATA drives as removable file volumes (not > deduped). > > For the initial proof of concept, I'd use an inexpensive SATA dock with > 3.5 inch 1TB or 2TB drives for the offsite copy volume and small (100GB or > so) 2.5 inch drives for the data base backups. > > These drives would go offsite in plastic drive sleeves daily and reclaims > would run from the onsite pools. > > I've found a little about using removable file pool volumes, but I wanted > to run this by the experts to see what others may have tried. > > For disaster recovery, it might be nice if all the drives could be mounted > in an enclosure (I don't think there will be over about a dozen offsite > volumes) -- Maybe a Promise SAN in JBOD mode or something that can be used > with bare drives. > > Bob > This electronic transmission and any documents accompanying this > electronic transmission contain confidential information belonging to the > sender. This information may be legally privileged. The information is > intended only for the use of the individual or entity named above. If you > are not the intended recipient, you are hereby notified that any > disclosure, copying, distribution, or the taking of any action in reliance > on or regarding the contents of this electronically transmitted information > is strictly prohibited. >
