Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> SharePoint Products and Technologies >> SharePoint - Setup, Upgrade, Administration and Operation

MOSS native backup slow performance after start of daylight saving time.

The backup for my MOSS farm have gone from 40 minutes to 7 hours, since the daylight savings time change. There appears to be a pause for 1 or 2 hours at certain points during the backup. Note times below.

I have seen discussions about this on google groups, but no real solution. Just work arounds like uninstalling the DST patch 931836 and changing the MOSS servers timezone to a location that has the same time as DST. I'm hoping for a real fix.

[3/13/2007 9:30:45 PM]: Progress: [UserProfileApplication] 50 percent complete.
[3/13/2007 9:30:45 PM]: Verbose: Starting object: SessionStateSharedApplication.
[3/13/2007 9:30:45 PM]: Verbose: Starting object: Shared Search Index.
[3/13/2007 9:30:45 PM]: Progress: [Shared Search Index] 50 percent complete.
[3/13/2007 10:31:01 PM]: Verbose: Starting object: SharedServices1_Search_DB.

[3/13/2007 10:31:39 PM]: Verbose: Starting object: Windows SharePoint Services Help Search.
[3/13/2007 10:31:39 PM]: Progress: [Windows SharePoint Services Help Search] 50 percent complete.
[3/13/2007 10:31:39 PM]: Verbose: Starting object: Search instance.
[3/13/2007 10:31:39 PM]: Progress: [Search instance] 50 percent complete.
[3/14/2007 12:32:01 AM]: Verbose: Starting object: WSS_Search_FFEUSPLMSAP212.

[3/14/2007 12:32:09 AM]: Verbose: [WSS_Search_FFEUSPLMSAP212] SQL command completed at: 3/14/2007 12:32:09 AM.
[3/14/2007 12:32:09 AM]: Verbose: Starting object: Search instance.
[3/14/2007 12:32:09 AM]: Progress: [Search instance] 50 percent complete.
[3/14/2007 2:32:31 AM]: Verbose: Starting object: WSS_Search_FFEUSPLMSAP211.

[3/14/2007 2:32:38 AM]: Progress: [Windows SharePoint Services Help Search] 100 percent complete.
[3/14/2007 2:32:39 AM]: Verbose: Starting object: Search instance.
[3/14/2007 3:32:41 AM]: Progress: [Search instance] 100 percent complete.
[3/14/2007 3:32:42 AM]: Verbose: Starting object: WSS_Search_FFEUSPLMSAP212.
[3/14/2007 3:32:42 AM]: Verbose: Starting object: Search instance.
[3/14/2007 4:32:48 AM]: Progress: [Search instance] 100 percent complete.

[2140 byte] By [BernardL] at [2008-1-1]
«« Cannot sign in to communications service error on Vista (credentials prompting)?
»» SQL Query To Sum Two Columns Values Based on Its Record
# 1
In Cologne (Germany) we are experiencing the same problems since we switched to DST saturday night. We found this KB article, but at first sight it does not seem to fix the problem: http://support.microsoft.com/kb/932563.
TomHeylen at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 2

yea this is happening alot. I will try to get some more info on this but for now this will help.

Try this. STSADM.EXE –o execadmsvcjobs

BobFoxMVP at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 3
OK, we will integrate it in our scripts for now. Thnx for the info.
TomHeylen at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 4

I am running my backup by using STSADM, from the command prompt. I started my backup, waited until the job" hung" on the Shared Search Index, and then tried executing the command "stsadm -o execadmsvcjobs" command. Nothing happened.

When the backup job hangs, I go to Central Admin | Operations | Timer Job Definitions.

Look for the Search Backup and Restore item under the Title column. Select the link, on the Edit Timer Job page click delete button.

This will allow the job to proceed to the next hang point. Repeat the procedure until the backup job completes. This works, but who is going to login at night to delete timer jobs.

Bernard

BernardL at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 5

Two other methods to try:

Run the backup via a script. No need to exectute the previous fix

stsadm -0 backup -directory \\servername\backup_FolderName -backupmethod Full

Fire this off in a Scheduled task or manually and you will be fine...

Or

What i found that was interesting is leaving the GUI sit there for an hour... or simply go home Smile In an hour it eventually will kick off with no intervention needed.

HTH

BobFoxMVP at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 6

Hi,

The issue still occurs when executing through a script, here at least.

My backup seems to be taking longer than 1 hour, more like 2-4 hours.

I'm in GMT 0 (with DST/BST). If I change to a GMT0 zone without DST, sharepoint backup works fine, but causes Symantec BE to fail (presumably because it's out of synch with the other servers).

Anyone know whether MS plan to fix this any time soon?

Thanks

michaeleastaugh at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 7

Hey Michael,

I saw a thread last evening that a fix was being worked on. I will post back when this does go out but im sure the Sharepoint Team Blog will have this information out before anyone else. Keep that site on your radar.

BobFoxMVP at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 8

Yes, post when the fix is available.

I am executing the backup via a script and my backup is still running 6-7 hours, when it was taking 45 minutes.

BernardL at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 9
Ok thanks Bob, will do.
michaeleastaugh at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 10

I was experiencing similar problems (backups would hang). In my case it was because WSS 2.0 and 3.0 were installed on the same server. The problems went away once I disabled the WSS 2.0 "SharePoint Timer Service". (Don't confuse that service with the WSS 3.0 "Windows SharePoint Services Timer" service.)

After that (and possibly a reboot), I no longer experience the problem. I can start a farm backup and it runs immediately and completes in a matter of minutes, not hours.

BrianSmith at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 11
Just curious to all that were experiencing this problem... does it still exist?
BobFoxMVP at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 12

Hi Bob,

The problem seems to have resolved itself here.

Thanks

Mike

michaeleastaugh at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 13

Since the beginning of april we don't have the problem anymore.

Tom

TomHeylen at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 14

Ah that old Microsoft Easy Button comes back into play Smile

Glad all are back working normally again.

BobFoxMVP at 2007-9-12 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
SharePoint Products and Technologies
SharePoint - Setup, Upgrade, Administration and Operation

SharePoint Products and Technologies Hot Topic

SharePoint Products and Technologies New Topic

SharePoint Products and Technologies

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified