Christopher D. Clausen a écrit :
thank you for this solution, I will keep it in mind but for now I would prefere a solution where I have two servers living side to side to be 100% sure that he new one is functional before directing clients to itGérald Macinenti <[EMAIL PROTECTED]> wrote:Christopher D. Clausen a écrit :Gérald Macinenti <[EMAIL PROTECTED]> wrote:yes, this is the best way to describe it, two differents servers with just happen to have the same cell name, my goal is to replace the old by the new one, so I kept the cell nameThe correct solution would be to make both servers members of the same cell by copying the KeyFile from the original one to the new one. And then restart the server processes and vos move from one to the other.but both servers have there own root.cell, wouldn't it be an issue? and then which vldb would retain the information of moving the volume ? and concerning the Keyfile: both servers use their own kerberos server (as I migrate this one in the process too)Are the root.cell volumes different between the two servers? If you aren't doing a full migration, than copying data manually might be the best answer.Their own Kerberos server? What does that mean? You set up an additional Kerberos realm with the same name as well? Did you actually migrate the Kerberos KDC? Or did you just setup a new one?Is there a particular reason you don't want the two servers to communicate?yes: the fear to render my old server unusable as I don't master all the consequences of doing so ;)Adding a server with just an fs instance should not cause any problems. You will want to remove all volumes on the new server and follow the instructions for adding additional fileservers to a cell. Once the fileserver is up, vos move the data to it. You can then go through the process of adding this machine as a full AFS DB server to migrate your pt and vl databases from the old server. Once up, you can then remove things from the old server and change the IP address on the new one to match the IP address of the old one.
I do it because we want to completely upgrade this server (hardware, Linux distribution and of course softwares versions) so I took the options to build a new server from scratch and only migrate AFS data.Can I ask why you are doing this? Its going to be quite a hassle, especially if your cell only has a single AFS DB server. If you need to keep the cell up while doing the migration, I'd stringly recomend having at least 3 AFS DB servers.
So the situation is I have two Kerberos/AFS with the same configuration, but with AFS volumes (and vldb) only on the old one
-----In theory, restoring the dumps should work. You need to ensure that the PTS database is the same between the two servers as well. I don't know why fs sa is crashing, but I suspect it has something to do with two different cells having the same name. Are you sure your test client is pointed at the correct server? The server and clients have different CellServDB files.
yes I'm sure and the PTS database is an exact copy of the old onewould it be an option to simply rsync AFS partitions *.vol from the old to the new server and then copy the vldb.* files from the old to the new server ?
would it be another option to have a simple fileserver added to both administrative servers (with the same cell name??) and migrate volumes with a vos move from old to this fs then move from this fs to new?
Cheers -- Gérald Macinenti - Admistrator / / ___ / /_ / _/ /_ | | / /___ __ _____ / / / _ \/ __/ / // __/ | | /| / / __ `/ | / / _ \ / /___/ __/ /_ _/ // /_ | |/ |/ / /_/ /| |/ / __/ /_____/\___/\__/ /___/\__/ |__/|__/\__,_/ |___/\___/ 8-16, rue Paul-Vaillant-Couturier, 92240 Malakoff; FRANCE Tel +33 1 4092 5454 - Fax +33 1 4092 5441 - http://www.letitwave.fr
smime.p7s
Description: S/MIME Cryptographic Signature
