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!

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> 

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?

Hi,

We have configured windows server backup scheduled backup option.

we are able to run the backup manually, but the scheduled job is failing.

After checking further, the scheduled task is failing to launch.

The following is the event:

Task Scheduler failed to start "\Microsoft\Windows\Backup\Microsoft-Windows-WindowsBackup" task for user "XXXXXXXXX".

Additional Data: Error Value: 2147943726.

please advise.

Thanks in advance

Ekachakra

I am trying to use WSB to backup my Hyper-V VM's from a Server 2016 system.  Actually this is happening on two identical servers. 

When trying to backup a VM, it completes the Host component but fails on the actual VM.  It fails immediately with the following error(s).  The ETL file I have opened using Windows Performance Analyzer but I have not idea what the content means.  Can someone please look at this and point me in the right direction?  This is not new technology.  It was available in Server 2012r2.  It should not be this difficult.   Thanks already

Details:

Event ID:  1001

Fault bucket , type 0

Event Name: Windows Server Backup Error

Response: Not available

Cab Id: 0

Problem signature:

P1: 2

P2: 1

P3: 0x00000000

P4: 0x00000000

P5: 0x00000000

P6: 0x00000000

P7: 0x00000000

P8: 0x8100010f

P9:

P10:

Attached files:

\\?\C:\Windows\Logs\WindowsServerBackup\WBEngine.0.etl

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER28B2.tmp.WERInternalMetadata.xml

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_7ba82da1c416ce745c85c91194d9cc184b6e2abf_00000000_cab_2e7e2a58

Analysis symbol:

Rechecking for solution: 0

Report Id: dd92e97e-d89c-11e9-842b-1866dab7c9fd

Report Status: 100

Hashed bucket:

 
Some of the attached files reference above are either not present or I am not sure how to use them.

Below is the contents of the log file in the C:\Windows\Logs\WindowsServerBackup folder 

Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {D2616CFA-F481-48A9-9E91-BCBAF048E5F6}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)   
  Component: 72D8F630-F1C7-4520-A32F-1437E7697280   
  Logical Path:   
  Component Result: 8100010F   
  Component Message: Component reports path on volume which has been excluded. (0x8100010F)

*-----------------------------*
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}   
  Component: 72D8F630-F1C7-4520-A32F-1437E7697280   
  Caption     : Online\Poly-DC1   
  Logical Path:   
  Error          : 80780175   
  Error Message   : Component was skipped from volume shadow copy.
  Detailed Error  : 8100010F   
  Detailed Error Message : Component reports path on volume which has been excluded.
*-----------------------------*

I have  following query regarding Tape Loader integrated with Windows server.

I have windows 2008 server and Dell Powervolt TL2000.

• Is it possible to take windows server 2008 backup from backup and restore feature of windows to Dell Powervolt TL2000   tape Library.
• Windows 2008 server support backup directly to  Tape Library (Without any 3^rd party software) .

Hello,

I implemented my first 2016 server a few weeks ago. I've been having intermittant problems with back ups, and the cause seems to be that the log file is locked so a new back up doesn't start.

Here is my script run with a scheduled task (ip changed)

It's the backuplogs.txt that is staying locked after backups. Then when the next run of the backup happens, it can't open the file so the backup doesn't run.

It can go 1 to many days just fine, then one day it stays locked and no more backups work (with task or manually run) until I restart the server(which unlocks the file), then they the work fine again.

Can anyone please tell me why this file is staying locked sometimes? Backing up to a synology disk station that is up to date.  The VM on this same server never fails (but no system state on that backup). Server 2012 backing up to same device has no problems either.

The backup file is very useful so I'd like to keep it. I could append the date I guess to the file name but I'd rather it just work.  

We have Server 2012 standard Domain controllers. The PDC is being backed up daily using windows backup utility. We keep 7 last backups. The backup selection is full backup including system State and all drives. Back target location is Drive letter V which is a LUN mounted as Disk. 

We are trying to test restore to an isolated Lab build on HyperV. The Hyper V host is connected to production network but in a work group. We created "Internal Virtual Switch" in Hyper V so that guest machines can only communicate between and hyperV host but not to the production network. 

I started by copying the "WindowsInageBackup" folder from V drive of production domain controller backup location to C drive of HyperV host and shared it. I then build a vanilla windows 2012 server as guest on hyperV host. I booted the guest VM  with OS CD and pressed F8 to chose Repair computer> Troubleshoot>System Recovery >  System Image Recovery> System attempt to find recovery files, I then "Select an image" >Advanced>Search System Image on network> enter UNC path as \\<HyperV-Host-IPAddress\ShareName. I get prompted to login, but after login no restore files found. 

I tried several combination of share and tried to share upstream downstream folders. When I use command line in recovery mode, I can ping host machine, I can map share, see share files and folders in command line. 

When I use wbadmin get version XXXXX I get error about Time Zone is -8GMT no backup files found. 

So for some reason, the image files are not being detected. 

I even tried to take a system state backup of guest machine using target location as Host Machine. Still I dont find restore files when recovering.. 

I am not sure where its going wrong... 

Any clue will be greatly appreciated as I have spent lot of time figuring out the fix. 

Thanks a lot

SA

NSW DECC

Windows Server 2019 has good integration with Linux systems, and OS can be run on Windows. How does it optimize better? How do the costs lower?

Any detailed explanation would be really helpful. 

Thanks
Elisha

Hi Folks,

I'm trying to run a backup on one of my 2012 DC's using wbadmin's -allcritical switch. The backup is being directed to a network share on a Netapp. The machine is a VM running on VMWare, however, other physical 2012 servers are able to backup to this Netapp successfully. The syntax being used is:

wbadmin start backup -backuptarget:"\\fileserver\VM Backup\MYDC\1st" -include:c: -allcritical -vssfull -quiet > "c:\scripts\Server Backup.log"

Strangely, the 350 MB 'System Reserved' partition auto-created during the Windows install seems to back up and copy fine, but the C: drive will not. I have tried directing the backup to a different network share with the same result. I have wbadmin running sucessfully on 5 other 2008\R2 servers (also VM's running from the same VMWare server) against the same network share.

Any ideas on this? I'm not really finding much on it I'm afraid. Thanks for any help,

ianc

Below is the output from the log: 

Retrieving volume information...
This will back up System Reserved (350.00 MB),MYDC(C:) to \\fileserver\VM Backup\MYDC\1st.
The backup operation to \\fileserver\VM Backup\MYDC\1st is starting.
Creating a shadow copy of the volumes specified for backup...
Creating a shadow copy of the volumes specified for backup...
Creating a backup of volume System Reserved (350.00 MB), copied (56%).
The backup of volume System Reserved (350.00 MB) completed successfully.
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
Creating a backup of volume MYDC(C:), copied (0%).
The backup of volume MYDC(C:) could not be completed. Error: The mounted backup volume is inaccessible. Please retry the operation.
Summary of the backup operation:
------------------

The backup operation stopped before completing.
The backup operation stopped before completing.
Detailed error: The mounted backup volume is inaccessible. Please retry the operation.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-02-01-2013_21-17-33.log

Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-02-01-2013_21-17-33.log

There was a failure in preparing the backup image of one of the volumes in the backup set.
The mounted backup volume is inaccessible. Please retry the operation.

I've got a server running Server 2012 R2 Standard with a 21TB volume that I need to backup. Unfortunately it appears that WSB isn't capable of backing up a volume of this size. I've searched and have not been able to find any definite volume limit in the documentation.

Has anyone else run into this?

Thanks,

Dewayne

Hi,

I am trying to do a backup on my AD server (Server 2012 R2 with latest patch) using Windows Server Backup, however, I encountered error when doing a full backup.  It stated "system writer is not found in the backup".  

In Event Viewer, error ID 513 is logged as well.  

CAPI2 Event Properties 513

Cryptographic Services Failed while processing the OnIdentity() call in the System Writer Object. 

Details:

AddCoreCsiFiles: RtlConvertNtFilePathToWin32Path() failed. 

System Error: 0xC0000039 (unresolvable)

The backup Operation that started at ‘2019-09-24T00:55:27.911302400Z has failed with following error code ‘0x80780102’. (The system writer is not found in the backup.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. 

System writer is indeed not shown when I executed "VSSadmin list writers" in command prompt.  

I have found some solution online but I am uncomfortable with the instructions, such as, amending file permissions.  I have two ADs running and both encountered the same.  I am not able to do backup prior to changes, hence, I need to be very careful not to destroy my ADs with the steps.  From the past logs, it seems that this problem happened since day one.  

Would anyone be able to share more with me?  Appreciate lots in advance.  

Hi,

We have just installed a Windows 2016 Hyper-V server and I wanted to check if this version of Windows Server Backup can protect Hyper-V VMs running Windows 2008 R2 and later.  I also wondered if it could back up a VM running Windows 2008, although this may not be necessary yet.

Thanks

Chris

Hello All ,

I have CISCO Blade physical server. I have taken baremetal and data drive backup of the server.

While restoring it from the network I am getting this error.
"System image restore failed with error: 0x807800B8"

When I try to do restore from another disk within the same Server, it work fine.

Any help much appreciated.

Thanks

We have Windows Server 2012 software running on an HP Proliant server that lost the system disk over the weekend. I saw some disk errors on Friday and ordered a replacement drive to be delivered on Monday. I checked in Windows Server Backup and noticed that there were numerous backups of the system. I thought that I had stopped the scheduled backups. So I left for the weekend planning on replacing and restoring the system disk on Monday.

Monday morning the server was down because the system disk had completely failed and won't mount. So I booted from the distribution DVD and looked at the available backups. Nothing was displayed on the System Image recovery.

I moved the drive over to another Windows 2012 server and looked with backup. There were only 2 backups, both over the weekend with the C: drive not having a backup (because of drive errors?). None of the previous backups were on the drive.

The system disk only contains the OS and applications. All application data is kept on a storage space array on the same machine. The storage array is working fine and I don't wish to mess with it.

So I went to a drive with older backups. I attempted to restore using the booted distribution. I excluded the storage array and got a message saying that I had excluded a critical disk so the restore would not proceed. I forced the storage array offline with diskpart and got the same restore message. Then I physically removed all of the storage array disks and got a message about "failed to find enough suitable disks".

I went to another Windows server and mounted the backup disk. The most recent backup has only AD, FRS, Registry, System Reserved, System State. The older backup has AD, Bare Metal, Development (the storage array), Exchange, FRS, Local disk (C:), Registry, System Reserved, System State.

I tried restoring the "Local disk (C:)" item to an empty disk, but I could not get the disk to boot. I used bootrec to set up the boot information, but the HP red screened on power-up indicating it can't find a bootable drive. What did I do wrong?

My thought was to restore the C: drive, bring the AD up to date with DSRM, and add the software updates. I don't seem to be able to accomplish this. Does anybody have any ideas on how to get this machine back running?

I'm Using Windows Server backup.

I think there's a bug in the bare-metal restore  (Re-Image) Process in server2016TP5

I have created a Bare-Metal backup from Windows server 2016tp5, into a network shared folder.

The restore (Re-Image) process is loading the installation media, choose repair, and restore the image from the network.

what I did: Loading the Server2016TP5 ISO (Bootable USB), and trying to connect to the shared folder, It failed to connect to the server with the following error: "A specified logon session does not exist. It may already have been terminated (0x80070520)"

I get the same error for Hyper-V Virtual computer, and a Bare Metal (Physical) Server.

Why I think it is a bug ?

I tried to Bare-Metal restore the 2016TP5 with ISO of 2012R2, with exactly the same process (Same network account), it finds the backup files, but I get different error because it can restore Windows 2012R2 only (That error indicate that the backup data is accessible to the 2012R2 Re-Image process

I Also Try to bare-metal backup an restore 2012R2, on the same shared folder (Same account), It worked great on virtual, and Physical system.

can anyone confirm ?

did I do something wrong here ?