Juha Jäykkä wrote:
No, actually, it's "if you want to run old servers, have fun"
Ok. I am now moving to 1.4.1 clients, but the servers need a little more
care. Is the procedure as simple as one would wish:
1) shut down *one* server (file or db)
2) install new version on it
3) restart
4) repeat steps 1-3 for every server, one at a time?
If it's as simple as that and there is guaranteed (sic!) to be no data
loss, I'll take that path probably even before the new server arrives.
Can't guarantee anything in this business (*)
But I have done it several times now. Three servers, 1.2.11 -> 1.4.0,
and then later 1.4.0 -> 1.4.1. In the first case, the servers were done
several months apart.
I tried to minimize the impact by migrating most of the volumes off the
server before each upgrade, so users were not impacted at all.
Obviously, that requires having sufficient free space and time to move
the data around between upgrades.
Steve
(*) I did one server from home late on Saturday, but because I was also
upgrading the kernel at the same time, rebooted after putting the new
version in place. The system never returned! I had to come into work
the next day just to hit F5 to acknowledge the RAID controller's
complaint about a failing disk in the RAID-5 array. Good thing I moved
the users' volumes off first.
-----------------------------------------------------------------------------
Stephen G. Roseman
Lehigh University
[EMAIL PROTECTED]
_______________________________________________
OpenAFS-info mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-info
