Uh. The below is a really bad idea!
During the time between the first and completion of the third step, your
users won't be able to access the data reasonably, since the readonly volume
won't exist any more in the vldb. Always create the new one first, then
remove the old one.
-- Nathan
> -----Original Message-----
> From: Steve Lammert [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 29, 2000 10:26 AM
> To: Jeff Blaine
> Cc: Mitch Collinsworth; [EMAIL PROTECTED]
> Subject: Re: Replication volume swaps
>
>
> 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
> [EMAIL PROTECTED] | v: 412-473-6544 | f: 473-6538 | c: 310-3406
>
