Author: "Grendelman M. (Martijn)" <Martijn.Grendelman AT NL.FORTIS DOT COM>
Date: Thu, 16 Sep 1999 11:54:51 +0200
Hi all, Currently we have one big tape pool for our Netware backups. Now we want to split this pool in two, with collocation turned on for one of the new pools and turned off for the other. From ther
Author: James SPORER <james.sporer AT CCMAIL.ADP.WISC DOT EDU>
Date: Thu, 16 Sep 1999 09:14:32 -0600
I would just leave the data in the non-collocated pool and start backing up to the collocated pool. Eventually the data in the non-collocated pool will expire and things will be collocated. Your orig
Why do you think you need collocation? Collocation can put a strain on something you do everyday (backup) while offering perhaps a faster restore (something you don't do everyday). Are your restores
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:39:21 -0500
I would just leave the data in the non-collocated pool and start backing up to the collocated pool. Eventually the data in the non-collocated pool will expire and things will be collocated. Your orig
Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
Date: Fri, 17 Sep 1999 08:56:14 -0700
I did the same thing a couple of years ago. I created the new storage pool and exported the smaller nodes data one at a time to the new pool (The larger node would have taken too long to export) afte
My understanding of collocation is that if ADSM can't find a scratch tape or empty volume for a collocated pool, it will put data on an existing tape, essentially doubling up clients onto tapes. Is t