Then the "WseComputerBackupSvc" gets stopped, I have to manually restart it.
When run, it generates in Event Viewer Error 267: Windows Essentials Computer Backup Service failed at (183) of (admin\serveressentials\backup\pc\utili\diskfile.cpp) and also Error 267: Windows Essentials Computer Backup Service encounteredĮrror Code 112 at F:\ API name SetEndofFile. When I try to Fix the error, or manually run the Essentials "Backup Cleanup" task in Scheduler (which by the way it always says "Completed successfully 0x0" but obviously not), it doesn't clear any space on the backupĭrive (F:). I get the error "A scheduled cleanup task for Client Computer Backup did not succeed." (& has not for 50 days) If you have feedback for TechNet Support, contact you! Please remember to mark the replies as answers if they help and unmark them if they provide no help. The drives should also be large enough to accommodate the future growth of your Your storage drives should contain at least 2.5 times the storage capacity of the data that you want to back up. This can improve your disaster preparedness planning by helping you recover your data if physical damage occurs to the hardwareĬhoose a drive that contains sufficient space to store your data. You can use multiple external storage drives for backups, and you can rotate the drives between onsite and offsite storage locations.
You can configure this cleanup task to delete old backups to get more free space.ĭetail information you may reference link below: >For server backup: The cleanup task(client computer backup) deletes backups from the client computer backup database according to the backup retention policy.
Since it is clear now that the problem I am having with this server has been around for a long time, it is too bad that it has been like pulling teeth to get to a solution and that the solution requires drastic action-and nothing (but consistent manual Worth a try before doing the scorched earth solution. Runs" when I try this on my test server, maybe in this situation Cleanup will work on the problem server. Although it says: "The existing backups will be deleted the next time Cleanup
It specifies complete backups database deletion as the solution for a full backup drive preventing Cleanup from functioning.īut before doing that, my next opportunity at the customer's site I will try to turn off client backup for a few low priority workstations, deleting existing backups.
Which is the closest thing, although it is for 2011 and apparently 2012 is different. As best I can tell it is just WseComputerBackupSvc. Restart the services or just reboot the server and tomorrow you should have some backups Once they are stopped you can just browse to the client backups folder, highlight all, hold down shift and press the delete key. You have to stop 2 services I think, The client backup service is one for sure, just stop them all :)Ĭlick start, type services.msc, the windows server essentials services. Is there something I am missing, or is something failing to work that can be fixed-or is it necessary for constant technician intervention to manually deal with backup drives filling? So, two independent backups managed by the server fail hard due to an apparent inability to do the basic task (an advertised feature) of making room on the drive for the next backup. Here again, the backup drive eventually filled, and from then on all server backups fail.īut in this case, the drive is inaccessible in Microsoft infinite wisdom, so cannot manually delete anything (unless format it and start over loosing prior backups). Now that server (total data 1.3 TB) is suffering a similar problem with the built-in Essentials server backup (to 3 TB USB ext HDD). To eventually fill no matter how large it is. I think the root cause is that the system is not deleting old backups that should no longer be retained, causing the backup drive
Reducing the number of days/weeks/months held, plus deleting things on the backup drive, then restarting the service. I find that the backup HDD is full, and Essentials client backup service has stopped. I've seen this with the client backup, where all the clients start getting the message that their backup failed. Both the Essentials (R2) client backup (to an internal drive) and the full server backup (to USB ext drive) appear incapable of properly removing old backups to make room, and from then on all backups fail.