When I had set up the backup schedule for my WinServer 2016 domain controller in Windows Server 2016 Backup, I had it dedicate a virtual drive to backups.

The file for the virtual drive is called "Domain Controller Backup.vhdx" and is sitting on a backup drive mounted to G: on the host Windows system, FREDHOST (for purposes of this discussion).

Unfortunately, the vhd file for our domain controller got corrupt, so I'm trying to restore.

When I try to boot into the server, called DC1 (for purposes of this discussion), it cannot successfully boot and takes me to the troubleshooting options (as you would expect).

The problem is when I try to use System Image Recovery (in troubleshooting options), it just will not find any backups.

I have the backup virtual drive mounted to the virtual machine (via HyperV Manager) just as I did when it was successfully doing backups. However, it won't find any backups.

When I run mountvol in a command prompt, it shows multiple volumes, but none have a subdirectory called WindowsImageBackup.

I've tried making the virtual drive available via a network share (\\FREDHOST\G) and accessing via the network location option in System Image Recovery. It seems to see it, but then asks for ID and password. No matter what I enter (including a valid ID/PW for the host machine), it says its an invalid ID/PW. (Frankly I don't think this route is the answer, since I have a dedicated virtual backup drive.)

What do I need to do to get to my backups?!

Do I need to mount the dedicated backup drive a different way? Am I going to have to create a new 2016 Server and load from the Windows Server Backup interface?

I've seen a bunch of articles on the 'net, but none seem to address dedicated backup drives.

Thanks for your help.

In a command prompt when I enter mountvol, I see several volumes, but none of them have a subdirectory called WindowsImageBackup.

↧

Fail Start

January 19, 2020, 7:02 pm

≫ Next: Backup Fails intermittently and Causes DPC Watchdog Error BSOD

≪ Previous: Cannot restore from dedicated backup drive on Server 2016

Greetings,

After installing the latest 10 updates for windows 2008 Server R2, Windows only enters recovery mode, but has no restore image.

Any quick and urgent tips?

Thanks

↧

Backup Fails intermittently and Causes DPC Watchdog Error BSOD

January 15, 2020, 3:25 pm

≫ Next: Windows server 2019 backup DPM and WSB

≪ Previous: Fail Start

We're a small non profit and have an HP Proliant ML350 Gen9 that is running Windows 2016 Server and hosting two VMs also running Win 2016 Server. For approximately 6 months Windows Server Backup was running a scheduled full backup every morning with no issues. Following a Windows update the backups started to crash the host with a DPC Watchdog BSOD. Initially I swapped out one of the two USB Drives I was using for the backup. Success for a week or so and then the same problem returned. It would crash during the backup (and the backup would fail). If I swap out drives (or apply updates) it then sometimes works again for a while but then usually starts the crashes again.

I then replaced both USB Drives which again solved the problem temporarily but then it returned. In analyzing the Dump files as best I am able there does not appear to be any one driver or file that is causing the problem. It appears to timeout at different times and crash with the dump files indicating different offending modules. This is an example of two:

Error: DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
Crashed: PROCESS_NAME: System
Caused:
MODULE_NAME: vmswitch
IMAGE_NAME: vmswitch.sys

13th Crash:
Error: DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
Crashed: PROCESS_NAME: svchost.exe
Caused:
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe

HP insists that it is not a hardware issue with the controller. I believe I have gone through and updated all relevant drivers.

Recently I adjusted the backup to only include our data files and excluded the Hyper V machines as well as system State and Bare metal. This backup completed.

Any suggestions or ideas as to what I could try next? Is there more information that would help in diagnosing the problem?

Thanks,
Byron

↧

Windows server 2019 backup DPM and WSB

March 13, 2020, 10:01 am

≫ Next: How do I properly backup AD Users, Groups and OUs?

≪ Previous: Backup Fails intermittently and Causes DPC Watchdog Error BSOD

Hi All

We have upgraded from server windows 2012 to windows server 2019 data center. New server, clean install and are using VM’s for the first time in Hyper-V and in the past we used the windows server backup (WSB) tool that is on the dashboard. Our VM’s are running DC AD with roaming profiles, file shares, DHCP, DNS, SQL etc.

I have been reading about it. There is Data Protection Manager (DPM) and WSB. We only have one server that runs all the VM’s.

Can we backup the host server using WBS and will it backup all the VM’s and file etc?

Or use DPM to backup the Host or backup the VM’s only?

What would be the best way/method to backup everything?

Thank you.

↧

How do I properly backup AD Users, Groups and OUs?

March 15, 2020, 1:43 am

≫ Next: Fail Start

≪ Previous: Windows server 2019 backup DPM and WSB

Hello, I need to back up AD Users and OU ,

At work, we have a Microsoft Small Business Server 2011 server that's doing AD for the company. There are multiple Windows client machines that are part of the domain, but that server is the only domain controller in the AD. Keeping track of users and groups is pretty much the only thing the AD was doing for us - it has no GPOs configured, no exchange server, and nothing else that we need to worry about.

The reason we are going to Format DC it has NO REPLICATION with other DCs for over 60 days

my question is how to keep users and OU safe to restore it to new AD domain controller

Thanks

↧

Fail Start

January 19, 2020, 7:02 pm

≫ Next: Backup Fails intermittently and Causes DPC Watchdog Error BSOD

≪ Previous: How do I properly backup AD Users, Groups and OUs?

Greetings,

After installing the latest 10 updates for windows 2008 Server R2, Windows only enters recovery mode, but has no restore image.

Any quick and urgent tips?

Thanks

↧

Backup Fails intermittently and Causes DPC Watchdog Error BSOD

January 15, 2020, 3:25 pm

≫ Next: Server Backup

≪ Previous: Fail Start

↧

Server Backup

March 24, 2020, 2:20 pm

≫ Next: Bare Metal Recovery

≪ Previous: Backup Fails intermittently and Causes DPC Watchdog Error BSOD

What external device is compatible with Server 2019 to use in Windows Server Backup? I have tried a Seagate Expansion Desktop Drive and Seagate External HDD and both are not recognized. When I called Seagate technical support, they said their products where not compatible with Server OS.

↧

Bare Metal Recovery

March 25, 2020, 4:26 am

≫ Next: Windows Server 2019 Windows Admin Center can not find all the drives for the Storage Replica partnership.

≪ Previous: Server Backup

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.

↧

Windows Server 2019 Windows Admin Center can not find all the drives for the Storage Replica partnership.

March 25, 2020, 7:37 pm

≫ Next: WBAdmin Incremental Backup

≪ Previous: Bare Metal Recovery

Trying to use Windows Admin Center Storage Replica to back one Windows Server 2019 Standard server data volume to another Windows Standard server data volume. Windows Admin Center Storage Replica can see the data volumes but can not see the drives I want to use for the log volume. Windows Admin Center Storage Replica can only see a volume with a Windows Server 2019 OS backup or data and not any other volume.

↧

WBAdmin Incremental Backup

March 26, 2020, 7:26 am

≫ Next: A drive is hidden for backup.

≪ Previous: Windows Server 2019 Windows Admin Center can not find all the drives for the Storage Replica partnership.

Hi Folks,

Each day I perform a backup:

WBAdmin start backup -VssFull -quiet -AllCritical -systemstate -backupTarget:\\NAS0...\d0\<date-time>

Generally, I get a full backup taking ten hours, but on occasion I get an incremental backup taking ten minutes. So, I know incremental backups are possible. I would like toforce baremetal or incremental on my schedule. I'm certain that I will always get a baremetal backup with the above instruction, if it is the first backup in "\\NAS0...\d0\<date-time>", but I would like to force any other backup to the same location to be incremental. I have tried various combinations:

-VssFull or -VssCopy
with and without -AllCritical
with and without -Include

How do I request an incremental backup?

Thanks for the help,

Chris.

↧

A drive is hidden for backup.

March 28, 2020, 4:17 am

≫ Next: VMware quiesced snapshot on Windows VM's generates NTFS events in the event logs

≪ Previous: WBAdmin Incremental Backup

Hello All

I have a problem in windows server 212, any help appreciated.

I have a d: volume hard partition and a usb external drive in which i want to take backup by windows server backup.

In backup schedule i select custom then press add, but it does not show drive D:.

It started A few weak ago i turned off my computer detached the backup drive and move computer to another place, when assemble it again, it failed to backup due to not enough disk space to create the volume shadow. I stoped the backup, deleted the backups, but still same.

Please help

best regards

↧

VMware quiesced snapshot on Windows VM's generates NTFS events in the event logs

September 18, 2017, 11:05 am

≫ Next: How can I mount vss snapshots and why we have to do that to take backup in window server backup?

≪ Previous: A drive is hidden for backup.

We have been trying to find out why a VMware quiesced snapshot generates event ID's 50, 137 and 150 on all windows 2008 R2 and 2012 R2 servers. The KB below from VMware shows this as an issue but offers no solution and said it is a Microsoft issue. Also the links for solutions from Microsoft are old and outdated.

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2006849

I need to find a fix to allow quiesced backup jobs to run on my VM's

Thank you

Chris

Chris A. DeFortuna Systems Solution, Inc

↧

How can I mount vss snapshots and why we have to do that to take backup in window server backup?

April 1, 2020, 9:50 am

≫ Next: How to backup a backup created by wbadmin on a dedicated drive

≪ Previous: VMware quiesced snapshot on Windows VM's generates NTFS events in the event logs

"Windows Server Backup cannot guarantee Volume Shadow Copy (VSS) snapshots are retained. In certain situations, after restoring to a new volume, the VSS snapshots may no longer be recognized and appear inaccessible. To guarantee protection of a VSS snapshot, mount the VSS snapshot, and run a backup job on that snapshot." It's written in the doc of window server backup. what's this pharagraph suggesting can someone please explain it to me? I tried to find online but found very little information.

My questions :

1) why we have to protect vss snapshot, does not window server backup feature takes care of it ? If no then how can I do it?

↧

How to backup a backup created by wbadmin on a dedicated drive

April 1, 2020, 10:33 am

≫ Next: Backup error 0x80780021

≪ Previous: How can I mount vss snapshots and why we have to do that to take backup in window server backup?

Hi,

I am planning to dedicate an HDD to Windows server backup for backing up the BMR of our 2019 Domain Controller systems. However, I also need a mechanism to backup this backup disconnected from network. I.e. the incremental backup file which will be generated usingwbadminand stored locally on that dedicated drive, I need to copy that over to a network share for redundancy just in case of, you probably know why... Unfortunately, what I have seen is that once I dedicate a drive towbadmin, the drive is no longer available for other backup programs and even not to wbadmintool itself to perform a backup of the backup. Please advise if there is a supported way by Microsoft Support of creating a copy of the backups stored on the drive dedicated towbadminor have another scheduled task to backupthe server to a file share in addition to the dedicated backup HDD.

Thanks for your help

Lovely day

↧

Backup error 0x80780021

April 2, 2020, 5:02 am

≫ Next: Can not schedule backup to run under group managed service account

≪ Previous: How to backup a backup created by wbadmin on a dedicated drive

Hi, this post is consequence of a issue with Veeam Backup.

Short summary: all the jobs fails with error (another shadow copy creation is already in progress), and the last step was test a backup with Windows Server Backup.

So, i tried a job (Full and VSS mode), but in bot cases, these failed with the error:"The backup operation that started at '‎2020‎-‎04‎-‎02T01:08:27.852000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '0x80780021'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

This is a Windows Server 2012 R2, Physical, with Hyper-V role installed and several Productions VMs running on. Is part of a Cluster of 12 nodes.

I tried restart the VSS services, but the error persist. The last weekend we reboot all nodes

There is no errors on writers:

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

Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
Provider type: Software
Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
Version: 1.0.0.1

Provider name: 'Microsoft CSV Shadow Copy Provider'
Provider type: Software
Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
Version: 1.0.0.1

Provider name: 'VSS Null Provider'
Provider type: Software
Provider Id: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
Version: 5.0.158.0

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

Provider name: 'VSS Null Provider'
Provider type: Fileshare
Provider Id: {f4a69dd4-f712-40e3-a6b3-faeff03cb2b8}
Version: 5.0.158.0

**************

C:\>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: {a0f6e4a6-4876-450e-ab27-0dcdb20872d7}
State: [1] Stable
Last error: No error

Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {002ec0b5-07cb-41a1-a7a6-a8d1da9178c8}
State: [1] Stable
Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'
Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
Writer Instance Id: {879cdb3d-34d7-44ab-8ef3-786195073fe7}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {de69ac02-fa58-409a-8c69-00a24a6fa0bc}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {b491f370-506e-4201-aaa7-e9d97ad0acb6}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {637adda5-d3c7-4042-9f85-be644ec582a5}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {0b7f82ca-2e03-421b-8c20-fd8b672df530}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {b423f282-8f3b-4000-a59d-bbf288eb66bf}
State: [1] Stable
Last error: No error

Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {886e0d10-ca78-456e-a8e3-ea09b1f547a5}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {f67dabce-48ba-4166-83c3-cff9cc45fab7}
State: [1] Stable
Last error: No error

Some idea?

Regards¡

Marcos Ferreira

↧

Can not schedule backup to run under group managed service account

April 12, 2013, 12:01 am

≫ Next: Primary Domain Controller is dead

≪ Previous: Backup error 0x80780021

I scheduled to run system state backup under group managed service account but am getting error "The backup operation attempted at ... has failed to start, error code '2155413599'

gmsa is member of local Administrators and Backup Operators. When I changed that scheduled task to run under local admin account, system backup succeeded.

↧