I am backing up to a mounted iSCSI drive. The drive is dedicated to server backups My question is why do I need to have ANY space devoted to shadow copies on this volume? Making shadow copies of the backups means I'm making shadow copies of the shadow copies on the server drives, doesn't it? What purpose does this serve, and can I disable this behavior?

Dear sir,

you are requested 

how to backup Active directory domain services windows server 2008 & after  formatting how will restore all Active directory domain servicess

shrikant

Hi,

I have a 2 cluster node environment, Windows server 2012 Standard installed. Backup solution used is EMC Networker.

The problem that I'm facing is that when we try to backup the passive node, The backup fails due to the fact that it searches for a volume path that is active/online on the active node j:\usr\sap\kp1\ascs11\exe.

Event Id 8193, VSS -- I am receiving at every backup attempt:

Log Name:      Application
Source:        VSS
Date:          09.06.2016 21:53:28
Event ID:      8193
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:     
Description:
Volume Shadow Copy Service error: Unexpected error calling routine GetVolumePathName is fail on the path j:\usr\sap\kp1\ascs11\exe, winerror 0x00000002..  hr = 0x80070002, The system cannot find the file specified.
. 

Operation:
   PrepareForSnapshot Event

Context:
   Execution Context: Writer
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {b1a7e0b9-5790-4f11-848e-7c80c7e90d96}

Output of the VSS Writers:

vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 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: {7c84bfb1-9f29-4e64-9269-642d030e3968}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'
   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Writer Instance Id: {1f5a87ec-482d-4b64-b32d-d4ab7dbd0bef}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {2ca5cc73-ed8e-4ee0-a1a6-4f459c3cd32c}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {19839fee-6306-44d4-a2b1-c3599d76edf4}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {f96446c5-5a6a-429a-a7bb-c55d23e9e4ce}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {2283eaef-e547-4ab0-88cf-1c179f56634b}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a27147d3-69e8-4966-b8da-28e405572cc8}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {787b1258-c1bd-4b49-8033-5cb487d8a954}
   State: [1] Stable
   Last error: No error

I have found fixes for Server 2008 and 2008 R2 but have yet to find a resolution 
for Server 2012 R2.  I have worked with EMC to try a resolve with no
luck.  The issue is the e:\ volume is on the other node in the cluster but
is looking at this path due to a SAP service that installed to this
cluster volume location on this node "e:\usr\sap\trn\ascs01\exe\sapstartsrv.exe".  
Below is the VSS event id, vssadmin list writers, and diskshadow output for
further information.

________________________________________

Event Id 8193, VSS -- I am receiving at every backup attempt:

Volume Shadow Copy Service error: Unexpected error calling
routine GetVolumePathName is fail on the path e:\usr\sap\trn\ascs01\exe,
winerror 0x00000002.. hr = 0x80070002, The system cannot find the file
specified.

Operation:

PrepareForSnapshot Event

Context:

Execution Context: Writer

Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}<o:p></o:p>

Writer Name: System Writer

Writer Instance ID:
{b37cf597-c4a9-46ec-a4f1-f834daf9295c}

______________________________________________

Output for vssadmin list writers

Microsoft Windows [Version 6.3.9600]

(c) 2013 Microsoft Corporation. All rights reserved.

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: {51014fc6-79fc-4719-a47e-890c12eae4af}

   State: [1] Stable

   Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'

   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}

   Writer Instance Id: {ca77048d-6a55-429d-8156-cd20cd480286}

   State: [1] Stable

   Last error: No error

Writer name: 'SqlServerWriter'

   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}

   Writer Instance Id: {02ce344c-fee1-471e-add1-80fc0f0eab1c}

   State: [1] Stable

   Last error: No error

Writer name: 'ASR Writer'

   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}

   Writer Instance Id: {7470832b-d895-43e1-bb24-4ba2411fa7bf}

   State: [1] Stable

   Last error: No error

Writer name: 'Registry Writer'

   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}

   Writer Instance Id: {0591d297-755a-426e-83de-20dbc24d4a8a}

   State: [1] Stable

   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'

   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}

   Writer Instance Id: {a163cc77-d300-4089-a5fb-2a45c33deb14}

   State: [1] Stable

   Last error: No error

Writer name: 'Cluster Database'

   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}

   Writer Instance Id: {a717560f-50db-4771-99bc-03a68aa01f5d}

   State: [1] Stable

   Last error: No error

Writer name: 'COM+ REGDB Writer'

   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}

   Writer Instance Id: {6a4a6d8b-4b54-4904-8bf9-9433120b1aad}

   State: [1] Stable

   Last error: No error

Writer name: 'WMI Writer'

   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}

   Writer Instance Id: {2ff1dddd-8586-43f0-a824-e4025d538a3f}

   State: [1] Stable

   Last error: No error

______________________________________________

Output for diskshadow

C:\Windows\system32>diskshadow

Microsoft DiskShadow version 1.0

Copyright (C) 2013 Microsoft Corporation

On computer:  AOTRNCL01,  9/11/2015 8:08:51 AM

DISKSHADOW> add volume c:

DISKSHADOW> create

COM call
"lvssObject4->GetRootAndLogicalPrefixPaths" failed.

Alias VSS_SHADOW_1 for shadow ID {a817c807-f00b-496b-b799-06a15a6f9e0f} set as
e

nvironment variable.

Alias VSS_SHADOW_SET for shadow set ID {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}
se

t as environment variable.

Querying all shadow copies with the shadow copy set ID
{e9ce9d2b-97d0-4415-ae49-

2ec7b5b3c87d}

        * Shadow copy
ID = {a817c807-f00b-496b-b799-06a15a6f9e0f}

%VSS_SHADOW_1%

               
- Shadow copy set: {e9ce9d2b-97d0-4415-ae49-2ec7b5b3c87d}

%VSS_SHADOW_SET%

               
- Original count of shadow copies = 1

               
- Original volume name: \\?\Volume{bcb4e1e6-f8a3-11e4-80bf-806e6

f6e6963}\ [C:\]

               
- Creation time: 9/11/2015 8:09:38 AM

               
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeS

hadowCopy1

               
- Originating machine: AOTRNCL01.waterone.org

               
- Service machine: AOTRNCL01.waterone.org

               
- Not exposed

               
- Provider ID: {b5946137-7b9f-4925-af80-51abd60b20d5}

               
- Attributes:  Auto_Release Differential

Number of shadow copies listed: 1

Hi

Server 2012, a year plus of daily full backups on external drive f:

Serv2012 is name of server.

Catalog on server shows new external drive backup but not old ones (I had replaces first external with another.)

Seems I need to use wbadmin to restore a directory? I got wbadmin get versions - backuptarget:f: to show my backups.

I need command to restore a folder named folder on drive d:   (d:folder) help!!!!

Volumn is 06/30/2016-4:00

Hi everyone

We want to OS upgrade from Windows server 2008x86 enterprice to 2012 R2 x64,

and want keep some "set up" and "share folder policy".

And we used "Windows server backup in 2008, then restore in 2012".
If this method can workable, we save a lot of trouble.
or else more better method can provide us.
Thank you very much

Hello,

I'm running Windows Server 2012 R2 Essentials as a file server for a group of Windows 10 PC clients.  I'm trying to set up the Client Restore Service in the server, which requires download and install of the Windows Preinstallation Environment, WinPE, on the server. 

The setup screen for Client Restore Service includes a link to the WinPE installer, but the link seems to target the WinPE for Win 8.1. 

Since my clients are Windows 10, I downloaded and installed the WinPE for Windows 10 and restarted the server.  However, the Client Restore Service screen appears exactly as it did before, with the error message "Cannot Find Windows Preinstall Environment Image".

Do I have to uninstall the Windows 10 version of WinPE and install the Windows 8.1 version?  This seems backwards since all of my clients are Windows 10 clients.  My understanding is that the Windows 10 version of WinPE is preferred when installing Windows 10 since it includes Windows 10-compatible drivers.  Thus I may end up with incompatible drivers if I try to restore a Windows 10 machine using Windows 8.1 version of WinPE.

Is there a registry tweak in Windows Server 2012 R2 Essentials that will direct the Client Restore Service to the installed Windows 10 version of WinPE already on the server?

Thanks!

Dave

I had restored BMR on HP Proliant DL380 G6  having 3X 300GB Raid 5 server, this was done by using win 2008 setup disc & selecting repair option, the restore goes sucessful, but i am not able to boot the server because after restoring i can see system reserved partition has take c: drive which had boot loader files, while my actual C: is now D:, D: drive is E: & E: drive is F: 

I tried diskpart utility to change the drive letter & making the partition active, but when i restart the server again with win2008 setup disc , i see changes have reverted back & gives boot loader missing

Can some one help me as this is my domain controller with imp application running on it.

Thanks

Manoj

Hi

i have two server in 2012 versión, i want backup specific roles in the first server and recover it on the second server but retaining  the roles existents.

Is possible recover some the specific roles and features in the second server without override the actual roles and features ?

On Win 2012 r2 from few weeks i have a strange issue.

Every second backup end after about 1 minute with message "more data is available"

Reconfigured backup from scratch - the same error. Reformatted usb disk - no change.

I've no idea. I can't find any valuable info in logs. When i start backup manually from console - everything is ok.

Server is up to date, restarted. Nothing helps.

Maybe someone can help ?

OK, we all know that BMR is really intended for restore on identical HW.  For reasons that some of you may know, I need to migrate from a Dell server with a PERC S130 to the same HW but using a real RAID card, say a PERC H330.  Here's what I tried:

a) Did a BMR backup to an external drive

b) Removed the old drives and old RAID controller

c) Inserted brand spanking new drives and the new RAID controller

d) Restored

Restore went well, but got the proverbial blue screen of death.  I realized that there is probably a driver issue at hand, but not certain as the restore proceeded -- that is, the restore wrote onto the new disk array.

In any case, I have two ideas in my head:

a) Try putting the NEW RAID controller in the box without any drives connected to it while running on the old RAID.  Hopefully Windows will detect new HW and either load a driver or ask to have a driver loaded (which I have).  After that, do the BMR backup, remove the old RAID, swap in the new RAID and drives and hopefully, the restore image will have the right drivers.

b) Just install the driver for the new RAID while running on the old RAID (not bothering with actually installing the HW), then doing the BMR backup, and so forth.

Before blowing another few hours on this, any words of wisdom?

Ken

Hi everyone,

I am hoping that someone can help me out here.  I have a 2 node 2012 R2 Hyper-V Failover Cluster, and I am trying to get our Veeam backups to work on this Cluster.  On node 1 the backups work fine with no issues, but on node 2 the Veeam jobs constantly fail with the following error:

10/09/2015 14:39:23 :: Unable to create snapshot (Microsoft CSV Shadow Copy Provider) (mode: Veeam application-aware processing with failover). Details: Failed to check whether provider '{400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}' supports shadow copies on the volume '\\?\Volume{d8496e1b-cf0c-4cf4-8554-0afd39f67e5d}\'.The volume shadow copy provider is not registered in the system.--tr:Failed to add volumes to the snapshot set.--tr:Failed to perform pre-backup tasks. 

C:\Windows\system32>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 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

But for some reason on the working node, it lists the above providers along with the additional provider that Veeam is expecting:

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

I could really do with knowing why node 2 is missing this provider, and how I can get it installed so that I can get the backups to work.  The Cluster Nodes were both built at the same time using the same configuration, so why this is missing is a mystery to me!

Any help anyone can give me is greatly appreciated.

Many thanks.

Robert Milner | MCITP: Virtualization Administrator | Website: http://www.remilner.co.uk | Twitter: @robm82

Hi,

We have written a VSS hardware provider. Which is working fine. However we are facing a strange issue with one particular server. VSS snapshot creations is always failing with "VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER". But the VSS service is not invoking "AreLunnsSupported" function. The server has simple configuration.

- Windows 2008Rs SP1

- It has only one disk.

- When we are calling "AddToSnapshotSet" on the system reserved partition, we are facing this issue.

- It has only NTFS volumes.

Is there any way VSS can return error without consulting the provider ? We are passing our provider GUID to "AddToSnapshotSet". But still VSS service is not contacting the provider.

Appreciate any help! Thanks.

My server has dual OS Drives c:\ and 4 RAID data drives as the d:\.

I store all my data on the d:\  drives, in Folders I created: Admins, Clients, Regulatory, etc.

I'm backing up the data (the entire d:\Serverfolders) nightly to an off-site NAS.  I do not need or want Windows backup to backup the data, just the OS, settings, users, machine name, Domain, permissions, etc.  IF my OS drives fail, I assume my data on d:\ will be fine.

I'd like for Windows back to back up the entire C:\ drive AND perhaps just the folders (the names and permissions only) on the D:\ drive, so I won't have to redo their setup and permissions, if I need to rebuild the OS Drives.

Or do I just need to back up the OS on the c: Drive and manually add back the folders on the D: drive after the server rebuild?

==========

All,

I have a Server 2012 R2 forest with an empty root and two child domains. Everything is Server 2012 R2 end-to-end. I've installed Windows Server Backup on a DC in each domain. I've created separate gMSAs in each domain, added them to Domain Admins in their respective domains, and installed them on each of the three DCs to be backed up. I created a share on a server in one of the child domains and gave Domain Admins from each domain full control at the share and security ACL levels.

I'm creating scheduled tasks to run as gMSAs and they run powershell.exe with the arguments of "wbadmin.exe start systemstatebackup -backupTarget:\\server.contoso.com\backup -quiet"

Backups on each of the child domains work fine. However, the backup on the root DC is failing with "Error Value: 2147943785" when running as the gMSA. If I switch the user running to use my domain admin account, it runs without issue.

I've added the gMSA to the local domain admins, backup operators, administrators, even schema and enterprise admins, but nothing works. I've deleted and re-created the gMSA with different names and different principals allowed to recover the managed password.

I understand that the error value indicates the account doesn't have rights to run as a batch job, but all of the groups in which it's a member do have that right, and I've added the account explicitly to the run as a batch job list, but it still fails.

Any ideas? Is there a reason a gMSA from a parent domain couldn't talk to a child domain? The trusts are built transitive and there are no issues with communications between the two child domains.

This is a test domain, and I'd hate to burn hours to call support. Hope someone can help.

Ron Arestia, MCSA (Server 2012)

Dear all,

After a sudden death of the drive in my PC due to the (then) famous hard drive firmware bug I started to getting very worried on running backup regularly. I did have regular backup to the most important files from one partition to another partition, but that was all gone because all of them resided in the failed disk.

After a month of chaos, I finally realized that was a bug in the firmware and sent it to the vendor for the drive recovery. Now I got it back and bought another drive for backup purpose, the next best thing to do is the all-time important: the backup.

Knowing that the only way to create a VSS backup for all the volumes in disk 0 to disk 1 is wbadmin, so I have:

wbadmin start backup -backuptarget:e: -include:c:,d: -vssFull -quiet

When doing the end-to-end testing for the restore, the only way I could (instead of GUI):

wbadmin start recovery -version:08/31/2010-20:58 -items:d: -itemtype:Volume -backupTarget:e: -recoveryTarget:d: -quiet

C:\>wbadmin start recovery -version:08/31/2010-20:58 -items:d: -itemtype:Volume -backupTarget:e: -recoveryTarget:d: -quiet
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Warning:  The START RECOVERY command is not supported in this version of Windows.
The operation ended before completion.

C:\>

Can anyone point out that this is the best approach in terms of backup/restore in Windows 7 (x64 Ultimate) using Microsoft's VSS implementation? The start recovery command seems not supported, what gives? Or I overlooked something in the Windows backup/restore GUI tools? Thanks in advance :)

Bonjour, 

Pouvez-vous m'indiquer si Windows Serveur 2008 et R2 sont compatibles avec les lecteurs de sauvegardes HP LTO-7 ?

D'avance, merci.

Bonne journée.

I am having a problem with my Windows Server 2008R2 machine where when I try to add another external hard drive to my backup schedule it will not allow me to. I can start to add it, but when it gets to the point of formatting and naming the drive I receive an error that the name is invalid. As a work around I have been stopping and starting a new schedule every day after I swap out the drives. Any ideas on how to correct this would be greatly appreciated.

Sincerely,

Deven W.