Have a client running a 2016 server hosting multiple VM's. They use Windows Server backup - once the backup is done running the VM's all show Merge in Progress. One of the VM's is an Exchange 2016 server -it becomes unresponsive and mail stops flowing until the merge is finished (over 2 hours). Sometimes several Exchange services stop during the merge as well and have to be manually started after. Has anyone else seen this issue? Thinking about changing the backup to only the host physical drives to just pick up the VHD's -  would that eliminate the merge issue?

Jack

Jack - IT Portfolio

I see there is a lot of shadow copy when I run vssadmin list shadows. It seems that a shadow copies created very hour. This creates problem for me because it is a exchange server and shadow copy on database drive will freeze the db temporally. It also almost used up all free space on the drive. I check everywhere I know trying to disable this behavior but I can't find it. There server is win2012R2. Can anyone help to point out where to disable the shadowcopy running? Also I have Backupexec agents installed on the server. But there is no backup job setup. I consulted with Veritas and they said it's not their software causing it. I disabled the Backupexec agents and the shadow copy still creates. So it's not Backupexec causing the issue.

Thanks 

Alan

Alan

While creating snapshot on Microsoft Windows Server 2012 R2 Standard Edition (build 9600), 64-bit
found below errors
errors captures in logman are below:

Error 1:

-----------------------------------------------------------------------------------------

[ 1:11:27.532 P:13D0 T:2FE4 CORSOFTC(0123)    COORD] ENTER[CVssSoftwareProviderWrapper::QueryInternalInterface] 
[ 1:11:27.532 P:13D0 T:2FE4 CORSOFTC(0128)    COORD] Error while obtaining an interface interface 0x80004002
[ 1:11:27.532 P:13D0 T:2FE4 CORSOFTC(0123)    COORD] EXIT[CVssSoftwareProviderWrapper::QueryInternalInterface] Time spent: 00:00:00-0000; total: 0; HRESULT: 0x80004002

-----------------------------------------------------------------------------------------

Error 2:

-----------------------------------------------------------------------------------------

[ 1:11:27.594 P:13D0 T:2FE4 CORFILESHAREC(0124)    COORD] ENTER[CVssFileShareProviderWrapper::QueryInternalInterface] 
[ 1:11:27.594 P:13D0 T:2FE4 CORFILESHAREC(0129)    COORD] Error while obtaining an interface interface 0x80004002
[ 1:11:27.594 P:13D0 T:2FE4 CORFILESHAREC(0124)    COORD] EXIT[CVssFileShareProviderWrapper::QueryInternalInterface] Time spent: 00:00:00-0000; total: 0; HRESULT: 0x80004002

-----------------------------------------------------------------------------------------

Errors captured by vsstrace

Error 1:

-----------------------------------------------------------------------------------------

[23:34:05.907 P:1D58 T:2D94  TRCTRCC(0592)      GEN] Tracing started or updated. PID=7512, CommandLine=[Vssadmin  list writers" > "C:\PROGRA~2\SAAZOD\zCMon\Test_EXCMD.txt], UserName=[Name: NT AUTHORITY\SYSTEM, SID:S-1-5-18]. SQN=[-1 -> 1]
[23:34:05.911 P:1D58 T:2D94 ADMVADMC(0529)    ADMIN] THROW[CVssAdminCLI::ParseCmdLine] Invalid command[23:34:05.927 P:1D58 T:2D94 ADMVADMC(0808)    ADMIN] HRESULT exception caught: hr: 0x1002
[23:34:05.927 P:1D58 T:2D94 ADMUTILC(0940)    ADMIN] Input HR: 0x00001002

-----------------------------------------------------------------------------------------

Error 2: later it fails while taking backup then to cleanup while deleting the snapshot again throw the error

-----------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------

While creating snapshot on Microsoft Windows Server 2012 R2 Standard Edition (build 9600), 64-bit
found below errors
errors captures in logman are below:

Error 1:

-----------------------------------------------------------------------------------------

[ 1:11:27.532 P:13D0 T:2FE4 CORSOFTC(0123)    COORD] ENTER[CVssSoftwareProviderWrapper::QueryInternalInterface] 
[ 1:11:27.532 P:13D0 T:2FE4 CORSOFTC(0128)    COORD] Error while obtaining an interface interface 0x80004002
[ 1:11:27.532 P:13D0 T:2FE4 CORSOFTC(0123)    COORD] EXIT[CVssSoftwareProviderWrapper::QueryInternalInterface] Time spent: 00:00:00-0000; total: 0; HRESULT: 0x80004002

-----------------------------------------------------------------------------------------

Error 2:

-----------------------------------------------------------------------------------------

[ 1:11:27.594 P:13D0 T:2FE4 CORFILESHAREC(0124)    COORD] ENTER[CVssFileShareProviderWrapper::QueryInternalInterface] 
[ 1:11:27.594 P:13D0 T:2FE4 CORFILESHAREC(0129)    COORD] Error while obtaining an interface interface 0x80004002
[ 1:11:27.594 P:13D0 T:2FE4 CORFILESHAREC(0124)    COORD] EXIT[CVssFileShareProviderWrapper::QueryInternalInterface] Time spent: 00:00:00-0000; total: 0; HRESULT: 0x80004002

-----------------------------------------------------------------------------------------

Errors captured by vsstrace

Error 1:

-----------------------------------------------------------------------------------------

[23:34:05.907 P:1D58 T:2D94  TRCTRCC(0592)      GEN] Tracing started or updated. PID=7512, CommandLine=[Vssadmin  list writers" > "C:\PROGRA~2\SAAZOD\zCMon\Test_EXCMD.txt], UserName=[Name: NT AUTHORITY\SYSTEM, SID:S-1-5-18]. SQN=[-1 -> 1]
[23:34:05.911 P:1D58 T:2D94 ADMVADMC(0529)    ADMIN] THROW[CVssAdminCLI::ParseCmdLine] Invalid command[23:34:05.927 P:1D58 T:2D94 ADMVADMC(0808)    ADMIN] HRESULT exception caught: hr: 0x1002
[23:34:05.927 P:1D58 T:2D94 ADMUTILC(0940)    ADMIN] Input HR: 0x00001002

-----------------------------------------------------------------------------------------

Error 2: later it fails while taking backup then to cleanup while deleting the snapshot again throw the error

-----------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------

Hi - am running Windows Server 2012 R2.  Have been consistently running the Windows Server Backup (Bare Metal Recovery) on a nightly schedule, however recently it's stopped completing with this error.  When I monitor the progress, I notice that it occurs right after "Creating shadow copy of volumes" completes successfully and it progresses to the System Reserved backup.  It then changes to the "Removing deleted items" stage per usual, but it's at this point that it fails.  I do not wish to reinstall this Windows Server from a clean install to lose this configuration and will move to an alternate product than Windows Server Backup if necessary.  Preference would be to restore this functionality.

I've confirmed all vssadmin list writers show no errors.  I've even done a wbadmin delete catalog and completely cleared all backups and recreated the backup schedule.  Have run a chdsk /f on all drives and no errors are reported, including temporarily assigning a drive letter to the System Reserved partition of C:.

No new software has been installed on this server.  No viruses or malware.  The machine is completely current on all windows update. Even removed antivirus and re-ran the WSB and it consistently returns this same error.

Event Viewer > Application Error (1000) is reporting the following:

Faulting application name: wbengine.exe, version: 6.3.9600.19692, time stamp: 0x5e88af65
Faulting module name: ntdll.dll, version: 6.3.9600.19697, time stamp: 0x5e91f8a1
Exception code: 0xc0000374
Fault offset: 0x00000000000f1ce0
Faulting process id: 0x6154
Faulting application start time: 0x01d62b9f3b2224a6
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 2049e8c7-9793-11ea-82e3-902b343742d3
Faulting package full name: 
Faulting package-relative application ID:

At that same time the System Event (7031) is reported as follows: The Block Level Backup Engine Service service terminated unexpectedly.  It has done this 2 time(s).  The following corrective action will be taken in 300000 milliseconds: Restart the service.

The Backup > Operational log reports Event ID 100: The scheduled backup was canceled. To create a new backup, you must reconfigure scheduled backups or run a one-time backup operation.

There should not be any old items for this WSB to remove since I've already complete deleted all existing shadow copies with DISKSHADOW and deleted the wbadmin catalog to start clean.

It's almost acting as if something in the System Reserved partition on C: might have somehow become corrupted.

The Windows Server Backup logs folder includes a wbengine0.etl file that I cannot view, however there are no new *.log files created after this error occurs to give me help in resolving this issue.

I might actually considering paying for a Windows support ticket if it will restore this functionality.

Thank you in advance.

Here is a list of my VSS Writers

C:\Windows\system32>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: {b139d3f7-6419-42ef-8637-96eab28d5a68}
   State: [9] Failed
   Last error: Timed out

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {2a07eceb-cef4-4f5b-81b0-9a983a2f66b2}
   State: [9] Failed
   Last error: Timed out

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {003070dd-bfc1-4ce6-b9d9-46c062caa420}
   State: [9] Failed
   Last error: Timed out

Writer name: 'MSSearch Service Writer'
   Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
   Writer Instance Id: {5b5b00bb-3189-4e36-902a-935c79dc6317}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {e6cd7f66-c024-4dc0-a920-ac598b7b7b2e}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {93e7300d-5177-4365-ae3a-00bc8acd5384}
   State: [9] Failed
   Last error: Timed out

Writer name: 'FRS Writer'
   Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
   Writer Instance Id: {51e305d2-6fc8-4a7f-9219-37de8f8614e7}
   State: [9] Failed
   Last error: Timed out

Writer name: 'NPS VSS Writer'
   Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
   Writer Instance Id: {5558bebc-abfe-449a-86ab-0f60caeb33ce}
   State: [9] Failed
   Last error: Timed out

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {d95f9097-d295-4ede-811f-ed9854d9a109}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {627d2264-d514-48be-817c-dfe8a0d0642d}
   State: [9] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {ba71a4e5-8058-41df-ad70-f93f20206726}
   State: [9] Failed
   Last error: Timed out

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {c6bc6449-7f94-41b1-809a-57ede0989d4b}
   State: [9] Failed
   Last error: Timed out

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {a1c7882e-ce1b-49f5-898f-0f1b956f7f75}
   State: [10] Failed
   Last error: Timed out

Writer name: 'Dedup Writer'
   Writer Id: {41db4dbf-6046-470e-8ad5-d5081dfb1b70}
   Writer Instance Id: {100459e2-bb88-4a80-8985-67c2819a8cbb}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {0a21deba-1361-448d-a0ec-5a8e42ffcd78}
   State: [9] Failed
   Last error: Timed out

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {1fed8a2d-e72b-4f7e-8cca-75131ad86591}
   State: [9] Failed
   Last error: Timed out

Hi guys,

I have implemented a bare metal backup for my Hyper-v guest VM (Win Server 2012 R2) using Azure Backup Server (MABS), which is almost identical to DPM. I was able to recover the backup as well in the form of 2 vhdx drives (one for the "system reserved" data and the second for the remaining data. Now, I am really struggling to boot up the recovered data. I simply don't know how to do so. What are the steps that need to be taken next? I am new to the whole backup thing, so please take it easy on me.

I have a production server (10TB - 1.69TB used) which I have been using MS Server Backup backing up to vhdx files on a NAS as I like to keep 2-3 weeks worth of backups. However due to some network and capacity issues at the NAS end I've had to make several other vhdx files in other places and switch the schedule to those. Today was a day when I wanted to start fresh and to create a new empty vhdx container in a different location and once working correctly clear up the old vhdx files, but when I set a new backup going the amount of data it was backing up was a lot less than the used space on the drive indicating to me it was doing an incremental. So I've:

1) Created a new empty 12TB dynamically expanding vhdx file

2) Deleted the existing schedule and created a new one, set the backup going

What would happen if I remove the old vhdx files? Presumably it would mean I don't have a full back of this server..

Is there anyway to clear MS Backup's references to old backups and start fresh?

Dear Team,

                My Active directory time is mismatch our current time. i tried to some of the google solution but still now its not resolved can you help sort out this issue

Active directory : Windows server 2012 R2 

Below picture for server time(its wrong time)



This is correct time ..its my pc

Ad command query status

We setup Windows Server Backup. We chose to do full backups, system state and some selected virtual machines. The backup works properly and no errors are generated. But whne we look into the details of the backup we can see, that there happened no transfer of data of the virtual machines. Why is this? Is this because we already do a full backup and therefore the virtual machines are not backed up separately?

When we try to restore only VMs instead of the whole server, it never works... What are the requirements, that one can restore a VM on a new server? Is this even possible or is the VM recovery only intended to be done on the server where it was originally stored on?

Thanks for the help in advance

Joël

Situation:

Our production MS Windows 2016 DataCenter with HyperV as the primary application serving 12 VMs, mostly Windows 2012/r2 and/or 10 Ent.
ArcServe UDP v7u2 used to perform backups.
ArcServe UDP Agent installed on HyperV server, and agentless backups performed of the VMs.
The backup initiates generation of an AVHDX disk (normal) which is used to capture the deltas since the last backup.  The failure is, that the AVHDX should auto-merge with its VHDX parent, however, it fails to do so.
Now, we have a long chain of AVHDX differencing disks for several VHDX on several machines.  The backups are successfully generated and files are recoverable.
A query of "vssadmin list writers" shows no errors.
An investigation of Hyper-V-VMMS Event logs shows internal error 0x8007054F and 0x8000FFFF related to AVHDX merge and/or removal of snapshot. 

I have a PoSH script that successfully discovers the VM disks currently in use, and merges the AVHDX back into the VHDX.  However, this requires the entire chain be copied, and then merged via PoSH script which all takes lots of time.  And, then requires that I build a new VM instance to mount these VHDX disks.

How do I prevent the AVHDX merge failure in the first place?  Is there a known KB or other patch to address this?

Thanks!

Hi,

 I'm after some advice on writing an AD restore plan. We have a single domain forest with 4 2012 DCs at a 2003 domain and functional level. We use Veritase NetBackup which can restore the DC OS with the system state data.

https://www.veritas.com/content/support/en_US/doc/18716246-136359033-0/v41613219-136359033

My plan for a non authoritative restore is to use the above, but if an authoritative restore is needed, then to additionally use ntdsutil:

1. 1.        Ntdsutil
   2.       Activate instance ntds
   3.       Authoritative restore
   4.       Restore database
   5.       Once finished “quit”

We have 6000 users in a single AD site. Would the above be a feasible restore method?

Thanks

Hi Folks,

Got below error and need your help:

Hi Folks , 

Getting below error on server with OS :Win2k12 r2 
Log Name:      Application
Source:        VSS
Date:          6/7/2020 7:36:47 AM
Event ID:      12347
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      not mentioned 
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  The Registry Writer failed to respond to a query from VSS. Check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events. 

Issue : Backup is getting failed , system writers are missing .Upon restarting cryptsvc all the writers are stable.but still not able to take system state backup.Also tried taking local system state backup which went through successfully.
When i checked Eventvwer found below VSS related events : 
Also could see below event IDs:

Hi Folks,

We are not able to trigger the backup , as the system state srivers are missing, Upon checking VSSadmin list writers.

We have restarted the CryptSVC and VSS , WMI services but still backup is not completing.

mentioned server OS :WIN2K8 R2

Please advise. Here Im attaching the VSS Logs for reference .

Log Name:      Application
Source:        VSS
Date:          5/9/2020 1:50:25 AM
Event ID:      12291
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      
Description:
Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
].

===========================================

Running Windows Backup on a Windows Server 2012 to a Network share

I think the backup is completing & is listed in ALL Backups but I see the message

"Event Log is inaccessible. Only messages for currently running operations will be displayed."

Any ideas how to fix the issue?