Attempting to perform backup on Server 2016 and keep getting this error:

VSS error 0x800423f2: The writer's timeout expired between the Freeze and Thaw events. 

I have attempted the recommended registry fix to extend the timeout times which have not resolved the issue.

Have also re-registered the services.

All updates are installed. Unit is NOT running Sophos AV which has been known to cause this issue.

Any ideas? Thank you!

Could someone tell me how would I backup window server full every Friday, and then each day is incremental?? Recently in the past, it backs up Full, and then each day is incremental, as shown on the picture below.  When I schedule it in "window task schedule" to every Friday, then the backup is not occurring not even incremental everyday. Please tell me how I can backup window server full every Friday, and then each day is incremental. Thanks.

Jason Chang

Hawaii  

Jason Chang

Hello,

Server - HPE Proliant DL360 Gen10
OS - Windows Server 2012R2

100GB C: Drive - GPT Partition
100MB EFI Partition
350MB Recovery Partition
200GB Backup Partition - MBR

Trying to do full server backup (bare metal, system state, efi, and c:) and backup fails.  On the EFI partition and system state I get 'Handle is invalid'  If I check logs, I get

Backup of volume \\?\GLOBALROOT\Device\HarddiskVolume2\ has failed. The handle is invalid.

After this failed backup, getting into Server Backup GUI or Disk Management/diskpart is impossible.  Must reboot server to make it work.

I've tried to use vssadmin to change location of shadowstorage, but I get invalid options error

Ideas?

Hi All

I've tried to create a Full Server Backup schedule through the wizard as well as through wbadmin in command prompt. I'll paste the command prompt here which is the same error I get when I try to add the schedule through the Windows Server Backup schedule:

wbadmin enable backup -systemState -allcritical -schedule:21:00 -addtarget:{6ef6b4bf-0000-0000-0000-000000000000}
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Retrieving volume information...
The scheduled backup settings:

Bare metal recovery : Included
System state backup: Included
Volumes in backup: Local Disk(C:),System Reserved (100.00 MB)
Files excluded: None
Advanced settings: VSS Backup Option (COPY)
Location to store backup: StoreJet Transcend USB Device
Times of day to run backup: 21:00

Do you want to enable scheduled backups with the above settings? [Y] Yes [N] No
y

Do you want to format and use StoreJet Transcend USB Device (that includes volumes D:) as the location to store scheduled backups? [Y] Yes [N] No
y

Label the backup disk as SERV 2019_03_25 11:54 Disk_01.
This information will be used to identify this backup disk during a recovery.
The operation to format the disk failed. Please ensure the disk is online and accessible.

The system cannot find the file specified.

Any assistance would be appreciated!

Thanks

Hello.

I am a Korean and a backup engineer.

I'm writing this article that I want to ask for help.

Can IBM Windows Server 2008 R2 server recognize LTO 8 Drive?

If that is the case, please get the hotfix.

It was not Google but there was no search found.

Help me.

We look forward to your answers.

Hello,

I'm creating a script to automatize my Wsus offline. I created a backup from the source server and I want to restore it on the destination server using powershell Server backup cmdlets.

Here is what I've done so far:

on the source server:

wsus is on E:\Wsuscontent
I backup to a USB drive I:\

On the destination server:

Wsus is on e:\wsuscontent
Backup is on \\mynas\backup

To restore I use: 

$BackupLocation = New-WBBackupTarget -NetworkPath "\\mynas\backup"
$Backups = Get-WBBackupSet -BackupTarget $BackupLocation -MachineName SourceServer
Start-WBFileRecovery -BackupSet $Backups -NoRestoreAcl -Option SkipIfExists -SourcePath "E:\wsuscontent" -TargetPath "E:\" -Force

  And I get the following error: "Start-WBFileRecoverry: The specified backup storage location is invalid."

any idea ?

Regards,

Jon

MCITP Enterprise Administrator / Server Administrator

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".

I have a Windows 2008r2 server that is running Veritas Backup Exec and has been running for several years.  Unless something goes wrong the job status always shows "backup successful".  Starting on or around 5-9-19 I started getting a slightly different status that shows "success with exceptions".  I opened a ticket with Veritas support and after a little work with an engineer it was determined that my backups were actually running and backing up my files.  However, I felt like I needed to dig a little deeper and figure out what has changed on the server to effect the backup.

The following is the error I get from the backup log.   See it states an issue with VSS about another snapshot running.  I have not made any changes whatsoever to the server.   I had not even ran Windows updates until after I started having this issue.

- Snapshot Technology: Initialization failure on: "F:". Snapshot technology used: Microsoft
Volume Shadow Copy Service (VSS). V-79-10000-11233 - VSS Snapshot error. A Microsoft Volume
Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot
can run at a time. Try running the job later.

I found some information saying to turn off any Shadow copies on shared volumes so I checked the settings on the server by right-clicking the drives on the server, Properties, Shadow copies.  As I thought I did NOT have any shadow copies enabled on this server.  But, one thing I did notice was a funny looking volume listed under drives like c:, d:, etc.  The funny looking volume is shown below.

\\?\Volume{d3969e0b-34db-11e0-b58c-806e6f6e6963}\

I have had problems with backups in the past and many times if you have a large external drive or something similar connected and the drive is not formatted GPT you will get some strange VSS issues that can show up with your backups like Veritas Backup Exec.

Can anyone tell me what this funny looking volume represents or what it is and how I can remove it in hopes it will clear up my "success with exceptions" error in my backup routine?

thanks

Environment: Windows 2012 R2

Hi,

Perhaps someone can explain this for me . . .

I am performing a BareMetal backup to a local volume on the server.

I have a scheduled Bi-Weekly BareMetal backup. One hour before the backup, I run a maintenance task to keepVersion:2 so that only 2 versions of the BareMetal backup are kept.

The next BareMetal backup which is run is successful. I open a PS session, runwbadmin get versions and it shows 3 BareMetal backups performed. 2 weeks later, the next maintenance scheduled task is run, it removes the oldest BareMetal backup and displays 2 BareMetal versions (wbadmin get versions). When I open Explorer, under WindowsImageBackup\<Servername>, it still shows the BareMetal backup version which was deleted. I.E. runningwbadmin get versions shows 2 versions of the BM backup, but 3 versions exist in Explorer.

As this continues, the BM's are deleted when running wbadmin get versions but the files are not being removed.

If this continues without my checking it, I will eventually run out of disk space.

Why aren't the files for the BM backup being deleted when my maintenance task (wbadmin DELETE BACKUP -keepversions:2) runs?

Help!

David

Domain Controller Backup is failing. VSS writers are waiting for completion.

Backup is done by Networker tool on Physical Servers.

Xcopy is blocked in infra and on DC too.

C:\ drive backup is failing and System State backup also fails.

All other Drives backup are completed except C:\

System:Event ID 1 

Disaster recovery backup of the critical volumes failed.

System Event ID 8220

Output of VSSADMIN LIST WRITERS

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

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: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {62be2954-ee27-42b5-9cb0-5197a49cc544}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {334e03db-923b-4641-b9b8-3ab24ccad80a}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {85357157-1c4c-495a-a210-6f8ea797d514}
   State: [1] Stable
   Last error: No error

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {d55449d9-de26-4efa-87e4-c1e2046cad6c}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {0d1b06ed-1b5e-4c1d-945e-bc7aa9d2c77f}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a0bfb87e-3526-4dca-88f6-119a60a78de5}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {1ab0cd91-540f-4c75-9890-a19a198d825d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {2bb557e6-6dd6-4ef3-b443-662db0b87af3}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {dcf2947d-8237-45f5-bfa4-8464a5dbb46d}
   State: [5] Waiting for completion
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {660dd751-00d9-483b-b5be-b4ad9784e722}
   State: [5] Waiting for completion
   Last error: No error

Output of Vssadmin list providers

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Microsoft File Share Shadow Copy provider'
   Provider type: Fileshare
   Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
   Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

We have recently installed Window 2008 and are receiving the following message:

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

Details:

AddCoreCsiFiles : BeginFileEnumeration() failed.

System Error:

Access is denied.

I have followed all of the posting that are listed and have made sure the necessary rights have been assigned to the c:\windows\registration file but hte "System Writer" will not show when running vssadmin list writers. 

Please help.

Thank you.

I know how to add a backup destination using wbadmin.  But how do we do the inverse to remove redundant targets.

If I issue the command

WBADMIN ENABLE BACKUP -removetarget

i need the disk id to be able to remove target drives registered with Windows Server Backup (WSB).

How do I get the Disk ID for drives that say have failed and been disposed of that WSB has registered with it

WBADMIN GET DISKS

only tells us the drives that are physically connected to the server at the time.

Why: I have a client site that is quite harsh on their external drives used for backup.  It has a large number of drives registered as destinations and I'd lke to cull them.  Becuase it is easy to use one of the disk editing tools to write the disk id and hence impersonate a backup drive, I'd like to remove any that are no longer alive.

I have done a search of the registry for a know DISK ID but none returned assuming they are either stored encrypted or stored elsewhere.

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?

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}

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.
*-----------------------------*

Hi, 

Since some time now i have not been able to use the Windows server backup tool anymore.

I cant really tell since when this started, but for all i know the windows server backup service worked fine.

I even created a backup schedule and it made some backups. 

I am running this windows server 2012 Standard at home with just a couple of basic applications.

The server is used to host several websites with IIS, it manages my local DHCP and is used for locally shared storage.

There are no other security applications installed yet, because i am trieing to get rid of this error first. (so no symantec or whatever)

Since some time i am having trouble opening the windows backup snap-in. 

When ever i trie to open the Windows server backup snap-in i get the following error:

A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation.

Error details: The Windows Server Backup service has stopped. 

Close Wbadmin.msc and then restart it.

Whenever this error occures the folowing error is show in the windows logbook:

I tried to find simmilar cases over the internet but i cant seem to find a solution for the problem. 

I already tried to remove and reinstall the Windows server backup feature, this did not help. 

Is there anyone here that can help me find a solution for this problem ?

Thank you !

Best Regards Maikel