[8362] in Info-AFS_Redistribution
Re: Replication volume swaps
daemon@ATHENA.MIT.EDU (Steve Lammert)
Fri Dec 29 11:58:23 2000
Message-ID: <3A4CBB2F.F2C33FD7@MARS-SYSTEMS.COM>
Date: Fri, 29 Dec 2000 11:26:23 -0500
From: Steve Lammert <shl@mars-systems.com>
MIME-Version: 1.0
To: Jeff Blaine <jblaine@linus.mitre.org>
CC: Mitch Collinsworth <mitch@ccmr.cornell.edu>, info-afs@transarc.com
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Jeff Blaine wrote:
>
> > - vos addsite to define a new r/o volume location
> > - vos release to clone the r/w to all r/o's
> > - vos remove to remote the old r/o
>
> So, now my question is (to you and the other person who replied with the
> same info): Why is 'vos remsite' never used in your solution?
Answer: It should have been.
vos remsite to remove the old r/o location from the VLDB
vos addsite to define the new r/o location in the VLDB
vos release to write new data to the disk
Then you can use "vos remove" to delete the old clone from the disk at
your leisure. Actually, I think at one time it was necessary to use
"vos zap" ...
--
steve lammert | medical archival systems, inc. (a/k/a MARS)
systems analyst v | 1370 beulah road | pittsburgh, pa 15235-5084
shl@mars-systems.com | v: 412-473-6544 | f: 473-6538 | c: 310-3406
