The PHBs want to move the whole shebang over to the new server and then worry about other stuff later. We've told them a dozen times that this won't necessarily work, but they think it's a simple copy/mapping/renaming operation. The new server has two hard drives and the only thing on it right now is the o.s.
We were thinking that we'd like to back up the old server's data to tape and then move it to the new server, but one PHB called that notion "half-baked." We also thought about using Amanda but it would be a bit more complex and a learning process all the way through. Full disclosure: I've used RH from 6.2 through 9.0 and Core 5 on desktops but only recently completed RH 133 admin training (toward the RHCT) and am now thought to be a Linux guru, although this is my first production environment running it. Dave Hardy Old VMS Guy On 12/1/06, Thomas Charron <[EMAIL PROTECTED]> wrote:
If I'm reading the original poster correctly, he doesnt want to move the entire installation to the new server. He wants to upgrade the system to use the new release of the OS, and somehow get a listing of files that have been modified or changed since the original install, as he has no idea where people placed scripts, what they do, where they're called from, etc.. Look paul, I'm TOP posting! :-) On 12/1/06, Dave Peter <[EMAIL PROTECTED]> wrote: > > Are these Raid? or just single disk? > If only single, try to use Symantec ghost and should > work. Otherwise, if you have veritas backup, use the > backup and restore. Backup your old one and restore to > the new one. > > -- > Dave > > --- David Hardy <[EMAIL PROTECTED]> wrote: > > > Greetings, all; > > > > We have an older (and ailing) Dell PowerEdge 6300 > > running RH 9.0 and > > overloaded with a ton of (no-longer-sold and barely > > supported) Telemation > > phone system software. This machine is currently > > part of our network. > > > > We just bought a new Dell PowerEdge 860 and it came > > installed with RHEL 4.0. > > This box connects to the internet dynamically and > > they would like us to > > migrate the whole can of worms from the old box to > > the new one and then fix > > stuff, if necessary, afterward. It has been > > explained at least a dozen > > times to them that the process is not as simple as > > what they call "copying" > > or "mapping" directories to the new machine; there > > are site-specific > > scripts and files all over the old box written by > > several people over the > > years who have since left and never documented > > anything that they did (never > > enforced by same management that is on us like white > > on rice now to get this > > thing done.) > > > > I was wondering if anyone else here has faced this > > sort of situation before > > and how they dealt with it. > > > > Dave Hardy > > Old VMS guy > > > _______________________________________________ > > gnhlug-discuss mailing list > > gnhlug-discuss@mail.gnhlug.org > > > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > > > > > > > > ____________________________________________________________________________________ > Yahoo! Music Unlimited > Access over 1 million songs. > http://music.yahoo.com/unlimited > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ > -- -- Thomas
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
