Curt,
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?
Yes, no problems - you create a DEVCLASS of type SERVER, then a storage
pool that
To: [EMAIL PROTECTED]
cc:
Subject:TSM Storage Pool Hierarchy Question
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
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
On Tuesday 21 October 2003 07:41, 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
I asked this question a while back but didn't get a reply.
A migration process from disk to tape will normally handle only one client's data per
migration process and hence only use one tape drive.
Since the virtual volumes on MS appear to come from a single client (RS), then this
data will
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
