Cannot backup Exchange VSS Error
in [Microsoft Exchange]
|
From: KCotreau on 26 Sep 2008 11:24 Hi all, I was getting similar errors recently but in Backup Exec. First, did you have Microsoft Automatic Updates set to run? If so, you may have gotten Exchange SP1 Rollup 4 installed automatically, which was promptly pulled. You should check in Add/Remove Programs and if it is installed, you will need to uninstall it. This is discussed in detail at the Exchange Team's blog here: http://msexchangeteam.com/archive/2008/09/11/449787.aspx . Second, even after all that I was still getting the following error, where the 3916 and 7 are variables to your system: Event Type: Error Event Source: ESE Event Category: ShadowCopy Event ID: 2007 Date: 9/22/2008 Time: 3:56:34 AM User: N/A Computer: EDITEDDC01 Description: Information Store (3916) Shadow copy instance 7 aborted. I solved that one by installing the VSS Rollup patch, which can be found here: http://support.microsoft.com/kb/940349 I hope this helps you. Kevin Cotreau, MCSE+I, MCNE, et. al. "introtologic" <otgkhan(a)gmail.com> wrote in message news:7815de0f-50d3-4b90-b415-9d1238f990ef(a)z66g2000hsc.googlegroups.com... > Thanks for the suggesion John. I tried to create a Database-Level > backup only. Still the backup failed. In application log First the > same VSS error showed up then some information entries telling me that > storage gourp is froze, thawed ready for copy etc. One infromation > entry mentions dirty shutdown state: > > Log Name: Application > Source: Storage Group Consistency Check > Date: 9/25/2008 11:13:11 AM > Event ID: 200 > Task Category: Database Header Validation > Level: Information > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Instance 1: Database headers have been successfully validated. All > databases are in a dirty shutdown state. To bring these databases to a > clean shutdown state, log generations 8367 (0x000020af) to 8379 > (0x000020bb) will be required. > > The log generation numbers are different each time I try to back up > and as you can see it is an information entry not an error. > > this is followed by several more info. entries about different tasks > Log file integrity check etc and all show completed tasks. > > Then these four errors appear: > > 1. Log Name: Application > Source: Storage Group Consistency Check > Date: 9/25/2008 11:27:03 AM > Event ID: 402 > Task Category: Termination > Level: Error > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Instance 1: Termination of the physical consistency check was > prevented because the operation has either already been performed or > was not yet ready to be performed. The operation failed with error > code -1059 (0xfffffbdd). > > 2. Exact same error as mentioned in my original post about IVssWriter > callback interface. > > 3. Log Name: Application > Source: MSExchangeIS > Date: 9/25/2008 11:27:04 AM > Event ID: 9782 > Task Category: Exchange VSS Writer > Level: Error > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Exchange VSS Writer (instance edfba2a7-4f27-4b48-ad5b-0dc51802fa64:3) > has unsuccessfully completed the backup of storage group 'First > Storage Group'. No log files have been truncated for this storage > group. > > 4. Log Name: Application > Source: ESE > Date: 9/25/2008 11:27:04 AM > Event ID: 2007 > Task Category: ShadowCopy > Level: Error > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Information Store (2568) Shadow copy instance 3 aborted. > > For more information, click http://www.microsoft.com/contentredirect.asp. > > The last entry in the sequence in an information entry : > > Log Name: Application > Source: MSExchangeIS > Date: 9/25/2008 11:27:04 AM > Event ID: 9616 > Task Category: Exchange VSS Writer > Level: Information > Keywords: Classic > User: N/A > Computer: email.asms.net > Description: > Exchange VSS Writer (instance edfba2a7-4f27-4b48-ad5b-0dc51802fa64:3) > has processed the backup completion event successfully. > > Though the backup has not completed.
From: Ed Crowley [MVP] on 26 Sep 2008 17:05 You should be able to back it up with NTBACKUP to get the logs truncated until you can get your problem with Arcserve resolved. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "introtologic" <otgkhan(a)gmail.com> wrote in message news:6c346006-49b3-41c8-9220-013c60d28a86(a)k13g2000hse.googlegroups.com... > Exchange and OS are set up on a Single hard disk. The exchange DB size > is about 20 GB. But it hasnt been backed up in a while and the logs > have grown in size. Still the used space on the drive is about 60 GB > and 70GB is free. Shadow Copy settings allow for as much space needed > (No limit set). Currently regular shadow copies are not enabled. IN > past several backups I have only been trying to run the exchange Db > level backup (Not system state and not even Document level backup for > exchange.) I have opened up a support ticket with ArcServe again but > all they do is tell me to give them time to do some research and then > comeback with some KB articles which don't help.
From: John Fullbright on 26 Sep 2008 18:05 When you do a freeze with the exchange writer. E0n.log is closed and renumbered the highest log number. At that point, the VSS provider does a snapshot of the volume. A thaw is then issued and a new e0n.log is created. When you go to verifiy the backup, either eseutil or chksgfiles is used to verify the backup. You get a -1059, JeterrorTooManyActiveUsers, which is a bit strange. It could be the RU4 that was released on 9 September and then recalled I suppose. I have seen chksgfiles fail with -1811 when the 9 Sep RU4 is installed. Rolling back resolved the issue. If this were the issue, I'd expect to see event ID 305 or 401. I don't think your situation quite matches that. Try going in and deleting all the Shadow Copies on the C: volume except the last one, then try backing up the storage group by itself. John "introtologic" <otgkhan(a)gmail.com> wrote in message news:db1ad64f-255f-41cd-ad2b-94e753aad1b4(a)k37g2000hsf.googlegroups.com... > Thanks for the suggesion John. I tried to create a Database-Level > backup only. Still the backup failed. In application log First the > same VSS error showed up then some information entries telling me > that > storage gourp is froze, thawed ready for copy etc. One infromation > entry mentions dirty shutdown state: > > Log Name: Application > Source: Storage Group Consistency Check > Date: 9/25/2008 11:13:11 AM > Event ID: 200 > Task Category: Database Header Validation > Level: Information > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Instance 1: Database headers have been successfully validated. All > databases are in a dirty shutdown state. To bring these databases to > a > clean shutdown state, log generations 8367 (0x000020af) to 8379 > (0x000020bb) will be required. > > > The log generation numbers are different each time I try to back up > and as you can see it is an information entry not an error. > > > this is followed by several more info. entries about different tasks > Log file integrity check etc and all show completed tasks. > > > Then these four errors appear: > > > 1. Log Name: Application > Source: Storage Group Consistency Check > Date: 9/25/2008 11:27:03 AM > Event ID: 402 > Task Category: Termination > Level: Error > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Instance 1: Termination of the physical consistency check was > prevented because the operation has either already been performed or > was not yet ready to be performed. The operation failed with error > code -1059 (0xfffffbdd). > > > 2. Exact same error as mentioned in my original post about IVssWriter > callback interface. > > > 3. Log Name: Application > Source: MSExchangeIS > Date: 9/25/2008 11:27:04 AM > Event ID: 9782 > Task Category: Exchange VSS Writer > Level: Error > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Exchange VSS Writer (instance edfba2a7-4f27-4b48-ad5b-0dc51802fa64:3) > has unsuccessfully completed the backup of storage group 'First > Storage Group'. No log files have been truncated for this storage > group. > > > 4. Log Name: Application > Source: ESE > Date: 9/25/2008 11:27:04 AM > Event ID: 2007 > Task Category: ShadowCopy > Level: Error > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Information Store (2568) Shadow copy instance 3 aborted. > > > For more information, click http://www.microsoft.com/contentredirect.asp. > > > The last entry in the sequence in an information entry : > > > Log Name: Application > Source: MSExchangeIS > Date: 9/25/2008 11:27:04 AM > Event ID: 9616 > Task Category: Exchange VSS Writer > Level: Information > Keywords: Classic > User: N/A > Computer: email.company.net > Description: > Exchange VSS Writer (instance edfba2a7-4f27-4b48-ad5b-0dc51802fa64:3) > has processed the backup completion event successfully. > > > Though the backup has not completed. > >
From: introtologic on 26 Sep 2008 20:45 Thanks a bunch guys. I did check and see if the Auto Update had installed Roll up 4 but that is not the case. I also tried to backup with the NTBackUp or Windows Server Backup as it is called in Server 2008 but that runs into similar errors and closes without truncating logs. The server becomes extremely sluggish when the backup is running I wonder if it is being timed out. The network is Gigabit so I know its not the bandwidth but the server only has 2 GB of RAM. I will be calling MS Professional Support and see if they can help me fix this thing. I will post the results here
First
|
Prev
|
Pages: 1 2 3 Prev: ccr create public folder database Next: Undeliverable Message when Sending e-mail |