Hello
I work for a small S/W house (5 people). We have VERY little network traffic and no external links into our server. If the server was down for a few days it wouldn't be too critical. We have numerous tape backups and full HDD backups to a laptop. I was asked to build a standby server (I'm an A/P with no network or server O/S experience) to be used in the event of a disaster.
I've disconnected the standby server from the network and changed the computer name to be the same as the main server.
I've restored a full system backup and the system state from the main server in Directory Services Restore Mode as recommended by my reference book.
I still can't get the system up and running. Once the Win2K status bar reaches the right hand side of the screen the system reboots itself.
The hardware profiles are not identical. Is this critical ???? (Details below)
If I'm going about this the wrong way could somebody point me in the right direction please or suggest a better way to cater for disaster. I've spent 2.5 weeks trying to do this and I'm getting nowhere fast.
Please advise or help if you can.
Thank you
Keith
Main server
256MB RAM
800MHz AMD processor
1 x Std floppy (A
Adaptec AIC-788x/AHA-2940UW Pro SCSI controller
1 x SCSI ARCHIVE Python 0468-xxx DAT drive
3 x SCSI Seagate HDD 8GB each (C:, D:, E
1 x CDROM Creative 48 speed (F
1 x ATI 3D Rage Pro AGP Graphics
1 x HCF 56k modem
1 X Scanjet 440c
1 x HP Lasrjet 6P
Standby server
128MB RAM
300MHz Intel PII MMX
1 x Std floppy (A
Adaptec AHA-2940U/AHA-2940UW SCSI controller
1 x SCSI ARCHIVE Python 0468-xxx DAT drive
1 x IDE Maxtor HDD 32GB Partitioned (C
9GB), D
11.5GB), E
11.5GB))
1 x CDROM 56 speed (F
S3Trio 32/64 Graphics
No modem fitted
No scanner attached
No printer attached
I work for a small S/W house (5 people). We have VERY little network traffic and no external links into our server. If the server was down for a few days it wouldn't be too critical. We have numerous tape backups and full HDD backups to a laptop. I was asked to build a standby server (I'm an A/P with no network or server O/S experience) to be used in the event of a disaster.
I've disconnected the standby server from the network and changed the computer name to be the same as the main server.
I've restored a full system backup and the system state from the main server in Directory Services Restore Mode as recommended by my reference book.
I still can't get the system up and running. Once the Win2K status bar reaches the right hand side of the screen the system reboots itself.
The hardware profiles are not identical. Is this critical ???? (Details below)
If I'm going about this the wrong way could somebody point me in the right direction please or suggest a better way to cater for disaster. I've spent 2.5 weeks trying to do this and I'm getting nowhere fast.
Please advise or help if you can.
Thank you
Keith
Main server
256MB RAM
800MHz AMD processor
1 x Std floppy (A

Adaptec AIC-788x/AHA-2940UW Pro SCSI controller
1 x SCSI ARCHIVE Python 0468-xxx DAT drive
3 x SCSI Seagate HDD 8GB each (C:, D:, E

1 x CDROM Creative 48 speed (F

1 x ATI 3D Rage Pro AGP Graphics
1 x HCF 56k modem
1 X Scanjet 440c
1 x HP Lasrjet 6P
Standby server
128MB RAM
300MHz Intel PII MMX
1 x Std floppy (A

Adaptec AHA-2940U/AHA-2940UW SCSI controller
1 x SCSI ARCHIVE Python 0468-xxx DAT drive
1 x IDE Maxtor HDD 32GB Partitioned (C



1 x CDROM 56 speed (F

S3Trio 32/64 Graphics
No modem fitted
No scanner attached
No printer attached