The first rule of NT is never use the NT FTdisk.exe to mirror drives
(Mirroring via software is slow and not that reliable).
If I remember, the NT mirroring S/W will always rebuild the mirrored drive
after a dirty shut down.
Since you did not mention any events of actual hard drive failures, NT would
use the drive with address value 0 as the master and value 1 as the
re-mirrored slave. If the 8 hours of data are not on the master drive or
backed up somewhere else then it's lost forever.
After all that, I don't think FTdisk.exe was the cause of your data loss.
But it's a a good idea to spend a few bucks and get a hardware mirroring
solution.
Good luck,
Jerry Solobay
(Mirroring via software is slow and not that reliable).
If I remember, the NT mirroring S/W will always rebuild the mirrored drive
after a dirty shut down.
Since you did not mention any events of actual hard drive failures, NT would
use the drive with address value 0 as the master and value 1 as the
re-mirrored slave. If the 8 hours of data are not on the master drive or
backed up somewhere else then it's lost forever.
After all that, I don't think FTdisk.exe was the cause of your data loss.
But it's a a good idea to spend a few bucks and get a hardware mirroring
solution.
Good luck,
Jerry Solobay
> -----Original Message-----
> From: John [SMTP:JYohann@...]
> Sent: Tuesday, September 05, 2000 5:11 AM
> To: vantage@egroups.com
> Subject: RE: [Vantage] TECHNICAL PROBLEM VANTAGE
>
>
> I forgot one thing. It is normal for your NT server to request SAM
> updates
> every hour from the PDS. Mine updates every 43 minutes after the hour,
> every hour.
>
> John Yohannan
>
> -----Original Message-----
> From: Jeanne Weiler [mailto:JWEILER@...]
> Sent: Friday, September 01, 2000 5:49 PM
> To: vantage@egroups.com
> Cc: IS Department
> Subject: [Vantage] TECHNICAL PROBLEM VANTAGE
>
>
>
> Here is an "interesting" occurrence that will hopefully never happen to
> you.
>
> We are running as our Vantage server, an Intel LB440GX motherboard running
> dual P3-600 and 512 meg of ram. This is inside of a 2U rack mount chassis
> with two 9gig drives running a RAID 1 software mirror via NT server.
>
> Approximately 24 hours ago, the Vantage server began submitting SAM
> database
> update from the Primary NT server. Over the course of the next 24 hours,
> the
> Vantage server would request a new update every 10 minutes linearly
> increasing the number of update it received back. Nearly 16 hours later,
> Vantage crashed, and none of the users were able to work in Vantage. This
> failure went unreported until 8 hours later. There was an attempt to
> shutdown the Vantage server which ended in a Blue Screen of Death. The
> Vantage server was then shut off and brought back up normally.
>
> Everything appeared to be working fine, but the event log showed that
> Ftdisk
> had begun Mirror initialization on boot. The end result is that we are
> currently missing exactly 1 day worth of data.
>
>
> Has anyone ever had this happen before, if so what did you do?
>
> ANY and all answers or suggestions would be very very helpful.
>
>
>
> We no longer allow attachments to files. To access/share Report Files,
> please go to the following link: http://www.egroups.com/files/vantage/
> (Note: If this link does not work for you the first time you try it, go
> to
> www.egroups.com, login and be sure to save your password, choose My
> Groups,
> choose Vantage, then choose Files. If you save the password, the link
> above
> will work the next time you try it.)
>
>
>
> We no longer allow attachments to files. To access/share Report Files,
> please go to the following link: http://www.egroups.com/files/vantage/
> (Note: If this link does not work for you the first time you try it, go
> to www.egroups.com, login and be sure to save your password, choose My
> Groups, choose Vantage, then choose Files. If you save the password, the
> link above will work the next time you try it.)