Here's what I do, for what it's worth:
1. Separate boot drive and data drive.
2. Mirror or Raid 5 the data drive, back it up remotely to tape or to another raided disk.
3. Copy the boot drive to a spare boot drive. (to do this, I boot a Win9 diskette, and run Powerquest's "drivecopy" software. Both drives must be connected and running to do this copy; the spare is disconnected after the copy is finished)
If the boot gets corrupted or hacked or just fails, then using an inexpensive removeable drive tray, swap in the good boot drive, and you are up and running again in minutes. Make another spare boot drive next time you can take the server down.
This is not the best procedure, but it works. What I'd rather see is an SME function to copy to a client hard disk everything *EXCEPT* the actual data on the ibays. This info would be easy to store on most any client hard drive, easy to restore, and fast, too, and would avoid the file size limitations under Windows so often complained of on this forum.
Just my $.02.
Jáder Marasca wrote:
>
> Kelvin wrote:
>
> > The chances of a filesystem corruption due to
> > powerfailures / improper shutdown are fairly great
>
> I´m very impressed how unstable is EXT2 when not proper
> shutdown!
> I´m from Novell world, and his FS is very stable and have
> auto correct!
> In almost 10 years I can remember to have FS lost twice!
>
> > Hmm... in all these many years with Windoze servers, I've
> > NEVER had this problem - lose open files yes, lose the server
> > itself - no.
>
> I´m sorry my english is too bad... I couldn´t understand...
> do you NEVER lost a FS on a Win Server? Your a lucky guy!
> I have a couple of Win servers that NEVER go up again... by
> SEVERAL reasons.
> I have to go back and reinstall them and restore backups.
> I just was hoping EXT2 (and new EXT3 w/journaling) was MUCH
> MORE SAFE!
>
> Thanks!