Topic: version update procedure

[David Woolley]

Hi

I am planning to start replacement servers with the current release, which I think is v5.6u3.

I have downloaded and will install the plain vanilla v5.6

When I'm done, can I simply apply update 3 to this, or must I apply updates 1 & 2 before running update 3?

I haven't replaced a server before, but I'm supposing that regarding my configuration and data, I can make a backup to desktop of my old server (v5.5u2) and restore this to the new box.  

Am I right that all settings like ip addresses, domain name, user accounts etc etc will be overwritten in the restore process.  If so, can I just enter blah blah blah during the new v5.6 install?

Many thanks

David

[jb]

All you should have to do is apply update 3.  In the update 3 directory, all of the files from update 2 are there as well.

[jb]

All you should have to do is apply update 3.  In the update 3 directory, all of the files from update 2 are there as well.

[Bill Talcott]

Update 1 was included in the Unsupported ISO - you can't install it separately. And yes, updates are cumulative unless that's impossible. For example, there was a bug in the update process of 5.0 that was patched in Update 4, so you had to install that before you could install the later updates.

[Ray Mitchell]

David
It should not matter what configuration you enter when you instal v5.6 as it will be overwritten by the restore process. Of course you may still need correct (appropriate) values to allow access to your new server initially.

You should Verify your backup file to ensure it is a good backup before trashing the old server though. If you have not done it before, you may want to do a test restore on a test server first.
Note if your backup file is bigger than 2Gb you will have problems using the backup to desktop function (and restore). You may want to look at Darrell Mays backup2ws.
Regards
Ray Mitchell

[David Woolley]

Thanks very much guys.

I have installed Darrell's backup2ws, which seems to be doing the business.  A backup is in progress now.

However, in the server-manager messages log, I am seeing:
*********************

Apr 14 14:02:31 cochrane kernel: floppy0: floppy timeout called
Apr 14 14:02:31 cochrane kernel: end_request: I/O error, dev 02:0c (floppy), sector 2
Apr 14 14:02:36 cochrane kernel:
Apr 14 14:02:36 cochrane kernel: floppy driver state
Apr 14 14:02:36 cochrane kernel: -------------------
Apr 14 14:02:36 cochrane kernel: now=25504465 last interrupt=25504375 diff=90 last called handler=c0193f28
Apr 14 14:02:36 cochrane kernel: timeout_message=floppy start
Apr 14 14:02:36 cochrane kernel: last output bytes:
Apr 14 14:02:36 cochrane kernel:  8 80 25503956
Apr 14 14:02:36 cochrane last message repeated 2 times
Apr 14 14:02:36 cochrane kernel: 12 80 25503956
Apr 14 14:02:36 cochrane kernel:  0 90 25503956
Apr 14 14:02:36 cochrane kernel: 13 90 25503956
Apr 14 14:02:36 cochrane kernel:  0 90 25503956
Apr 14 14:02:36 cochrane kernel: 1a 90 25503956
Apr 14 14:02:36 cochrane kernel:  0 90 25503956
Apr 14 14:02:36 cochrane kernel:  3 90 25503956
Apr 14 14:02:36 cochrane kernel: c1 90 25503956
Apr 14 14:02:36 cochrane kernel:  8 90 25503956
Apr 14 14:02:36 cochrane kernel:  7 80 25503956
Apr 14 14:02:36 cochrane kernel:  0 90 25503956
Apr 14 14:02:36 cochrane kernel:  8 81 25504165
Apr 14 14:02:36 cochrane kernel:  7 80 25504165
Apr 14 14:02:36 cochrane kernel:  0 90 25504165
Apr 14 14:02:36 cochrane kernel:  8 81 25504375
Apr 14 14:02:36 cochrane kernel:  7 80 25504377
Apr 14 14:02:36 cochrane kernel:  0 90 25504377
Apr 14 14:02:36 cochrane kernel: last result at 25504375
Apr 14 14:02:36 cochrane kernel: last redo_fd_request at 25504165
Apr 14 14:02:36 cochrane kernel: 70  0
Apr 14 14:02:36 cochrane kernel: status=81
Apr 14 14:02:36 cochrane kernel: fdc_busy=1
Apr 14 14:02:36 cochrane kernel: DEVICE_INTR=c0193f28
Apr 14 14:02:36 cochrane kernel: cont=c022e6c0
Apr 14 14:02:36 cochrane kernel: CURRENT=c02676a4
Apr 14 14:02:36 cochrane kernel: command_status=-1
Apr 14 14:02:36 cochrane kernel:
Apr 14 14:02:36 cochrane kernel: floppy0: floppy timeout called
Apr 14 14:02:36 cochrane kernel: end_request: I/O error, dev 02:0c (floppy), sector 4
Apr 14 14:02:41 cochrane kernel:
Apr 14 14:02:41 cochrane kernel: floppy driver state
Apr 14 14:02:41 cochrane kernel: -------------------
Apr 14 14:02:41 cochrane kernel: now=25504975 last interrupt=25504884 diff=91 last called handler=c0193f28
Apr 14 14:02:41 cochrane kernel: timeout_message=floppy start
Apr 14 14:02:41 cochrane kernel: last output bytes:
Apr 14 14:02:41 cochrane kernel:  8 80 25504465
Apr 14 14:02:41 cochrane last message repeated 2 times

*************************
and similar repeating.  My SME does not have a floppy, do I need to disable something?

Many thanks, as always

David