GerryRigney Posted May 13, 2009 Report Share Posted May 13, 2009 Retrospect 7.0 with all updates Windows Server 2003 We run a file backup every night with a different backup set for each night. It usually takes around 8 hours to run but for over a week now it's been more like 18. The same amount of data seems to be getting backed up and the performance also around the same (600MB/ M) The bulk of the extra time is in the idle/loading/preparing stage. From what I can see it's the snapshot part that's taking so long. I thought after a week of this they sets would be back on their normal performance but it's still happening. Is there any way to stop this other than greating new sets? I've tried repairing the cataloge but it's had no effect. Thanks for any help gR Quote Link to comment Share on other sites More sharing options...
GerryRigney Posted June 4, 2009 Author Report Share Posted June 4, 2009 Just an update on this post in the hopes that the problem might ring a bell with someone . . . . We recently created a new backup set and did a full backup, after a week we had the new backup complete and last night was the 1st incremental backup to this new set. Unfortunatly, 9.30am this morning (starts at 10pm) it's still running. Looking at all the sets, the problem seems to be the creation of the snap shot for our biggest volume. It's the biggest volume (1.1TB of data). About 5GB of data changes and gets backed up and then it starts the snap shot. Snap shot is still running 12 hours later! Can anyone thing of a reason why this would suddenly have jumped 10 hours? Like I say, the amount of actual data being changed is always around the same. Thanks in advance for any thoughts you might have. I didn't want to go down the route of creating new sets but was was willing to if we had to, now seems even that won't solve the problem. Rgds Gerry Quote Link to comment Share on other sites More sharing options...
Mayoff Posted June 4, 2009 Report Share Posted June 4, 2009 This could be extra time saving ntfs permissions. 7.6 is MUCH faster in this phase of the backup. Quote Link to comment Share on other sites More sharing options...
GerryRigney Posted June 5, 2009 Author Report Share Posted June 5, 2009 Hi I just foud out what caused this problem yesterday evening and our backup last night was back to normal. We're running VSE 8.5 on our servers, we always had the "scan files open for backup" option turned on but it turns out that up until patch 8 for VirusScan that option was ignored (at least for some backup software) We pushed patch 8 to all machines over the past month or so, never twigged that the increase in backup times coincided with the patch deployment. So we turned that option off yesterday and the backup ran as normal. As the option was previously ignored we're no worse off having it disabled now. Anyway, just posted this in case someone else experiences the same problem, I believe it affects more backup software than just retrospect. gR Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.