This sounds like a great idea to separate the tape pools.. Thanks... However
I also created the separate Domains due to a shortage of a backup up window.
I am now able to place the servers that are able to be backup up during the
day into their own Domain and give it a start time for those backups. This
saves me from creating a new schedule for each server and eliminates guess
work from my part.
Thanks for the idea. I might resort to this with the remaining servers
(other than my DRP)
Joe Cascanette
-----Original Message-----
From: Warren, Matthew James [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 09, 2001 12:07 PM
To: [EMAIL PROTECTED]
Subject: Re: Moving Nodes to a different domain
Joe,
We had a similar idea for DR Tests as we have several different customers
using the same TSM silo. I initially looked at co-location but this
generates other problems with offsite copy pools.
The only way I know to do it is have separate storage pool hierarchies for
each group of servers that are backing up - you don't _have_ to have them in
separate domains if you specify managment classes for the client data that
point the data to different storage pools. You end up with a separate
disk/tape/copy pool for each 'collection' of servers.
We didnt do this in the end either - we have decided to keep the TSM setup
simple and operator performed tape movements simpler, and move all the
offsite tapes to DR sites when needed.
Matt.
_______________________________
Matthew Warren. GZPTXW
EDS Core Infrastructure,
UK Technical Services Group,
Wavendon Tower, Milton Keynes.
+44(0)1908284481
_______________________________
> -----Original Message-----
> From: Joe Cascanette [mailto:[EMAIL PROTECTED]]
> Sent: 06 July 2001 20:55
> To: [EMAIL PROTECTED]
> Subject: Re: Moving Nodes to a different domain
>
>
> Thanks... I have the domains setup for separate storage pools
> (357pool's and
> copy pools), however they all go the same archive pool for
> monthly backups.
>
> I guess the import/export is the only way to go then.
>
> Take care..
>
> Joe
>
>
> -----Original Message-----
> From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 05, 2001 3:08 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Moving Nodes to a different domain
>
>
> Domains don't necessarily have their own tapes.
>
> Domains have policy sets.
> Policy sets have management classes.
> The management classes have backup copy groups.
> The backup copy group points to a storage pool.
>
> The storage pool may be disk or tape.
> That's where the data goes.
> So you can have all domains pointing at the same pools or
> different pools.
>
> If you move a client to a different domain that DOES point
> the data to a
> dedicated storage pool, it still only affects NEW data. The already
> backed-up data stays where it is.
>
> Export/Import is the only way I can think of to actually move
> the data.
>
>
> -----Original Message-----
> From: Joe Cascanette [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 05, 2001 9:01 AM
> To: [EMAIL PROTECTED]
> Subject: Moving Nodes to a different domain
>
>
> I have setup some separate domains and have moved the nodes
> to them, however
> I am under the impression that the separate Domains will have
> their own
> tapes, how do I move the file space?. Yes the file space
> shows up in the new
> Domain under the node, however there is no process that
> starts to actually
> move the data into to separate tapes. I have looked into the
> import/export
> features, but it is a long process.
>
> No luck searching the Tivoli site.
>
> Joe
>
