Answered by:
Backup Service Stops After Sunday Cleaning & Backups

Question
-
This happens about every other week. According to event logs, the cleanup & backups ran fine. But when I later access Backup in Console/Settings, it says that the backup service has stopped running & I need to restart the server. I do this & then everything is fine for another week or two, but I wonder if this is a known problem that there is a solution for? I have run "Repair" on the backup database several times, but that doesn't seem to change things.
Thanks.Monday, January 5, 2009 9:19 AM
Answers
-
Have now uninstalled AutoExit. Will have to wait until Sunday night to see if it helps.
I cannot "break" the system at will. No matter what I do with manual repairs, cleanups, total deletions, etc., the backup service keeps running. It only stops running on Sunday night, after the automatic cleanup and the daily backups.- Marked as answer by Bobsie Monday, January 19, 2009 9:51 AM
Monday, January 12, 2009 4:41 PM
All replies
-
Hi,
maybe this problem can only be solved with a complete reset of the backup database (either with the old Windows Home Server Toolkit 1.0 or by deleting them manually through Windows Explorer). You will loose all backups that way, but also the faulty part in the database.
If you are registered at Connect or would be so kind to do it, you should create a bug report and send the CAB files, so that the WHS team can check, what is the problem with the repair process.
For manually deletion of the backup database you can use following method:
Login to your home server desktop.
Click Start / Run and type cmd. Click OK.
In the command prompt enter following commands:
d:
cd \folders\{00008086-058D-4C89-AB57-A7F909A47AB4}
net stop pdl
net stop whsbackup
del *.*
Check, if the folder still contains files.
If yes, try to get rid of them with the command
fsutil reparsepoint delete filename (replace file name with the name of the file, usually you can use the tab key to select the next file name)
If there are multiple files, you can try
For %i in (*.*) do fsutil reparsepoint delete "%i"
del *.* (again)
The directory should now be empty.
Check also the eventually available hidden folders
d:\DE\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\
c:\fs\<volumemountpoint>\DE\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}\
if there are still existing files. If yes, delete them as well.
Reboot the server.
Check, if you can run a backup and after it a cleanup without crashing out.
Best greetings from Germany
Olaf- Proposed as answer by kariya21Moderator Sunday, January 11, 2009 7:25 PM
- Marked as answer by Bobsie Sunday, January 11, 2009 8:18 PM
- Unmarked as answer by Bobsie Monday, January 12, 2009 7:50 AM
- Unproposed as answer by Bobsie Monday, January 12, 2009 7:55 AM
Monday, January 5, 2009 1:01 PMModerator -
I deleted all the backups early last week, using Toolkit 1.0. Unfortunately, yesterday's Sunday cleanup appeared to run fine, the subsequent backups ran fine, and then the backup service stopped running. The server is restarting now. Guess this will be a way of life, restarting the server every Monday morning. I've tried several times to join the Connect thing & file a bug report but it totally stymies me. Don't want to spend any more time on it.
Olaf, thanks for your advice.
I'm going to try to short-circuit this problem by manually starting a backup database cleanup on Sunday or maybe even Saturday. Maybe this will shake things up enough that the backup service will not stop running after the Sunday backups.
BTW, I have read every entry in the event viewer and there is absolutely no sign of trouble.Monday, January 12, 2009 8:24 AM -
Hi,
this sounds not very normal. Is the server a home built machine or a OEM one? How much memory does it have?
If the backup service stops, there must be a reason.
Could you login to your server and click Start/Run, type %qlogs% and pick the log files, which have been created around the crash time? (Set view in Explorer to Detail and sort by date.)
Can you open the backups from a client or does this also cause a crash?
Are drivers and Bios up to date and the drivers Windows Server 2003 compatible? (Especially the mass storage drivers may inflict some crash potential here.) I had a situation with original Server 2003, that handling large files on IDE drives (copy CD images and such stuff) caused Windows Explorer to hog more and more memory, until it left not enough resources for the remaining applications. Since these backup files are also not small, the reason could be similar.
Best greetings from Germany
OlafMonday, January 12, 2009 9:33 AMModerator -
This is a HP EX470 with RAM upgraded to 2GB
I've now gone to the server as you suggested & read through the several hundred entries in about a dozen logs that have been written since the last backup finished Sunday night. Nothing looks suspicious to me, but I don't really know what I'm looking for & I don't see any way to attach the logs here.
Also, I have now opened up, through the console, the latest backup from each of the 3 PCs being backed up. This did not cause the backup service to stop running.
I did a manual backup database cleanup and that also did not cause the backup service to stop running.
We'll see what happens after the regular backups tonight.Monday, January 12, 2009 10:01 AM -
Hi,
This is a HP EX470 with RAM upgraded to 2GB
this seems nearly to exclude lack of memory or driver issues.
Is there any other software running on the server (i.e. Virus scanner), which could cause a delay of the cleanup process, which is not liked by the process?
Best greetings from Germany
OlafMonday, January 12, 2009 11:09 AMModerator -
These add-ins are installed:
ASoft AutoExit (I probably don't really need this; maybe I should uninstall & see if the situation improves?)
WHS Disk Management
PVC Connect Media Server
avast! Antivirus
Grid Junction
WHS Toolkit 1.0
WebFolders4WHS
You mentioned the word "delay". I consistently see this kind of entry in the log for a "balancing" operation:1/11/2009 8:00:00 PM]
TraceCleanup: discarding log C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\DEUtil.010909.160000.2416.log
TraceCleanup: discarding log C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\DEUtil.010909.160000.3048.log
[1/11/2009 8:40:22 PM 420] Sleeping between passes 3601120.9047ms
[1/11/2009 8:40:22 PM 420] MigrationDisabled = 0
[1/11/2009 8:40:22 PM 420] Audit Grace Period is set to: 1440
[1/11/2009 8:40:22 PM 420] ***Starting Primary Pass
[1/11/2009 8:40:55 PM 420] Primary Pass: (duplication) 33561.3023ms
[1/11/2009 8:40:55 PM 420] ***Starting Secondary Pass
[1/11/2009 8:40:55 PM 420] Volume information -
Volume - Id = e00054e3-feed-4122-bfdb-c33ec60256de Size = 445 GB Free = 455971 MB
Volume - Id = f422714d-bae1-4a31-8c3b-6611f34ad880 Size = 931 GB Free = 832853 MB
Volume - Id = 2154140e-9eec-4474-b918-81951482a13a Size = 931 GB Free = 892489 MB
[1/11/2009 8:40:58 PM 420] ***ERROR: DEfileFromShadow(c:\fs\T\DE\shares\Photos\1999\My Pictures\lee12.jpg,e00054e3-feed-4122-bfdb-c33ec60256de) took too long. 1807.6367ms
[1/11/2009 8:41:14 PM 420] Secondary Pass: (balancing) 18690.3315ms
[1/11/2009 8:41:14 PM 420] Full Primary and Secondary Pass 52255.5106ms
Also, remember that the backups DO run after cleanup completion, and I DO find event viewer entries that say cleanup & each of the backups finished without a problem. After a whole lot of searching, never do i find a event viewer entry or a log entry that indicates the backup service has been stopped.Monday, January 12, 2009 11:34 AM -
Have now uninstalled AutoExit. Will have to wait until Sunday night to see if it helps.
I cannot "break" the system at will. No matter what I do with manual repairs, cleanups, total deletions, etc., the backup service keeps running. It only stops running on Sunday night, after the automatic cleanup and the daily backups.- Marked as answer by Bobsie Monday, January 19, 2009 9:51 AM
Monday, January 12, 2009 4:41 PM -
No problem this week; I'll assume AutoExit was the culprit.Monday, January 19, 2009 9:51 AM