I have a single Windows Server 2016 Hyper-v host that’s running our DC within a VM. I just happened to check the backups on the host and noticed they were completing but with errors since 4/22. The site is a very remote location but I do have remote access to both the host and VM. How can I narrow down what the cause of this error is? The external drive that's the backup target test as "ok".
Win server backup 2016 hyper-v host backups completed with warnings.
Backup only doing incremental
I have (5) 2TB USB drives that I backup about 1.5TB of data. Drives are for each day of the work week (Monday through Friday). I have it backing up system state, full bare metal, and volumes C and E.
When first creating the backup I noticed it did full-backups, however for over a week now it's only been doing incremental on volumes C & E.
I went under configuration performance and set them manually to do a full backup however it's still only doing incremental.
My concern is if the server crashes and I have to do a full restore, how can I get to the data for C & E since all 5 drives are incremental backups?
Can someone explain to me how this process works in regards to the WSB application?
2008 R2 - Stopped loading with Raid 0 after upgrade.
Windows Server 2016 Essentials Backup completed with warnings.
We have been having an ongoing issue with the built-in Windows Server Backup on our Windows Server 2016 Essentials. It has been very inconsistent since install of the server. We may get a run of 3 or 4 successful backups then a run of 3 or 4 backups that say completed with warnings. The error we are getting when it completes with warnings is Windows Server Storage VSS Writer - The writer's timeout expired between the freeze and thaw events. We have already increased the timeout and the server is currently up-to-date with updates.
The EFI System Partition, C Drive, and Recovery backup without issues. The Bare metal recovery back says backup failed to complete. The System state says backup canceled. System state backup was canceled.
Event 8193 Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid
Hello All,
We have a reoccurring event 8193. From what I could gather on line this is regarding a backup issue with the SID. Non the less, would like to cover all my bases since have not found anything specific for this faulty module.
Can someone help me out with the basics: Where is this coming from? Do we need to take up any measures? is this high impact? how to resolved if needed.
Thank you all in advanced.
Log info
--------------------------------------------------------------------------
Volume Shadow Copy Service error: Unexpected error calling routine ConvertStringSidToSid(S-1-5-21-3912081775-2972631207-1420028119-2182.bak). hr = 0x80070539, The security ID structure is invalid.
.
Operation:
OnIdentify event
Gathering Writer Data
Context:
Execution Context: Shadow Copy Optimization Writer
Writer Class Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Name: Shadow Copy Optimization Writer
Writer Instance ID: {0d22a722-80c3-4c36-9ab4-723896da904a}
32 bit Windows Server backup restore to 64 bit
Dear All,
I have windows server 2008 standard 32 bit. I want to use 64 bit architecture. Can i restore 32 bit windows image backup on 64 bit architecture windows server?
How to upgrade 32 bit to 64 bit with existing data?
On this server SQL server 2008 R2 and some usefull application.
Many thanks.
KB2781272 - Anywhere on this planet where I can get this hotfix?
I am in need of KB2781272 for my Windows Home Server 2011 but all links to its existance are no longer valid. I understand that support for this product stopped in April of 2016 but I am only looking for a hotfix file that, I would assume, still exists someplace. I am not looking for support, just the hotfix. Does anyone know where I can find it? Microsoft support has taken the attitude that its a dead product and will not seem to help. Not sure why there is no archive of old hotfixes someplace. Anyone have any ideas where I might be able to get this hotfix?
Thanks.
Bill
"Access denied" trying to restore files from backup
I've got Windows Server Backup on Server 2012 R2, and it's run flawlessly for years.
Last week I copied a folder from another computer to the server, and modified permissions on it so that only 2 users had access to it (a user, and the Administrator).
When I tried a test recovery from the nightly backup (Windows Server Backup), I suddenly cannot browse ANY previous day's backup, even prior to the new folder existing. When I expand the server name, I now just get:
"Unable to browse System Reserved. Access is denied" and
"Unable to browse Local disk (C:). Access is denied
These errors only showed up after adding the user folder last week, and modifying its permissions.
Once I saw that error, I went back to the permissions on the new folder and added the user "SYSTEM", with full permissions. But it has made no difference.
Has anyone ever seen this before?
Thanks
Dave
David Ewer
2008 R2 - Stopped loading with Raid 0 after upgrade.
Active directory backup and recovery tool
Hi, I am looking for a suitable tool for Active directory backup and recovery for my organization .
Currently we are using Quest recovery manager tool for AD Backup & recovery.
We've found some alternatives like ;
- ManageEngine's Recovery Manager Plus
- Veeam Backup and Replication
Please suggest which one is most relevant for the production environment and comparatively close to quest recovery manager.
Windows Server - System State Backup Failed
Hello Friends,
I am facing Windows Image backup failed with following error "The backup operation that started at '2016-09-29T15:30:19.165612500Z' has failed with following error code '0x8078014D' (There was a failure in updating the backup for deleted items.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved".
Windows Server version - 2012R2 Standard.
Log Name: Microsoft-Windows-BackupSource: Microsoft-Windows-BackupDate: 9/29/2016 9:07:27 PMEvent ID: 5Task Category: NoneLevel: ErrorKeywords: User: SYSTEM Computer: XXXXXXXXXXDescription:The backup operation that started at '2016-09-29T15:30:19.165612500Z' has failed with following error code '0x8078014D' (There was a failure in updating the backup for deleted items.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Backup" Guid="{1DB28F2E-8F80-4027-8C5A-A11F7F10F62D}" /> <EventID>5</EventID> <Version>3</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x4000000000000000</Keywords> <TimeCreated SystemTime="2016-09-29T15:37:27.619425900Z" /> <EventRecordID>1863</EventRecordID> <Correlation /> <Execution ProcessID="156" ThreadID="4400" /> <Channel>Microsoft-Windows-Backup</Channel> <Computer>XXXXXXXXX</Computer> <Security UserID="S-1XXX" /> </System> <EventData> <Data Name="BackupTemplateID">{2BB1F66E-7E8B-42DC-9396-0824F430D4FC}</Data> <Data Name="HRESULT">0x8078014d</Data> <Data Name="DetailedHRESULT">0x8078004f</Data> <Data Name="ErrorMessage">%%2155348301</Data> <Data Name="BackupState">12</Data> <Data Name="BackupTime">2016-09-29T15:30:19.165612500Z</Data> <Data Name="BackupTarget">\\DC-JKT\Backup-JKT\DC-JKT</Data> <Data Name="NumOfVolumes">1</Data> <Data Name="VolumesInfo"><VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="7" HResult="-2139618995" DetailedHResult="0" PreviousState="15" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="0" HasSystemState="1" IsCompacted="0" IsPruned="1" IsRecreateVhd="0" FullBackupReason="4" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1572" BackupTypeDetermined="1" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo></Data> <Data Name="SourceSnapStartTime">2016-09-29T15:30:19.134336600Z</Data> <Data Name="SourceSnapEndTime">2016-09-29T15:31:30.095919100Z</Data> <Data Name="PrepareBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="PrepareBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="BackupWriteStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="BackupWriteEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="TargetSnapStartTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="TargetSnapEndTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="DVDFormatStartTime"><TimesList></TimesList></Data> <Data Name="DVDFormatEndTime"><TimesList></TimesList></Data> <Data Name="MediaVerifyStartTime"><TimesList></TimesList></Data> <Data Name="MediaVerifyEndTime"><TimesList></TimesList></Data> <Data Name="BackupPreviousState">16</Data> <Data Name="ComponentStatus"><ComponentStatus></ComponentStatus></Data> <Data Name="ComponentInfo"><ComponentInfo></ComponentInfo></Data> <Data Name="SSBEnumerateStartTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="SSBEnumerateEndTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="SSBVhdCreationStartTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="SSBVhdCreationEndTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="SSBBackupStartTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="SSBBackupEndTime">1601-01-01T00:00:00.000000000Z</Data> <Data Name="SystemStateBackup"><SystemState IsPresent="1" HResult="-2139618995" DetailedHResult="-2139619249" /></Data> <Data Name="BMR"><BMR IsPresent="0" HResult="0" DetailedHResult="0" /></Data> <Data Name="VssFullBackup">false</Data> <Data Name="UserInputBMR">false</Data> <Data Name="UserInputSSB">true</Data> <Data Name="BackupSuccessLogPath">C:\Windows\Logs\WindowsServerBackup\Backup-29-09-2016_15-30-19.log</Data> <Data Name="BackupFailureLogPath">C:\Windows\Logs\WindowsServerBackup\Backup_Error-29-09-2016_15-30-19.log</Data> <Data Name="EnumerateBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="EnumerateBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="PruneBackupStartTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="PruneBackupEndTime"><TimesList><Time Time="1601-01-01T00:00:00.000Z" /></TimesList></Data> <Data Name="BackupFlags">0x9</Data> <Data Name="ComponentInfoSummary"><ComponentInfoSummary ComponentInfoArrayPresent="1" TotalComponents="0" SucceededComponents="0" /></Data> </EventData></Event>
Thanks in Advance
System image restore failed: The mounted backup volume is inaccessible (0x8078004F)
Hello,
Our physical Windows 2016 servers are making backups with Windows Server Backup to an iScsi connected disk.
This way we can store our backups on another location and have the benefits of incremental backups, which would not have worked over an regular network share.
During a disaster recovery we would then connect the iScsi disk to another server.
On the server we use "VSSADMIN LIST SHADOWS" to find the shadowcopy of the date that we want to go back to.
Then using "MKLINK /d <symbolic-link> <target>" we make that shadowcopy available for usage. Within the file explorer you can see the link and also view de WSB data, with the modified date of that specific point in time.
On this symbolic link we create a share so the system that needs te be restored can be pointed to get the WSB data from there.
This works and all is fine.. So far so good.. but now the problem we encountered.
That was in de WSB data from a point in time perspective.
One DR test worked without any problems and we could restore the system by using a shadowcopy from let's say two days back in time.
On another server we used the exact same procedure but the restore of two days back in time failed and gave the error:
"System image restore fialed: The mounted backup volume is inaccessible. Please retry the operation (0x8078004F)"
By trial and error I found out that the first WSB data back in time that was usable was from 40 days ago. All other shadowcopies untill the one that was made last night failed and could not be used.
Now we have some questions which we haven't found an answer to so far..
Q: Most important.. Is there any way that we can perform a health check of WSB data from our other servers that we haven't checked yet?
Q: Does anyone have a possible answer to why all WSB data after a date is not useable anymore. Personally I have a gut feeling that is has something to do with all being differentials.
Q: Can we limit the number of days of unuseable data by forcing a full backup once a week and the other days differential.
VM's hanging or save mode after Hyper-V Windows backup
Hi
I have 2 VM's in the Hyper-V and its hanging after the completion of windows backup. This is started after the update of Hyper-V integration service. From the event viewer it showing the error"VM_Name: The Volume Shadow Copy integration service is not
enabled". But the service is enabled for Manual(Trigger Start) under services.
Thanks
Michael
How to run restore from backup in safe mode?
So after last update my w2k8r2 is unable to stay afloat for so long that is required to roll back, it resets and ask me reason for shutdown afterwards. Safe mode seem stable, but does not allow me to restore the system. I found in some discussions that backup service requires shadow copy service to run, but if I try to start that service I get the very same message that it cant be run in safe mode. Seems like a bug, maybe conceptual?
I need to override this VERY FAST and do the restore in safe mode. How?
Full Backup of Windows 2012 Domain Controller
Port requirements for Windows Server Backup to backup to a remote drive
Windows server 2008 Sp2 32 bit Azure Backup
SQL Server and Windows Backup Bug/Issue.
Hello,
I have two servers, both with Windows 2019 STD + SQL Server 2017 STD installed.
The hosted MS SQL Databases are being replicated using Basic Always on Availability Groups, while testing Windows Server Backup (full server backup) on the primary and secondary SQL Server, I've found out that the backup completes successfully on the primary server, but on the replica server the backup finishes with errors.
Before jumping to conclusions, during the testing period I used SQL Server 2017 Evaluation (feature level equivalent to SQL Server 2017 Enterprise), with the same configuration, and on both primary and secondary servers, Windows Server Backup finishes without issues.
The reason it doesn't work on the Standard version of SQL Server 2017 is because the secondary replica cannot be set to readable during the backup process, and so the backup finishes with errors.
The error as shown in the Event Viewer:
Log Name: Application
Source: SQLWRITER
Date: 9/10/2019 12:52:52 AM
Event ID: 24583
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVERNAME
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 11.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 976
Error state: 1, Severity: 14
Source: Microsoft SQL Server Native Client 11.0
Error message: The target database, 'WideWorldImporters', is participating in an availability group and is currently not accessible for queries. Either data movement is suspended or the availability replica is not enabled for read access. To allow read-only
access to this and other databases in the availability group, enable read access to one or more secondary availability replicas in the group. For more information, see the ALTER AVAILABILITY GROUP statement in SQL Server Books Online.
Is there any way to do a full server backup on the secondary replica server? I mean other than doing a fail over, backup and then fail back to primary.
Thank you!
Erro no processo de copia de segurança.
Nome do registo:Application
Origem: Microsoft-Windows-Backup
Data: 10/09/2019 12:51:43
ID do evento: 517
Categoria de Tarefa:Nenhum
Nível: Erro
Palavras-chave:
Utilizador: SYSTEM
Computador: (XXXXXXXXXXXXXXXXXXXX)
Descrição:
A operação de cópia de segurança iniciada em '2019-09-10T15:10:11.095744600Z' falhou com o seguinte código de erro '0x80780102' (O escritor de sistema não foi localizado na cópia de segurança.). Consulte os detalhes do evento
para obter uma solução e, em seguida, execute novamente a operação de cópia de segurança após o problema estar resolvido.
Evento Xml:
<Evento xmlns = "http://schemas.microsoft.com / win / 2004/08 / events / event">
<Sistema>
<Nome do provedor = "Microsoft-Windows-Backup" Guid = "{1DB28F2E-8F80-4027 -8C5A-A11F7F10F62D} "/>
<EventID> 517 </EventID>
<versão> 1 </Version>
<Level> 2 </Level>
<Task> 0 </Task>
<Opcode> 0 </Opcode>
<Palavras-chave > 0x8000000000000000 </Keywords>
<TimeCreated SystemTime = "2019-09-10T15: 51: 43.921609000Z" />
<EventRecordID> 846932 </EventRecordID>
<Correlação />
<Execution ProcessID = "17204"ThreadID = "10520" />
<Channel> Aplicativo </Channel>
<Computer> (XXXXXXXXXXXXXXXXXXXX) </ Computador>
<Security UserID = "S-1-5-18" />
</System>
<EventData>
<Data Name = "BackupTime"> 2019-09-10T15: 10: 11.095744600Z </Data>
<Data Name = "ErrorCode "> 0x80780102 </Data>
<Data Name =" ErrorMessage "> %% 2155348226 </Data>
</EventData>
</Event>
Copyright (C) 2012 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> VSSADMIN LIST WRITERS
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Waiting for responses.
These may be delayed if a shadow copy is being prepared.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {093a98ed-c990-4618-9644-a0b27a3b3c49}
State: [1] Stable
Last error: No error
Writer name: 'WIDWriter'
Writer Id: {8d5194e1-e455-434a-b2e5-51296cce67df}
Writer Instance Id: {91955040-94b1-4ca9-9aa2-4d570392b2dc}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {8f2f7629-def9-4e56-af47-70c6b3ea27d7}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {9f5d5002-a97d-45d0-aaf8-272f7bcf2e09}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Azure Backup Agent - Offline backup - Unable to locate Azure Powershell
Hi,
I have installed MS Azure Recovery Service Agent on a W2K8 R2 SP1. I'm trying to schedule the first offline backup. I receive the error "Unable to locate Azure Powershell on this server". All the prerequisites are met, IE11, MARS Agent 2.0.9169, Powershell 5.1, .Net 4.7.2, Powershell Azure module installed.
Do you have an idea?