[ Rick Cochran had written regarding vldb strangeness... ]

Hm.  Our AFS db servers (umich.edu production cell) don't even *have*
a /usr/afs/local/sysid file.  I can't find any mention of such a file
in our copy of the AFS source either.  What's in it?  Any idea what uses
it?  What version of AFS are you running anyways?  What version of AIX?

If I were doing such a move, there are about two possibilities:

(1) the 530 & C20 are running the same revision of the OS, and can
understand the same physical filesystem.

        In this case, what I'd do would be to
                configure the C20 as a "blank" fileserver/db server.
                        all fileserver binaries, empty db files.
                shut the 530 down
                attach & configure the drive to the C20
                configure the C20 to the same IP address
                        as the 530
                bring it up.  The db files should be automatically
                        propogated to the C20 from other DB servers,
                        and the fileserver should be happy.
        The win here is that by reusing the same drive & physical
                files, the whole process could be quite quick.
        Based on your experience, of course, I'd wonder if this was
                entirely right.  Perhaps there's something strnage
                in those "uuid"s in the latest vldb format that isn't
                quite kosher.

(2) the 530 & C20 aren't filesystem compatible.  Two options here.

        Option 1. (if you have a spare disk)
                shut the 530 down.
                use "vos changeaddr" to change the IP address
                        of the 530 in the vldb to something temporary.
                change the 530's IP address, & restart it.
                configure the C20 as a "blank" fileserver/db server.
                        all fileserver binaries, empty db files.
                install a new empty disk on the C20
                give the C20 the the DB IP address.
                bring the C20 up.
                        db files will propagate from the other servers.
                Use "vos move" to move everything from the
                        530 to the C20.
                shut the 530 down.
        Option 2. (if you don't have a spare disk)
                dump everything on the 530 to tape.
                decommission the 530
                bring the C20 up in place of the 530.
                        (all server binaries, 
                        no db files,
                        newly reformatted drive from 530)
                restore everything from tape.

(Backups, both of all the files on the fileserver, & the db files, would
be a good idea, in any event.  pt+vl+ka aren't all that big, and are
definitely worth keeping backed up.)

What you went through sounds painful, though.  4G of data isn't
much fun to restore under the best of circumstances.

                                -Marcus Watts
                                UM ITD PD&D Umich Systems Group

Reply via email to