Subject: | |
From: | |
Reply To: | |
Date: | Tue, 7 Jan 1997 11:51:43 +0100 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Jerry Fochtman wrote:
>
> At 08:58 AM 1/6/97 -0500, Mikolai Jeff wrote:
> >You can absolutely build groups across
> >volume sets.
> >
> >An easy way to see if your group is part of
> >the account volume set is to do a simple
> >listgroup @.account.
> >
> >NOTE: The group can ONLY reside on 1 volume
> > set.
>
.. we should add "at one point in time" here.
It is absolutely possible to have two groups with the same
name on 2 different NON system volumesets (or user volume
sets) and "switch" back and forth, by changing the "pointer"
in the system volumeset's directory with the
ALTGROUP ;HOMEVS command.
Of course only one of these groups can be accessed at any
given time. Situations where this comes in "handy" could
be, if you want to access older versions from your files
on a backup, without having to deal with new names, or "swapping"
the production versions out to tape and back.
_If_ you have spare disks for another volumeset of course, and if
you have a timewindow, where the "non-accessibility" of your
normal production files is non-problematic.
Hope this helps more than it confuses,
Goetz.
|
|
|