Video Screencast Help
Search Video Help Close Back
to help

cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail

Created: 30 Jun 2010 | 6 comments
Ahmed Mostafa Hassabo's picture
Ahmed Mostafa Hassabo Partner Accredited
0 0 Votes
Login to vote

i have symantec backup exec 2010 installed on windows server 64bit... i used agent for exchage to backup my exchange server 2007 that installed in windowes server 2008 64bit..
i run full backup for my exchage server it run succufully without any poroblem
BUT when run incremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail
the exchage stop sending or receving mail when the incremental or deferential job start and begian "snapshot processing"

Discussion Filed Under:
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

Comments 6 Comments • Jump to latest comment

RahulG's picture
RahulG Symantec Employee
cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail - Comment:30 Jun 2010 : Link

Make sure you have sperate backup created which is backing up just the Exchange information Store and the AOFO option is not selected in the backup job properties ...
If you have the Aofo option selected uncheck it and retry the backup job again ...

If this response answers your concern, please mark it as a "solution"

0
Login to vote
  • Actions
RahulG's picture
RahulG Symantec Employee
cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail - Comment:30 Jun 2010 : Link
Removing the AOFO option would prevent the server getting lock and also will allow the users to send and recive email even when the backup is running . Howerver GRT based full backups of Exchange databases may run at an acceptable rate, however, incremental backups may run comparatively slow (i.e. there is a considerable difference in the backup speed of full and incremental backups).
 Solution:
 1. Make sure Backup Exec is fully patched and the Backup Exec Remote Agent on the Exchange server (if it is remote) is updated afterward.
2. Run an offline defragmentation of the Exchange database.  Refer to the Microsoft KB Article below for additional information on how to run a defragmentation on the Exchange database.
 How to defragment Exchange databases
 http://support.microsoft.com/kb/328804

If this response answers your concern, please mark it as a "solution"

0
Login to vote
  • Actions
Ahmed Mostafa Hassabo's picture
Ahmed Mostafa Hassabo Partner Accredited
cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail - Comment:30 Jun 2010 : Link
RahulG

i already make seprate backup job for exchange .. this job i made it in rule.. and the destintion is B2D...
the AOFO is not selceted ...i try the both with and without AOFO ...
but this problem is appear in icremental or deferential backup only...

The Full backup work without any problem ..
 

0
Login to vote
  • Actions
Ahmed Mostafa Hassabo's picture
Ahmed Mostafa Hassabo Partner Accredited
cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail - Comment:30 Jun 2010 : Link

i deselect the AOFO form job propertise ...

i need to hint somthing  the exchage Database in mount to SAN Storage ..

0
Login to vote
  • Actions
yunusf2's picture
yunusf2
cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail - Comment:27 Oct 2010 : Link

Iam having the same issue.  the fullbackup is running successfully , but the increment hangs showing snapshot pre3cessing

please help

0
Login to vote
  • Actions
alefesta's picture
alefesta
cremental or deferential the snapshot processing take long time and the exchage stop sending or receiving mail - Comment:29 Oct 2010 : Link

Please check/try the following:

1) in the exchange server check the vss writers:from the CMD type vssadmin list writers and check if the Exchange writer is "ready" or ina "retriable" state..in the last case do a reboot of Your exchange server.

2) did you manually deleted the log files on exchange or the full backup missed to delete some log files, if so, clean the log files with the exception of today and the day before than run a full backup.

3) delete all the exchange job backup and recreate them completly before test the job again.

let me know if it works.

Alessandro Festa

mail:a-festa@edist.it

******************

EDIST Engineering Srl

Via Goito 51/A

10095 Grugliasco TO

*********************

0
Login to vote
  • Actions