RE: Determining Corruption

2003-02-06 Thread Woodruff, Michael
Are you using any third party software on this exchange server?

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 06, 2003 8:19 AM
To: Exchange Discussions
Subject: Determining Corruption


I'll throw myself at the mercy of the group.  I have the following in in
the App Log.  They occurred during the backup with Veritas 8.6.  This is
a W2K/Exchange 2K setup.  I am going to call veritas but in the mean
time wanted to get input on what I can do to determine if these files
are actual corrupt? TIA.

Jim Liddil

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/4/2003
Time:   9:34:58 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for
24576
(0x6000) bytes failed with system error 87 (0x0057): "The
parameter is incorrect. ".  The read operation will fail with error
-1003 (0xfc15). If this error persists then the file may be damaged
and may need to be restored from a previous backup. 

And

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/5/2003
Time:   8:59:51 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for
65536
(0x0001) bytes failed with system error 87 (0x0057): "The
parameter is incorrect. ".  The read operation will fail with error
-1003 (0xfc15). If this error persists then the file may be damaged
and may need to be restored from a previous backup. 


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Determining Corruption

2003-02-06 Thread James Liddil
Yes. It also acts as a file server.  Diskkeeper, MacAfee antivirus, Trend
micro.  But nothing new installed in a while.

Jim

-Original Message-
From: Woodruff, Michael [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 06, 2003 8:24 AM
To: Exchange Discussions
Subject: RE: Determining Corruption


Are you using any third party software on this exchange server?

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 06, 2003 8:19 AM
To: Exchange Discussions
Subject: Determining Corruption


I'll throw myself at the mercy of the group.  I have the following in in the
App Log.  They occurred during the backup with Veritas 8.6.  This is a
W2K/Exchange 2K setup.  I am going to call veritas but in the mean time
wanted to get input on what I can do to determine if these files are actual
corrupt? TIA.

Jim Liddil

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/4/2003
Time:   9:34:58 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for 24576
(0x6000) bytes failed with system error 87 (0x0057): "The parameter
is incorrect. ".  The read operation will fail with error -1003 (0xfc15).
If this error persists then the file may be damaged and may need to be
restored from a previous backup. 

And

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/5/2003
Time:   8:59:51 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for 65536
(0x0001) bytes failed with system error 87 (0x0057): "The parameter
is incorrect. ".  The read operation will fail with error -1003 (0xfc15).
If this error persists then the file may be damaged and may need to be
restored from a previous backup. 


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Determining Corruption

2003-02-06 Thread ad
Are you using the Open File option ?

You cannot backup open Exchange files.  You should be using the Agent.

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 13:19
To: Exchange Discussions
Subject: Determining Corruption


I'll throw myself at the mercy of the group.  I have the following in in
the App Log.  They occurred during the backup with Veritas 8.6.  This is
a W2K/Exchange 2K setup.  I am going to call veritas but in the mean
time wanted to get input on what I can do to determine if these files
are actual corrupt? TIA.

Jim Liddil

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/4/2003
Time:   9:34:58 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for
24576
(0x6000) bytes failed with system error 87 (0x0057): "The
parameter is incorrect. ".  The read operation will fail with error
-1003 (0xfc15). If this error persists then the file may be damaged
and may need to be restored from a previous backup. 

And

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/5/2003
Time:   8:59:51 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for
65536
(0x0001) bytes failed with system error 87 (0x0057): "The
parameter is incorrect. ".  The read operation will fail with error
-1003 (0xfc15). If this error persists then the file may be damaged
and may need to be restored from a previous backup. 


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
Network Defence Ltd.

This footnote also confirms that this email message has been swept 
for the presence of computer viruses.

For more information please contact the Network Defence Technical
Department on 01925 272001

Network Defence Ltd.
**


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Determining Corruption

2003-02-06 Thread James Liddil
Yes I have OFO, but I also have the exchange agent.

Jim

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 06, 2003 8:32 AM
To: Exchange Discussions
Subject: RE: Determining Corruption


Are you using the Open File option ?

You cannot backup open Exchange files.  You should be using the Agent.

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 13:19
To: Exchange Discussions
Subject: Determining Corruption


I'll throw myself at the mercy of the group.  I have the following in in the
App Log.  They occurred during the backup with Veritas 8.6.  This is a
W2K/Exchange 2K setup.  I am going to call veritas but in the mean time
wanted to get input on what I can do to determine if these files are actual
corrupt? TIA.

Jim Liddil

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/4/2003
Time:   9:34:58 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for 24576
(0x6000) bytes failed with system error 87 (0x0057): "The parameter
is incorrect. ".  The read operation will fail with error -1003 (0xfc15).
If this error persists then the file may be damaged and may need to be
restored from a previous backup. 

And

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/5/2003
Time:   8:59:51 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for 65536
(0x0001) bytes failed with system error 87 (0x0057): "The parameter
is incorrect. ".  The read operation will fail with error -1003 (0xfc15).
If this error persists then the file may be damaged and may need to be
restored from a previous backup. 


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. If
you have received this email in error please notify Network Defence Ltd.

This footnote also confirms that this email message has been swept 
for the presence of computer viruses.

For more information please contact the Network Defence Technical Department
on 01925 272001

Network Defence Ltd.
**


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Determining Corruption

2003-02-06 Thread ad
Do not select the dirs where exchange exists for file selection backup.


Using OFO with exchange is bad for exchange.

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 13:29
To: Exchange Discussions
Subject: RE: Determining Corruption


Yes I have OFO, but I also have the exchange agent.

Jim

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 06, 2003 8:32 AM
To: Exchange Discussions
Subject: RE: Determining Corruption


Are you using the Open File option ?

You cannot backup open Exchange files.  You should be using the Agent.

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 13:19
To: Exchange Discussions
Subject: Determining Corruption


I'll throw myself at the mercy of the group.  I have the following in in
the App Log.  They occurred during the backup with Veritas 8.6.  This is
a W2K/Exchange 2K setup.  I am going to call veritas but in the mean
time wanted to get input on what I can do to determine if these files
are actual corrupt? TIA.

Jim Liddil

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/4/2003
Time:   9:34:58 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for
24576
(0x6000) bytes failed with system error 87 (0x0057): "The
parameter is incorrect. ".  The read operation will fail with error
-1003 (0xfc15). If this error persists then the file may be damaged
and may need to be restored from a previous backup. 

And

Event Type: Error
Event Source:   ESE
Event Category: General 
Event ID:   481
Date:   2/5/2003
Time:   8:59:51 PM
User:   N/A
Computer:   NHSERVER
Description:
Information Store (3876) An attempt to read from the file
"E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for
65536
(0x0001) bytes failed with system error 87 (0x0057): "The
parameter is incorrect. ".  The read operation will fail with error
-1003 (0xfc15). If this error persists then the file may be damaged
and may need to be restored from a previous backup. 


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]


**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify
Network Defence Ltd.

This footnote also confirms that this email message has been swept 
for the presence of computer viruses.

For more information please contact the Network Defence Technical
Department on 01925 272001

Network Defence Ltd.
**


_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Determining Corruption

2003-02-06 Thread Couch, Nate
Also make sure your McAfee AV software is setup to exclude the Exchange
directories.  Use some E2K compliant software to scan Exchange directories
such as Trend Micro or Groupshield 2000.

Nate Couch
EDS Messaging

> --
> From: [EMAIL PROTECTED]
> Reply To: [EMAIL PROTECTED]
> Sent: Thursday, February 6, 2003 07:35
> To:   [EMAIL PROTECTED]
> Subject:      RE: Determining Corruption
> 
> Do not select the dirs where exchange exists for file selection backup.
> 
> 
> Using OFO with exchange is bad for exchange.
> 
> -Original Message-
> From: James Liddil [mailto:[EMAIL PROTECTED]] 
> Sent: 06 February 2003 13:29
> To: Exchange Discussions
> Subject: RE: Determining Corruption
> 
> 
> Yes I have OFO, but I also have the exchange agent.
> 
> Jim
> 
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, February 06, 2003 8:32 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
> 
> 
> Are you using the Open File option ?
> 
> You cannot backup open Exchange files.  You should be using the Agent.
> 
> -Original Message-
> From: James Liddil [mailto:[EMAIL PROTECTED]] 
> Sent: 06 February 2003 13:19
> To: Exchange Discussions
> Subject: Determining Corruption
> 
> 
> I'll throw myself at the mercy of the group.  I have the following in in
> the App Log.  They occurred during the backup with Veritas 8.6.  This is
> a W2K/Exchange 2K setup.  I am going to call veritas but in the mean
> time wanted to get input on what I can do to determine if these files
> are actual corrupt? TIA.
> 
> Jim Liddil
> 
> Event Type:   Error
> Event Source: ESE
> Event Category:   General 
> Event ID: 481
> Date: 2/4/2003
> Time: 9:34:58 PM
> User: N/A
> Computer: NHSERVER
> Description:
> Information Store (3876) An attempt to read from the file
> "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for
> 24576
> (0x6000) bytes failed with system error 87 (0x0057): "The
> parameter is incorrect. ".  The read operation will fail with error
> -1003 (0xfc15). If this error persists then the file may be damaged
> and may need to be restored from a previous backup. 
> 
> And
> 
> Event Type:   Error
> Event Source: ESE
> Event Category:   General 
> Event ID: 481
> Date: 2/5/2003
> Time: 8:59:51 PM
> User: N/A
> Computer: NHSERVER
> Description:
> Information Store (3876) An attempt to read from the file
> "E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for
> 65536
> (0x0001) bytes failed with system error 87 (0x0057): "The
> parameter is incorrect. ".  The read operation will fail with error
> -1003 (0xfc15). If this error persists then the file may be damaged
> and may need to be restored from a previous backup. 
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> 
> **
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this email in error please notify
> Network Defence Ltd.
> 
> This footnote also confirms that this email message has been swept 
> for the presence of computer viruses.
> 
> For more information please contact the Network Defence Technical
> Department on 01925 272001
> 
> Network Defence Ltd.
> **
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://

RE: Determining Corruption

2003-02-06 Thread James Liddil
I just ran a backup on just the store an get the same thing I got last night.
I am on the phone with veritas now.  Is it time to call PSS?!

Performing Remote Agent backup

Media Name: "Media created 1/20/2003 09:24:46 AM"
Backup of "\\NHSERVER\Microsoft Information Store\First Storage Group "
Backup set #36 on storage media #1
Backup set description: "Differential"
Backup Type: FULL - Database & Logs (flush committed logs)
Backup started on 2/5/2003 at 8:53:33 PM.
WARNING: "Mailbox Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
WARNING: "Public Folder Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
Log files

Backup completed on 2/5/2003 at 9:05:41 PM.
Backed up 2 Exchange Server store(s)
Backed up Exchange Server logs
2 corrupt files were backed up
Processed 4,161,036,920 bytes in  12 minutes and  8 seconds.
Throughput rate: 327.1 MB/min

> -Original Message-
> From: Couch, Nate [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 06, 2003 8:35 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
> 
> 
> Also make sure your McAfee AV software is setup to exclude 
> the Exchange
> directories.  Use some E2K compliant software to scan 
> Exchange directories
> such as Trend Micro or Groupshield 2000.
> 
> Nate Couch
> EDS Messaging
> 
> > --
> > From:   [EMAIL PROTECTED]
> > Reply To:   [EMAIL PROTECTED]
> > Sent:   Thursday, February 6, 2003 07:35
> > To: [EMAIL PROTECTED]
> > Subject:RE: Determining Corruption
> > 
> > Do not select the dirs where exchange exists for file 
> selection backup.
> > 
> > 
> > Using OFO with exchange is bad for exchange.
> > 
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]] 
> > Sent: 06 February 2003 13:29
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> > 
> > 
> > Yes I have OFO, but I also have the exchange agent.
> > 
> > Jim
> > 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
> > Sent: Thursday, February 06, 2003 8:32 AM
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> > 
> > 
> > Are you using the Open File option ?
> > 
> > You cannot backup open Exchange files.  You should be using 
> the Agent.
> > 
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]] 
> > Sent: 06 February 2003 13:19
> > To: Exchange Discussions
> > Subject: Determining Corruption
> > 
> > 
> > I'll throw myself at the mercy of the group.  I have the 
> following in in
> > the App Log.  They occurred during the backup with Veritas 
> 8.6.  This is
> > a W2K/Exchange 2K setup.  I am going to call veritas but in the mean
> > time wanted to get input on what I can do to determine if 
> these files
> > are actual corrupt? TIA.
> > 
> > Jim Liddil
> > 
> > Event Type: Error
> > Event Source:   ESE
> > Event Category: General 
> > Event ID:   481
> > Date:   2/4/2003
> > Time:   9:34:58 PM
> > User:   N/A
> > Computer:   NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file
> > "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for
> > 24576
> > (0x6000) bytes failed with system error 87 (0x0057): "The
> > parameter is incorrect. ".  The read operation will fail with error
> > -1003 (0xfc15). If this error persists then the file 
> may be damaged
> > and may need to be restored from a previous backup. 
> > 
> > And
> > 
> > Event Type: Error
> > Event Source:   ESE
> > Event Category: General 
> > Event ID:   481
> > Date:   2/5/2003
> > Time:   8:59:51 PM
> > User:   N/A
> > Computer:   NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file
> > "E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for
> > 65536
> > (0x0001) bytes failed with system error 87 (0x0057): "The
> > parameter is incorrect. ".  The read operation will fail with error
> > -1003 (0xfc15). If this error persists then the file 
> may be damaged
> > and may need to be restored from a previous backup. 
> > 
> > 
> > _
> > List posting FAQ: 

Re: Determining Corruption

2003-02-06 Thread Andy David
Try doing a full online backup with plain ol NTBACKUP.

- Original Message -
From: "James Liddil" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Thursday, February 06, 2003 9:35 AM
Subject: RE: Determining Corruption


I just ran a backup on just the store an get the same thing I got last
night.
I am on the phone with veritas now.  Is it time to call PSS?!

Performing Remote Agent backup

Media Name: "Media created 1/20/2003 09:24:46 AM"
Backup of "\\NHSERVER\Microsoft Information Store\First Storage Group "
Backup set #36 on storage media #1
Backup set description: "Differential"
Backup Type: FULL - Database & Logs (flush committed logs)
Backup started on 2/5/2003 at 8:53:33 PM.
WARNING: "Mailbox Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
WARNING: "Public Folder Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
Log files

Backup completed on 2/5/2003 at 9:05:41 PM.
Backed up 2 Exchange Server store(s)
Backed up Exchange Server logs
2 corrupt files were backed up
Processed 4,161,036,920 bytes in  12 minutes and  8 seconds.
Throughput rate: 327.1 MB/min

> -Original Message-
> From: Couch, Nate [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 06, 2003 8:35 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
>
>
> Also make sure your McAfee AV software is setup to exclude
> the Exchange
> directories.  Use some E2K compliant software to scan
> Exchange directories
> such as Trend Micro or Groupshield 2000.
>
> Nate Couch
> EDS Messaging
>
> > --
> > From: [EMAIL PROTECTED]
> > Reply To: [EMAIL PROTECTED]
> > Sent: Thursday, February 6, 2003 07:35
> > To: [EMAIL PROTECTED]
> > Subject: RE: Determining Corruption
> >
> > Do not select the dirs where exchange exists for file
> selection backup.
> >
> >
> > Using OFO with exchange is bad for exchange.
> >
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:29
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> >
> >
> > Yes I have OFO, but I also have the exchange agent.
> >
> > Jim
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, February 06, 2003 8:32 AM
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> >
> >
> > Are you using the Open File option ?
> >
> > You cannot backup open Exchange files.  You should be using
> the Agent.
> >
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:19
> > To: Exchange Discussions
> > Subject: Determining Corruption
> >
> >
> > I'll throw myself at the mercy of the group.  I have the
> following in in
> > the App Log.  They occurred during the backup with Veritas
> 8.6.  This is
> > a W2K/Exchange 2K setup.  I am going to call veritas but in the mean
> > time wanted to get input on what I can do to determine if
> these files
> > are actual corrupt? TIA.
> >
> > Jim Liddil
> >
> > Event Type: Error
> > Event Source: ESE
> > Event Category: General
> > Event ID: 481
> > Date: 2/4/2003
> > Time: 9:34:58 PM
> > User: N/A
> > Computer: NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file
> > "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for
> > 24576
> > (0x6000) bytes failed with system error 87 (0x0057): "The
> > parameter is incorrect. ".  The read operation will fail with error
> > -1003 (0xfc15). If this error persists then the file
> may be damaged
> > and may need to be restored from a previous backup.
> >
> > And
> >
> > Event Type: Error
> > Event Source: ESE
> > Event Category: General
> > Event ID: 481
> > Date: 2/5/2003
> > Time: 8:59:51 PM
> > User: N/A
> > Computer: NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file
> > "E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for
> > 65536
> > (0x0001) bytes failed with system error 87 (0x0057): "The
> > parameter is incorrect. ".  The read operation will fail with error
> > -1003 (0xfc15). If this error persists then the file
> may be damaged
> > and may need to be restored from a previous backup.
> >
> >

RE: Determining Corruption

2003-02-06 Thread ad
The OFO may have damaged the store.

-Original Message-
From: James Liddil [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 14:35
To: Exchange Discussions
Subject: RE: Determining Corruption


I just ran a backup on just the store an get the same thing I got last
night. I am on the phone with veritas now.  Is it time to call PSS?!

Performing Remote Agent backup

Media Name: "Media created 1/20/2003 09:24:46 AM"
Backup of "\\NHSERVER\Microsoft Information Store\First Storage Group "
Backup set #36 on storage media #1 Backup set description:
"Differential" Backup Type: FULL - Database & Logs (flush committed
logs) Backup started on 2/5/2003 at 8:53:33 PM.
WARNING: "Mailbox Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
WARNING: "Public Folder Store (NHSERVER)" is a corrupt file. This file
cannot verify. ^ ^ ^ ^ ^ Log files

Backup completed on 2/5/2003 at 9:05:41 PM.
Backed up 2 Exchange Server store(s)
Backed up Exchange Server logs
2 corrupt files were backed up
Processed 4,161,036,920 bytes in  12 minutes and  8 seconds. Throughput
rate: 327.1 MB/min

> -Original Message-
> From: Couch, Nate [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 06, 2003 8:35 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
> 
> 
> Also make sure your McAfee AV software is setup to exclude
> the Exchange
> directories.  Use some E2K compliant software to scan 
> Exchange directories
> such as Trend Micro or Groupshield 2000.
> 
> Nate Couch
> EDS Messaging
> 
> > --
> > From:   [EMAIL PROTECTED]
> > Reply To:   [EMAIL PROTECTED]
> > Sent:   Thursday, February 6, 2003 07:35
> > To: [EMAIL PROTECTED]
> > Subject:RE: Determining Corruption
> > 
> > Do not select the dirs where exchange exists for file
> selection backup.
> > 
> > 
> > Using OFO with exchange is bad for exchange.
> > 
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:29
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> > 
> > 
> > Yes I have OFO, but I also have the exchange agent.
> > 
> > Jim
> > 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, February 06, 2003 8:32 AM
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> > 
> > 
> > Are you using the Open File option ?
> > 
> > You cannot backup open Exchange files.  You should be using
> the Agent.
> > 
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:19
> > To: Exchange Discussions
> > Subject: Determining Corruption
> > 
> > 
> > I'll throw myself at the mercy of the group.  I have the
> following in in
> > the App Log.  They occurred during the backup with Veritas
> 8.6.  This is
> > a W2K/Exchange 2K setup.  I am going to call veritas but in the mean

> > time wanted to get input on what I can do to determine if
> these files
> > are actual corrupt? TIA.
> > 
> > Jim Liddil
> > 
> > Event Type: Error
> > Event Source:   ESE
> > Event Category: General 
> > Event ID:   481
> > Date:   2/4/2003
> > Time:   9:34:58 PM
> > User:   N/A
> > Computer:   NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file 
> > "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for 
> > 24576
> > (0x6000) bytes failed with system error 87 (0x0057): "The 
> > parameter is incorrect. ".  The read operation will fail with error 
> > -1003 (0xfc15). If this error persists then the file
> may be damaged
> > and may need to be restored from a previous backup.
> > 
> > And
> > 
> > Event Type: Error
> > Event Source:   ESE
> > Event Category: General 
> > Event ID:   481
> > Date:   2/5/2003
> > Time:   8:59:51 PM
> > User:   N/A
> > Computer:   NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file 
> > "E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for

> > 65536
> > (0x0001) bytes failed with system error 87 (0x0057): "The 
> > parameter is incorrect. ".  The read operation will fail with error 
> > -1003 (0xfc15). If this error persists then the file
> may be dam

RE: Determining Corruption

2003-02-06 Thread ad
Now would be a good time to make an off-line backup too.

-Original Message-
From: Andy David [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 14:39
To: Exchange Discussions
Subject: Re: Determining Corruption


Try doing a full online backup with plain ol NTBACKUP.

- Original Message -
From: "James Liddil" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Thursday, February 06, 2003 9:35 AM
Subject: RE: Determining Corruption


I just ran a backup on just the store an get the same thing I got last
night. I am on the phone with veritas now.  Is it time to call PSS?!

Performing Remote Agent backup

Media Name: "Media created 1/20/2003 09:24:46 AM"
Backup of "\\NHSERVER\Microsoft Information Store\First Storage Group "
Backup set #36 on storage media #1 Backup set description:
"Differential" Backup Type: FULL - Database & Logs (flush committed
logs) Backup started on 2/5/2003 at 8:53:33 PM.
WARNING: "Mailbox Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
WARNING: "Public Folder Store (NHSERVER)" is a corrupt file. This file
cannot verify. ^ ^ ^ ^ ^ Log files

Backup completed on 2/5/2003 at 9:05:41 PM.
Backed up 2 Exchange Server store(s)
Backed up Exchange Server logs
2 corrupt files were backed up
Processed 4,161,036,920 bytes in  12 minutes and  8 seconds. Throughput
rate: 327.1 MB/min

> -Original Message-
> From: Couch, Nate [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 06, 2003 8:35 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
>
>
> Also make sure your McAfee AV software is setup to exclude the 
> Exchange directories.  Use some E2K compliant software to scan
> Exchange directories
> such as Trend Micro or Groupshield 2000.
>
> Nate Couch
> EDS Messaging
>
> > --
> > From: [EMAIL PROTECTED]
> > Reply To: [EMAIL PROTECTED]
> > Sent: Thursday, February 6, 2003 07:35
> > To: [EMAIL PROTECTED]
> > Subject: RE: Determining Corruption
> >
> > Do not select the dirs where exchange exists for file
> selection backup.
> >
> >
> > Using OFO with exchange is bad for exchange.
> >
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:29
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> >
> >
> > Yes I have OFO, but I also have the exchange agent.
> >
> > Jim
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, February 06, 2003 8:32 AM
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> >
> >
> > Are you using the Open File option ?
> >
> > You cannot backup open Exchange files.  You should be using
> the Agent.
> >
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:19
> > To: Exchange Discussions
> > Subject: Determining Corruption
> >
> >
> > I'll throw myself at the mercy of the group.  I have the
> following in in
> > the App Log.  They occurred during the backup with Veritas
> 8.6.  This is
> > a W2K/Exchange 2K setup.  I am going to call veritas but in the mean

> > time wanted to get input on what I can do to determine if
> these files
> > are actual corrupt? TIA.
> >
> > Jim Liddil
> >
> > Event Type: Error
> > Event Source: ESE
> > Event Category: General
> > Event ID: 481
> > Date: 2/4/2003
> > Time: 9:34:58 PM
> > User: N/A
> > Computer: NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file 
> > "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for 
> > 24576
> > (0x6000) bytes failed with system error 87 (0x0057): "The 
> > parameter is incorrect. ".  The read operation will fail with error 
> > -1003 (0xfc15). If this error persists then the file
> may be damaged
> > and may need to be restored from a previous backup.
> >
> > And
> >
> > Event Type: Error
> > Event Source: ESE
> > Event Category: General
> > Event ID: 481
> > Date: 2/5/2003
> > Time: 8:59:51 PM
> > User: N/A
> > Computer: NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file 
> > "E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 (0x) for

> > 65536
> > (0x0001) bytes failed with system error 87 (0x0057): "The 
> > parameter is inc

RE: Determining Corruption

2003-02-06 Thread Public Folder: Exchange

Make sure Diskeeper is not attempting to defrag the Exchange
directories.

Make sure your anti-virus is not scanning the Exchange directories.

-Kevin


> -Original Message-
> From: James Liddil [mailto:[EMAIL PROTECTED]] 
> Posted At: Thursday, February 06, 2003 5:26 AM
> Posted To: Exchange
> Conversation: Determining Corruption
> Subject: RE: Determining Corruption
> 
> 
> Yes. It also acts as a file server.  Diskkeeper, MacAfee 
> antivirus, Trend
> micro.  But nothing new installed in a while.
> 
> Jim
> 
> -Original Message-
> From: Woodruff, Michael [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, February 06, 2003 8:24 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
> 
> 
> Are you using any third party software on this exchange server?
> 
> -Original Message-
> From: James Liddil [mailto:[EMAIL PROTECTED]] 
> Sent: Thursday, February 06, 2003 8:19 AM
> To: Exchange Discussions
> Subject: Determining Corruption
> 
> 
> I'll throw myself at the mercy of the group.  I have the 
> following in in the
> App Log.  They occurred during the backup with Veritas 8.6.  This is a
> W2K/Exchange 2K setup.  I am going to call veritas but in the 
> mean time
> wanted to get input on what I can do to determine if these 
> files are actual
> corrupt? TIA.
> 
> Jim Liddil
> 
> Event Type:   Error
> Event Source: ESE
> Event Category:   General 
> Event ID: 481
> Date: 2/4/2003
> Time: 9:34:58 PM
> User: N/A
> Computer: NHSERVER
> Description:
> Information Store (3876) An attempt to read from the file
> "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 
> (0x) for 24576
> (0x6000) bytes failed with system error 87 (0x0057): 
> "The parameter
> is incorrect. ".  The read operation will fail with error 
> -1003 (0xfc15).
> If this error persists then the file may be damaged and may need to be
> restored from a previous backup. 
> 
> And
> 
> Event Type:   Error
> Event Source: ESE
> Event Category:   General 
> Event ID: 481
> Date: 2/5/2003
> Time: 8:59:51 PM
> User: N/A
> Computer: NHSERVER
> Description:
> Information Store (3876) An attempt to read from the file
> "E:\Exchsrvr\MDBDATA\priv1.stm" at offset 0 
> (0x) for 65536
> (0x0001) bytes failed with system error 87 (0x0057): 
> "The parameter
> is incorrect. ".  The read operation will fail with error 
> -1003 (0xfc15).
> If this error persists then the file may be damaged and may need to be
> restored from a previous backup. 
> 
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 
> _
> List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
> Archives:   http://www.swynk.com/sitesearch/search.asp
> To unsubscribe: mailto:[EMAIL PROTECTED]
> Exchange List admin:[EMAIL PROTECTED]
> 

_
List posting FAQ:   http://www.swinc.com/resource/exch_faq.htm
Archives:   http://www.swynk.com/sitesearch/search.asp
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin:[EMAIL PROTECTED]



RE: Determining Corruption

2003-02-06 Thread James Liddil
Spent the $245 for PSS.  Ran the isinteg tool a few times and all is well
now.  Now to figure out what is running at the backup time.  I thought I had
everything scheduled to not run then.

Jim


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, February 06, 2003 9:53 AM
To: Exchange Discussions
Subject: RE: Determining Corruption


Now would be a good time to make an off-line backup too.

-Original Message-
From: Andy David [mailto:[EMAIL PROTECTED]] 
Sent: 06 February 2003 14:39
To: Exchange Discussions
Subject: Re: Determining Corruption


Try doing a full online backup with plain ol NTBACKUP.

- Original Message -
From: "James Liddil" <[EMAIL PROTECTED]>
To: "Exchange Discussions" <[EMAIL PROTECTED]>
Sent: Thursday, February 06, 2003 9:35 AM
Subject: RE: Determining Corruption


I just ran a backup on just the store an get the same thing I got last night.
I am on the phone with veritas now.  Is it time to call PSS?!

Performing Remote Agent backup

Media Name: "Media created 1/20/2003 09:24:46 AM"
Backup of "\\NHSERVER\Microsoft Information Store\First Storage Group "
Backup set #36 on storage media #1 Backup set description: "Differential"
Backup Type: FULL - Database & Logs (flush committed
logs) Backup started on 2/5/2003 at 8:53:33 PM.
WARNING: "Mailbox Store (NHSERVER)" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
WARNING: "Public Folder Store (NHSERVER)" is a corrupt file. This file cannot
verify. ^ ^ ^ ^ ^ Log files

Backup completed on 2/5/2003 at 9:05:41 PM.
Backed up 2 Exchange Server store(s)
Backed up Exchange Server logs
2 corrupt files were backed up
Processed 4,161,036,920 bytes in  12 minutes and  8 seconds. Throughput
rate: 327.1 MB/min

> -Original Message-
> From: Couch, Nate [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 06, 2003 8:35 AM
> To: Exchange Discussions
> Subject: RE: Determining Corruption
>
>
> Also make sure your McAfee AV software is setup to exclude the
> Exchange directories.  Use some E2K compliant software to scan
> Exchange directories
> such as Trend Micro or Groupshield 2000.
>
> Nate Couch
> EDS Messaging
>
> > --
> > From: [EMAIL PROTECTED]
> > Reply To: [EMAIL PROTECTED]
> > Sent: Thursday, February 6, 2003 07:35
> > To: [EMAIL PROTECTED]
> > Subject: RE: Determining Corruption
> >
> > Do not select the dirs where exchange exists for file
> selection backup.
> >
> >
> > Using OFO with exchange is bad for exchange.
> >
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:29
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> >
> >
> > Yes I have OFO, but I also have the exchange agent.
> >
> > Jim
> >
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, February 06, 2003 8:32 AM
> > To: Exchange Discussions
> > Subject: RE: Determining Corruption
> >
> >
> > Are you using the Open File option ?
> >
> > You cannot backup open Exchange files.  You should be using
> the Agent.
> >
> > -Original Message-
> > From: James Liddil [mailto:[EMAIL PROTECTED]]
> > Sent: 06 February 2003 13:19
> > To: Exchange Discussions
> > Subject: Determining Corruption
> >
> >
> > I'll throw myself at the mercy of the group.  I have the
> following in in
> > the App Log.  They occurred during the backup with Veritas
> 8.6.  This is
> > a W2K/Exchange 2K setup.  I am going to call veritas but in the mean

> > time wanted to get input on what I can do to determine if
> these files
> > are actual corrupt? TIA.
> >
> > Jim Liddil
> >
> > Event Type: Error
> > Event Source: ESE
> > Event Category: General
> > Event ID: 481
> > Date: 2/4/2003
> > Time: 9:34:58 PM
> > User: N/A
> > Computer: NHSERVER
> > Description:
> > Information Store (3876) An attempt to read from the file
> > "E:\Exchsrvr\MDBDATA\pub1.stm" at offset 0 (0x) for 
> > 24576
> > (0x6000) bytes failed with system error 87 (0x0057): "The 
> > parameter is incorrect. ".  The read operation will fail with error 
> > -1003 (0xfc15). If this error persists then the file
> may be damaged
> > and may need to be restored from a previous backup.
> >
> > And
> >
> > Event Type: Error
> > Event Source: ESE
> > Event Category: General
> > Event ID: 481
> > Date: 2/5/2