Answering only your questions 3, 3b, and 4...
For the remote database backups at least, your RS can become a client of
the MS, and can back up its database to the MS. From the MS perspective,
the RS is just a regular backup/archive client doing an archive
operation on a rather big file. The MS stores those DB backups in its
storage pool heirarchies just like any other archive files for a client
node, including expiring them when they're no longer needed. It's
actually better to back up your DB to another TSM system, rather than
backing it up to local tape, because it uses far fewer tape volumes by
stacking multiple DB backups on a single tape.
This setup is fairly well described in the TSM Admin Guide. Evaluate it,
however, in terms of disaster recovery - you cannot lose both TSM
servers at once, so the two should not be in the same location.
I know I am still leaving your first 2 questions unanswered.
Roger Deschner University of Illinois at Chicago rogerd AT uic DOT edu
On Mon, 20 Oct 2003, Curt Watts wrote:
>Alright, time to ask the experts!
>
>Essentially, I'm trying to have our remote TSM servers (satellite
>locations) utilize the main TSM server as the next storage pool in it's
>hierarchy.
>
>The hierarchy will eventually look like this:
>
>Remote Server (RS) Disk Cache
> -Main Server (MS) Disk Cache
> -MS Tape Pool
> -MS Offsite Copy Pool
>
>Questions I have:
>1) Is this possible?
>2) Can I do this without the DR module?
>3) How does the RS backup it's database - because it won't backup to
>the local disk?
>3b) Should the RS backup it's DB directly to tape? and if so, how is it
>possible to share the tape library with no NAS?
>4) Should I just break down and put some tape drives out there to
>handle the DBs?
>
>Current setup:
> MS: W2k sp4, TSM v4.3.2, IBM 3853 w/ 54 slots & 2 LTO drives.
> RS: W2k sp4, TSM v5.2.0
>
>Thanks everyone.
>
>Curt Watts
>
>_______________________________________________
>Curt Watts
>Network Analyst, Capilano College
>cwatts AT capcollege.bc DOT ca
>
|
