[1621] in SIPB-AFS-requests
Re: Avoiding rebuilding the VLDB
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Fri Nov 18 16:19:56 1994
To: ghudson@MIT.EDU
Cc: sipb-afsreq@MIT.EDU, usenet@MIT.EDU
In-Reply-To: Your message of "Wed, 16 Nov 1994 17:10:21 EST."
<9411162210.AA18229@maze.MIT.EDU>
Date: Fri, 18 Nov 1994 16:19:37 EST
From: Jonathon Weiss <jweiss@MIT.EDU>
>> Chad brought up an interesting point. We should be able to do avoid
>> rebuilding the VLDB and avoid causing any outages as follows:
>>
>> 1. Put the 4GB and 2GB disk on opus, bring it up as new-ronald-ann.
>> 2. Migrate ronald-ann data to new-ronald-ann.
>> 3. Remove ronald-ann from server CellServDBs, take it down.
>> 4. Bring up ronald-ann as new-rosebud.
>> 5. Migrate rosebud data to new-rosebud (leaving behind vlserver).
>> 6. Update client CellServDBs to point at 18.181.
>> 7. Swap names new-rosebud/rosebud and new-ronald-ann/ronald-ann
>> 8. Take down rosebud after a few weeks.
If we use this approach I would like to do it slightly differently.
1. Put the 4GB and 2GB disk on opus, bring it up as new-*rosebud*
2. Migrate ronald-ann data to new-*rosebud*
3. Remove ronald-ann from server CellServDBs, take it down.
4. Bring up ronald-ann as new-*ronald-ann*
5. Migrate rosebud data to new-*ronald-ann* (leaving behind vlserver).
...
This has the advantage that Ronald-ann gets to stay ronald-ann. There
are some paperwork advantages to this if nothing else.
When will opus be ready to be re-installed?
Jonathon
