Windows Server Backup/Restore - mirrored physical to virtual

Scenario:
Server A is a Windows 2008 server with software mirrored drives running incremental backup to removable media
Server A dies but I have a working backup - seed/incrementals.
I bring in Server B and want to recover from the server A's backup media.
We have done this for non-software-mirrored situations - what would we have to do when the source is software-mirrored? Create two VHD's in the VM to be recovered to?

How does Disk2VHD deal with software mirrored drives in the original physical computer? I understand it creates a VHD but does that VHD have the mirrored drives in it? As far as I can tell it creates a single VHD file and then you attach that VHD
to a VM. However the fact is that the original was 'two drives - software mirrored' so the VM will need two VHD's won't it - one for each mirror. The process of doing this is unclear. Have you ever done this particular process?

Similar Messages

Can Windows Server Backup spread a single backup job across multiple disks if they are not set up as a virtual disk?

This may be a dumb question, but I can't seem to find any definitive information after having done many, many searches. Short question is - can Windows Server Backup spread a single backup job across multiple disks if they are not in a storage
pool or some other RAID/JBOD structure?
Background:
I'm running Server 2012 Essentials with all Windows Updates installed. I have been backing up approx 2.8TB of data (Bare Metal Recovery, C:, S: (shared folders), and system reserved) for the past year+ onto a storage pool made up of two-2TB external
USB drives. Backup is slow (takes approx 1.5 days to complete), but generally works. Not surprisingly I was constantly getting capacity low messages so I decided to increase my backup storage pool by adding a 3TB drive and another spare 750GB drive
for a total of 7.75TB. Instead of having four separate external USB enclosures, I bot a 4-bay enclosure - Startech.com model #S3540BU33E to simplify this (or so I thought!).
The first problem I had was adding the two new drives to the existing storage pool. I think that is because the Startech uses a JMicron USB controller that reports identical uniqueid's for all drives so only one shows up in the GUI interface for creating storage
pools. After doing research on this, I set up a new storage pool and virtual disk using all four drives via Powershell and thought I was good. However, when the backup ran, it failed after filling the first drive, saying there was no remaining capacity. In
reality there were three remaining empty drives and there storage pool reported almost 5TB of avail capacity. I assumed this was due to the identical uniqueid issue so I decided to try a different tactic.
Instead of using a storage pool that combines all four disks into one virtual disk, I just added each of them to Windows Server Backup as individual drives thinking it would manage them collectively. I.e., when a drive filled up during a particular backup,
it would just start using the next drive and so on. Apparently this was a foolish assumption because the backup failed again as soon as the first disk filled up.
So now I don't know if this is still an issue with the identical uniqueid's or if Server Backup actually can't spread a single backup across multiple individual drives that aren't in a pool or other virtual disk implementation. Hence, my original question.
My guess is that it does *not* spread them across individual disks, but I just wanted to get confirmation.
Thanks

Mandy,
Thank you for following up on my question.
Unfortunately the article you referenced doesn't address what I am trying to accomplish.
The article focuses on saving the same backup job to multiple disks and rotating the disks between on and offsite for enhanced protection. However, it still requires that an individual backup job fits on a single disk.
What I am trying to determine is if a single backup job can span across more than one physical disk (during the backup process) without those physical disks being in some type of virtual disk implementation (e.g., storage pool, RAID, etc.).
Thanks,
Gerry

Backed up files partially disappear after restore (Windows Server 2008 R2 - Windows Server Backup)

Dear all,
I am experiencing a problem with "Windows Server 2008 R2", using Windows Server Backup.
Here's my setup:
Server: RAID 5 Disk setup
Backup:
By using Windows Server Backup (within Windows Server 2008 R2), C: and D: were fully backed up, with "System State" and "Baremetal Recovery" options selected. Backup went okay without any errors.
Restore:
By using Windows Recovery Environment (booted from Windows Server DVD), C: and D: were fully restored to the original partitions with "System Recovery" option found within Windows RE (without re-formatting partitions during restore). Restore
went OK without any errors. Rebooted, and system has been running fine.
Problem:
After the restore, the system itself seems running OK; no BSOD, no crash, no visible errors.
However, our client insisted some files (around 6 to 7) which are related to the propriety software has "disappeared" right after System Recovery.
Question:
Since Windows Server Backup is using "Volume Shadow Copy" technology which enables "live backup" of the running system, is it possible that some files will disappear (=restore error) after
System Recovery?
I cannot really find any errors or warnings related to Windows Server Backup in the event log, through. No Windows-backup errors. No VSS errors, too.
Do anybody have experienced this kind of problem in the past? Any suggestion will be greatly appreciated.

Thank you for your reply, Ms. Mandy.
To make things clear, let me explain to you briefly:
1. The "missing data" was backed up with "full system backup".
2. After a system restore from the above backup image, as you mentioned, partitions has been overwritten with the partions' backup data in the Backup Data Set taken by Windows Server Backup. No error with backup. No error after restore, and reboot - system
has been running fine.
3. Although there was a report that the affected files(about 7 java exectables) were missing after the above restore operation, other aspect of system was running fine at the time of the report.
4. I have checked the original backup data set - and voila, there ARE files which seems to gone after restore.
5. When I used Windows Server Backup "on" Windows Server 2008 R2 normal environment (= NOT Recovery environment from DVD) and selectd ONLY these affected files to restore, these files could be RESTORED successfully, without any errors. SO... data
was property backed up.
> The recovery will overwrite the partitions so files created after the backup point will be missing.
I understand, and this is not the case this time, because the affected files are already present in the backup data set (= I have mounted the backup data as VHD, and I could clearly see them present in the mounted VHD file)
Plus, these files are completely restoreable via "selective file restore" in Windows Server Backup.
Things I want to know/confirm:
> The recovery will overwrite the partitions
If I understand this correctly, in case that the files in question are already present in the backup data set, these files SHOULD be restored after full system restore, right? (If these files could not be restored, Windows Server Backup SHOULD show some errors.)
What do you think, Ms. Mandy? :)
Jo

Server 2008 R2 Windows Server Backup. "Error in backup of Hyper-V.vhd during read: Error [0x80070001] Incorrect function.

Hello,
We are currently using Windows Server Backup to backup three Hyper-V guests running on a Windows 2008 R2 host. Two guests are running Server 2008 R2 and one is running Windows 7. I have the backups going to a dedicated external disk drive.
WSB backs up the two 2008 R2 Hyper-V guests just fine. However, when attempting to backup the Windows 7 Hyper-V guest, I receive the following error:
Error in backup of <Windows 7.vhd> during read: Error [0x80070001] Incorrect function.
I ran a "vssadmin list writers" and all the VSS writers showed "Stable" with no errors. I have plenty of space on the external drive as well. I've read this article:
https://support.microsoft.com/kb/973455?wa=wsignin1.0#workaroundissue12 except that doesn't seem to be what I'm experiencing here.
Anyone have any suggestions?

Hi,
As the other 2 guests could be backed up correctly, the issue should not be the Windows Server Backup feature.
First please refer to this article:
Backing Up and Restoring Virtual Machines
http://msdn.microsoft.com/en-us/library/dd405549(v=vs.85).aspx
Please check if all following requirements are met. Specifically please check if Integration Service is installed.
Backup (volume snapshot) Integration Service is installed and running in the child VM. The service name is "Hyper-V Volume Shadow Copy Requestor".
Windows 2000: Backup Integration Service is not supported.
The child VM must be in the running state.
The Snapshot File Location for the VM is set to be the same volume in the host operating system as the VHD files for the VM.
All volumes in the child VM are basic disks and there are no dynamic disks.
All disks in the child VM must use a file system that supports snapshots (for example, NTFS).
If you have any feedback on our support, please send to [email protected]

How are Windows Server Backup and Command Line Tools used in vCSHB installation?

How are Windows Server Backup and Command Line Tools used during the installation of vCSHB? Is it required in all types of deployments (PtoV, VtoV, PtoP)? Is it used to create the files that are put in the file share for the second node to use during vCSHB installation or is it only used during a vCSHB clone operation of a Physical to Physical deployment? Are these tools not used in some deployments?

You need Windows Server Backup installed on source and destination, and during the installation of vCSHB the installer will invoke the wbadmin (Windows Server Backup Utility) and will backup configuration and application data (application data is optimal but can decrease the sync time after installation of secondary node). On the secondary node you will need only run the vCSHB installer and everything will be restored.
Check this blog entry for some more info about some problems in P2P deployment: http://www.vcoportal.de/2013/12/vmware-vcenter-server-heartbeat-restore-on-a-second-node-a-journey/

Lost Windows Server Backup, historical backups. Backup seems to have restarted from a fresh full backup. How can I get to those old backups?

Scenario with very bad outlook:
Friday-16th, early AM. Win2008 SBS Server crashes due to RAID5 issues, bad disk. Found that server was NOT configured with hot spare and for some reason the controller had marked a 2nd disk bad..which turned out not to be the case.
Had a single external USB backup drive being fed by Windows Server Backup. Obtained support from vendor and was able to regain the RAID and start the server.
Soon became apparent that Exchange was having serious issues - edb was corrupt and not mountable. Restore edb from backup, repaired and was eventually able to mount. Then found it had Hub Transport issues. Researching that when it was noticed
NTFS events being logged at a high rate. Restarted system to repair the filesystem, which was successful.
After the FS repair, found the Exchange edb, new edb I had created to migrate mailboxes to, and public edb all 0k in size.
Restored the edb again and commenced repair, which eventually read Clean Shutdown again...but could not get it to mount. Exchange was having various issues seemingly with AD.
Changed backup time to avoid a backup that day, as did not want to back up while RAID was rebuilding - had inserted a replacement for the failed drive.
Monday/19th, was advised that much of the data was corrupt. This is an accounting firm and relies heavily on their data, especially since the last time their ext USB was rotated was Nov6 2013. They now have no year end backup, nor a backup from
post tax season 2014.
Is it possible to recover any of the historical backups prior to the full backup/restart?
Oh, and all Shadow Copies for the impacted volume/drive are gone.
Thank you.

Hi,
Please use the “Wbadmin get versions” command to check the backup versions on the server. If there is only latest shadow copy, you may not recover any of the historical backups prior to the full backup.
Backup Version and Space Management in Windows Server Backup
http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Error using Window Server Backup on 2012R2 Hyper-V to network share

Hi
I have a Windows 2012 R2 Hyper-V server. It runs a Windows 2012 R2 VM (called
server-1).
I want to backup the VM to a network location (\\network-1\server-1_backup$). To do this, I installed Windows Server Backup from the command line and configured a backup to look like this:
C:\Users\admin>wbadmin enable backup
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.
The scheduled backup settings:
Bare metal recovery : Not Included
System state backup: Not Included
Volumes in backup: (null)
Components in backup: HyperV\server-1
Files excluded: (null)
Advanced settings: VSS Backup Option (FULL)
Location to store backup: \\network-1\server-1_backup$\
Times of day to run backup: 04:00
But when I run this backup manually, I get the following error:
C:\Users\admin>wbadmin start backup
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.
Do you want to create a backup using the same configuration that you use for
scheduled backups?
[Y] Yes [N] No y
The backup operation to Scheduled backup target is starting.
Creating a shadow copy of the volumes specified for backup...
Summary of the backup operation:
The backup operation stopped before completing.
The backup operation stopped before completing.
Detailed error: A component critical volume failed to snapshot.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-23-02-2015_08-49-55.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-23-02-2015_08-49-55.log
ERROR - The shared restore point operation failed with error (0x8100010c)
No valid component or volume to snapshot.
A component critical volume failed to snapshot.
The log file then looks like this:
Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {3976D373-854E-4527-B85D-7B61924C8597}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Logical Path:
   Component Result: 8100010D
   Component Message: Component reports path on network share which cannot be snapshotted. (0x8100010D)
   Component: 30144C93-56A2-4259-B276-86D59AC767E9
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Caption     : Offline\server-1
   Logical Path:
   Error           : 8078001D
   Error Message   : The operation ended before completion.
The odd thing is that if I set this up from a Windows 2012 Server using the GUI to exactly the same network destination, the backup works no problem. It just doesn't work when using Server 2012 R2 Hyper-V configured through a command line.
Any help appreciated,
Andrew

Hi Andrew,
I tested this in my lab server 2012R2 , but there's no error .
I would suggest you to create a new share folder on other server then check if the issue persists .
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Logical Path:
   Component Result: 8100010D
   Component Message: Component reports path on network share which cannot be snapshotted. (0x8100010D)"
According to this error , please check if the VM's resource (such as VHD file) was restored on network share .
I also searched the error "ERROR - The shared restore point operation failed with error (0x8100010c)" , but I can not find it within following article :
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
Any further information please feel free to let us know .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

A fatal error with Windows Server Backup

Hey,
I'm trying to backup my Windows Server 2008 R2 (physical server). Windows Server Backup tool crashes when I start to start it. It gives me error "A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: The
Windows Server Backup service has stopped.
Errors I get to event viewer:
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 14 (Win32 error code 0x1).
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 10 (Win32 error code 0x1).
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 3 (Win32 error code 0x1).
ASR Warning: Failed to collect disk information for ASR Backup. Reason: Unable to obtain disk information for device 1 (Win32 error code 0x1).
The following process dump file was generated:
C:\Program Files\DebugDiag\Logs\Crash rule for all instances of wbengine.exe\wbengine__PID__9716__Date__07_04_2014__Time_03_08_24PM__911__First chance exception 0XE06D7363.dmp
These devices (disks) that are showing in warnings arent initialized from Disk Management. If I open Disk Management, it always pops up prompt to initialize disks. I havent initialized these disks cause I already have them in use, but Windows regonizes those
disks twice cause I'm using multipath. I shouldnt initialize one physical disk twice.
I think seeing these disks twice is crashing my Windows Server Backup. Is there a way to disable specific disks for Windows Server Backup? Can I disable those disks somehow, so Windows Server Backup wouldnt see those disks twice? Or can I somehow tell Windows
that its seeing my disks twice, and there is actually only one disk instead of two.
Greetings,
Niko Turunen
Finland

Hi,
How did you configure the disks by using multipath? The ASR component is a system-critical component that is reported by the ASR writer. Every fixed disk on the computer is exposed as a component in ASR. During backup, the requester should include all fixed
disks.
For more detailed information, please refer to the articles below:
Using VSS Automated System Recovery for Disaster Recovery
http://technet.microsoft.com/en-ca/aa384630(v=vs.80).aspx
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server Backup - 0x80042407, seriously?

I installed server 2008 on a test server with 4x250GB drives in a RAID5 array.
Windows was installed on a 60GB partition, the rest of the array was left as free space.
After installing updates and drivers, I decided that I wanted a RAID10 array.
This would give me a chance to test the restore functionality of Windows Server Backup.
I did a full backup with Windows Server Backup to a network location.
After reconfiguring the RAID array I started the recovery process.
Here is the issue. right when the restore should start, I get an error....
The Windows Complete PC Restore operation failed.
Error details: The disk that is set as active in BIOS is too small to recover the original system disk. Replace the disk with a larger one and retry the restore operation. (0x80042407)
I've tried creating partitions of all sizes and leaving the disk blank, same error.
I even set the disk as the first boot device in BIOS.
I've read elsewhere that the disk must be the same size or larger. That just seems like a bad April fools joke to me.
Can anyone give me some insight on this issue?

Hello Jason,
Thank you for your reply.
For your further concern, this same or bigger disk size requirement is by design for Windows Server 2008 and Windows Vista. As a suggestion, we recommend you use a bigger disk for Bare Metal Restore.
Currently we cannot edit the backup size. However, to fulfill your demand, there is a possible given workaround to restore the backup to smaller disk size.
Workaround: To recover the System manually using Volume recovery
By using this workaround, at minimum the OS critical partitions should be of the same size for the volume recovery.
To recovery the System manually from Windows Recovery Environment (when BMR – Complete PC Restore is not working), user has to recover all the partitions individually and then set the BCD boot entries.
Please follow the below mentioned steps:
1) Get the backup version from the backup target.
2) From version, get the size of partitions at the time of backup.
3) Recreate the partitions manually with same or more size.
4) Perform volume recovery of Individual volumes.
5) Set the Active bit for System volume.
6) Fix the Boot entries.
Please replace anything marked under <> with actual values. The yellow marked entries are for sample only. We have to pick the actual values from his system. Also assuming the Boot disk is disk 0 in this case.
Open Command prompt:
1) Do wbadmin get versions –backuptarget:<X:>.
a. Select the version id from. E.g. Version identifier: 02/11/2009-09:14
Note: If the backup target is network share, then run “start /w wpeinit” to enable networking.
2) Do wbadmin get items –version:<versioned> -backuptarget:<X:>
a. This will give the list of volumes that were backed up and their sizes.
3) Using Diskpart, recreate your volumes of the same or more size. Assume that the Boot disk is Disk 0 and is empty. Disk 0 is the boot disk and is the first disk in BIOS boot order.
If the required partitions are already present then skip the steps below.
a. Diskpart.exe
b. List disk
c. Select disk 0.
d. Create par primary size=<size>
e. Format fs=ntfs quick label=”OS” (Format the OS partition with NTFS)
f. Assign letter=D (assign drive letter D: to OS volume)
g. Do the same for all the volumes you want to recover.
h. Detail disk
i. It lists the newly created partitions.
4) To recover the volumes one by one,
a. Do wbadmin get items –version:<versionid> -backuptarget:<X:> .
b. Select the volume id or drive letter for OS volume that was backed up.
E.g. C: corresponds to the OS volume at backup time.
c. Wbadmin start recovery –version:<versionid> -backuptarget:<x:> -itemType:Volume –items:C: -recoverytarget:D:
d. Do the same for all the other volumes. Make sure that minimum space requirement is met.
e. Set the active bit of System volume from Diskpart.
f. Diskpart.exe ->
 i. Select volume D:
 ii. active
5) Reboot the OS and boot back into WinRE as OS is not yet bootable.
6) Select Startup-Repair option to fix the BCD boot entries.
7) Reboot and OS should be in a bootable state.
8) If OS is still not bootable, use bcdedit.exe/bootrec.exe in WinRE to fix the BCD boot options.
I understand that it will be reasonable to edit the backup so that the bare metal restore process can accept the smaller disk size, our product team are aware of this desired functionality and will definitely keep this in mind as future product development continues.
Thanks for your understandings.
This posting is provided "AS IS" with no warranties, and confers no rights.

Windows Server Backup fail

Hi,
I had config a Windows Server Backup, however it was fail in every backup time. in Event Log, shown the error code '2155348010' (cannot create a backup file.). I had search this error code on Google, said that the backup destination drive cannot
other than 512 sector size. And I checked the drive is 4098 physical sector size. How can I format it as 512 sector size or 512e??? I tried using command 'format x: /a:512', but it say cannot format the drive. Since, the sector size specific
is too large. Any method able to format my drive to 512e?
My drive is Seagage Expansion Desktop 3TB Model:SRD00F2
Many Thanks

Hi Kuen,
I don't understand the above event log. However, you can try the below options and see if it helps.
1) Install the below hotfix. Run the backup. If it fails, then try formatting the drive with 512 bytes cluster.
http://support.microsoft.com/kb/982018
2) Check with HDD manufacturer for the tool to format the disk to 512 bytes sector.
Thanks,
Umesh.S.K

Backing up Exchange Server 2013 CU3 with Windows Server Backup Program

Looking at configuring Windows Server Backup Program to backup Exchange Server 2013 CU3 which is a member a DAG Group using a specific Backup Domain Account.
From my understanding from the following technet Article" Using Windows Server Backup to Backup and Restore Exchange Data" at http://technet.microsoft.com/en-us/library/dd876851(v=exchg.150).aspx I cannot use wbadmin.exe has it uses an older
unsupported version of Powershell.
My question is what are the minimum AD rights required for an AD account needed to be able to backup/restore Exchange Datastore using Windows Server Backup Program in Windows Server 2012?
Thanks,
NIck

Hi Sathish,
After looking at your response, it all make sense except when I look at what exchange right assigned via RBAC. I understand that the backup service account will require access to the exchange databases
to be able to backing and restoring them. After looking at the different roles
I'm wondering if I require to assign both the Databases roles for Backing up the databases and the Disaster Recovery Role as well to be able to restore the databases has well as having a mailbox on the exchange
server for the backup service account?
Below is explanation of the roles via the ECP
Database Role
This role enables administrators to create, manage, mount and dismount mailbox and public folder databases on individual servers.
Disaster Recovery
This role enables administrators to restore mailboxes and database availability groups in an organization.
Thanks,
Nick

Windows Server backup script won't do differential/incremental

What follows is a script that doesn't seem to do backups on an incremental basis so it is creating full backups each time.
++++++++++
param(
[string]$volLetter,
[string]$scriptStorageLocation
function prepare-disk($checkDiskCriteria,$diskOrVolume){
 if($diskOrVolume -eq 'disk'){
 $disks = Get-WBDisk
 $selected = $disks|?{$_.DiskName -match $checkDiskCriteria}
 elseif($diskOrVolume -eq 'volume' ){
 $allVolumes = Get-WBVolume -AllVolumes
 $selected = $allVolumes|?{$_.MountPath -match $checkDiskCriteria}
return $selected
function add-volumeMountPoint($policyAdd,$mountPoint){
 $matchVolumes = Get-WBVolume -AllVolumes
 $correctVolume = $matchVolumes | ?{ $_.MountPoint -eq $mountPoint}
 Add-WBVolume -Policy $policyAdd -Volume $correctVolume;
 return $policyAdd
function add-VMToWB($policyAdd,$vmName){
$vmObject = Get-WBVirtualMachine |?{ $_.VMName -eq $vmName}
$vmobject='PCLaw';'2012CORPEXCHANGE';'File Server';'DC1'
Add-WBVirtualMachine $policyAdd -VirtualMachine $vmObject
return $policyAdd
function remove-policy(){
$policy = get-wbpolicy -editable
$policy|export-clixml 'backup.xml'
remove-wbpolicy $policy -force
function restore-policy($wbBackupTarget){
$policyRestore = import-clixml 'backup.xml'
$global:newPolicy = new-wbpolicy
Set-WBSchedule -Policy $newPolicy -Schedule $policyRestore.Schedule
$VolumeBackupLocation = New-WBBackupTarget -Volume $wbBackupTarget
Add-WBBackupTarget -Policy $newPolicy -Target $VolumeBackupLocation
if($([string]$policyRestore.VssBackupOptions) -match 'VssFullBackup' ){Set-WBVssBackupOptions $global:newPolicy -VssFullBackup;write-host 'foundFull'}
else{Set-WBVssBackupOptions $global:newPolicy -VssFullBackup;write-host 'FoundCopy'}
$newPolicyBound = $policyRestore.VolumesToBackup|%{add-volumeMountPoint $global:newPolicy $_.MountPoint;}
$global:newPolicy = $newPolicyBound[-1]
if($policyRestore.BMR){Add-WBBareMetalRecovery $global:newPolicy}
if($policyRestore.SystemState){Add-WBSystemState $global:newPolicy}
$newPolicyBound = $policyRestore.ComponentsToBackup | %{ add-VMToWB $global:newPolicy $_.VMName}
$global:newPolicy = $newPolicyBound[-1]
write-host -fore cyan 'Final Policy'
$global:newPolicy
Set-WBPolicy $global:newPolicy
function rename-WIB($pathWIB,$dateOfBackup){
if(test-path $pathWIB){
 $newName = "WIB_"+$dateOfBackup
 rename-item $pathWIB -newName $newName
Add-WBBackupTarget -Policy $newPolicy
Set-WBPolicy $newPolicy
if(!($scriptStorageLocation)){
$scriptStorageLocation = 'C:\Techbase\WindowsBackupRecreationScript';}
$volCheck = $volLetter+":";
$pathNew = $volLetter+":\WindowsImageBackup";
$dateOfBackup = Get-Date -UFormat "%Y_%m_%d";
$volName = $volLetter+":";
if(!(test-path "$scriptStorageLocation\WBfile.txt")){
$diskOrVolumeInput = Read-host 'Are you using a disk or a volume (type d or v)?'
$diskOrVolumeInput = $diskOrVolumeInput.ToLower();
 if(($diskOrVolumeInput -eq 'v') -or ($diskOrVolumeInput -eq 'd')){
 New-Item "$scriptStorageLocation\WBfile.txt" -type file
 Add-content "$scriptStorageLocation\WBfile.txt" $diskOrVolumeInput
 if($diskOrVolumeInput -eq 'd'){
 disk
 $diskNum= Read-host 'Please select the disk number ?'
 Add-content "$scriptStorageLocation\WBfile.txt" $diskNum
 elseif($diskOrVolumeInput -eq 'v'){
 $allVolumes = Get-WBVolume -AllVolumes;
 $allVolumes|Select *;
 $diskVol= Read-host 'Please type in the letter of the Mountpath you would like to use (Only type in the letter)?'
 $diskVol = $diskVol.ToUpper();
 Add-content "$scriptStorageLocation\WBfile.txt" $diskVol
 else{
 Write-host -fore red 'Sorry the input was not an available option.'
else{
write-host 'Your configuration file was ready when this script is executed.';
$info = gc "$scriptStorageLocation\WBfile.txt"
 if($info[0]='v'){
 write-host -fore cyan $info[1]
 $WB_Volume = prepare-disk $info[1] 'volume'
 $locationOfWIB = $info[1] +":\WindowsImageBackup";
 rename-WIB $locationOfWIB $dateOfBackup
 remove-policy
 restore-policy $WB_Volume
 elseif($info[0]='d'){
 $WB_Disk = prepare-disk 'WD My Book 1230 USB Device' 'disk'
 $WB_Disk;
+++++++++++
Also what follows is the most recent backup policy.
+++++++++++++++++++
- <Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04">
- <Obj RefId="0">
- <TN RefId="0">
<T>Microsoft.Windows.ServerBackup.Commands.WBPolicy</T>
<T>System.Object</T>
</TN>
<ToString>Microsoft.Windows.ServerBackup.Commands.WBPolicy</ToString>
- <Props>
- <Obj N="Schedule" RefId="1">
- <TN RefId="1">
<T>System.Collections.Generic.List`1[[System.DateTime, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]</T>
<T>System.Object</T>
</TN>
- <LST>
<DT>2014-10-14T19:30:00</DT>
</LST>
</Obj>
- <Obj N="BackupTargets" RefId="2">
- <TN RefId="2">
<T>System.Collections.Generic.List`1[[Microsoft.Windows.ServerBackup.Commands.WBBackupTarget, wsbcmdlet, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]</T>
<T>System.Object</T>
</TN>
- <LST>
- <Obj RefId="3">
- <TN RefId="3">
<T>Microsoft.Windows.ServerBackup.Commands.WBBackupTarget</T>
<T>System.Object</T>
</TN>
<ToString>F:</ToString>
- <Props>
<S N="Label">3TB USB</S>
<Nil N="WBDisk" />
<S N="WBVolume">3TB USB (F:)</S>
<S N="Path">\\?\Volume{7f5bcfe6-a050-44be-80c9-b056f0121819}</S>
<S N="TargetType">Volume</S>
true
true
</Props>
</Obj>
</LST>
</Obj>
- <Obj N="VolumesToBackup" RefId="4">
- <TN RefId="4">
<T>System.Collections.Generic.List`1[[Microsoft.Windows.ServerBackup.Commands.WBVolume, wsbcmdlet, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]</T>
<T>System.Object</T>
</TN>
<LST />
</Obj>
- <Obj N="FilesSpecsToBackup" RefId="5">
- <TN RefId="5">
<T>System.Collections.Generic.List`1[[Microsoft.Windows.ServerBackup.Commands.WBFileSpec, wsbcmdlet, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]</T>
<T>System.Object</T>
</TN>
<LST />
</Obj>
- <Obj N="FilesSpecsToExclude" RefId="6">
<TNRef RefId="5" />
<LST />
</Obj>
- <Obj N="ComponentsToBackup" RefId="7">
- <TN RefId="6">
<T>System.Collections.Generic.List`1[[Microsoft.Windows.ServerBackup.Commands.WBApplicationComponent, wsbcmdlet, Version=6.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]</T>
<T>System.Object</T>
</TN>
- <LST>
- <Obj RefId="8">
- <TN RefId="7">
<T>Microsoft.Windows.ServerBackup.Commands.WBVirtualMachine</T>
<T>Microsoft.Windows.ServerBackup.Commands.WBApplicationComponent</T>
<T>System.Object</T>
</TN>
<ToString>0E91F216-553D-4C7C-8178-A09E5D081020\</ToString>
- <Props>
<S N="VMName">PCLaw 2008 R2</S>
<S N="ComponentName">0E91F216-553D-4C7C-8178-A09E5D081020</S>
<S N="LogicalPath" />
<S N="Caption">Backup Using Saved State\PCLaw 2008 R2</S>
<G N="WriterId">66841cd4-6ded-4f4b-8f17-fd23f8ddc3de</G>
<G N="InstanceId">b0f4f239-bcc6-408f-9db6-b66d5de9458d</G>
</Props>
</Obj>
- <Obj RefId="9">
<TNRef RefId="7" />
<ToString>12DCBB00-87D9-4660-82E1-E01245A5E011\</ToString>
- <Props>
<S N="VMName">2012CORPEXCHANGE</S>
<S N="ComponentName">12DCBB00-87D9-4660-82E1-E01245A5E011</S>
<S N="LogicalPath" />
<S N="Caption">Backup Using Saved State\2012CORPEXCHANGE</S>
<G N="WriterId">66841cd4-6ded-4f4b-8f17-fd23f8ddc3de</G>
<G N="InstanceId">b0f4f239-bcc6-408f-9db6-b66d5de9458d</G>
</Props>
</Obj>
- <Obj RefId="10">
<TNRef RefId="7" />
<ToString>8A769D3A-4B21-419A-8BA2-584EC3168C51\</ToString>
- <Props>
<S N="VMName">File Server</S>
<S N="ComponentName">8A769D3A-4B21-419A-8BA2-584EC3168C51</S>
<S N="LogicalPath" />
<S N="Caption">Backup Using Saved State\File Server</S>
<G N="WriterId">66841cd4-6ded-4f4b-8f17-fd23f8ddc3de</G>
<G N="InstanceId">b0f4f239-bcc6-408f-9db6-b66d5de9458d</G>
</Props>
</Obj>
- <Obj RefId="11">
<TNRef RefId="7" />
<ToString>A912807A-04FE-4AB6-981B-01D6489865D6\</ToString>
- <Props>
<S N="VMName">DC1</S>
<S N="ComponentName">A912807A-04FE-4AB6-981B-01D6489865D6</S>
<S N="LogicalPath" />
<S N="Caption">Backup Using Saved State\DC1</S>
<G N="WriterId">66841cd4-6ded-4f4b-8f17-fd23f8ddc3de</G>
<G N="InstanceId">b0f4f239-bcc6-408f-9db6-b66d5de9458d</G>
</Props>
</Obj>
</LST>
</Obj>
false
false
false
- <Obj N="VssBackupOptions" RefId="12">
- <TN RefId="8">
<T>Microsoft.Windows.ServerBackup.Commands.VssBackupOptions</T>
<T>System.Enum</T>
<T>System.ValueType</T>
<T>System.Object</T>
</TN>
<ToString>VssFullBackup</ToString>
<I32>0</I32>
</Obj>
</Props>
</Obj>
</Objs>
++++++++
+++++++++++++++++++++++++
Script does everything perfect except for the backup not being incremental/differential - it just creates a different folder each iteration that it puts the backup into.
I would appreciate if someone could go through and let me know what we might be doing wrong - why we are not able to get this job to be incremental/differential.
Thanks in advance.

Hre are all of the options for Windows Backup:
http://technet.microsoft.com/en-us/library/ee706670.aspx
If you can find an incremental backup naywhere in the options then I will admit I have missed something.
The old Windows Backup, pre-2008, could do incremental backups. The newer backup system is minimal and serves different purposes.
The question about how to use a subsystem of Windows is NOT a scripting question. It is a "how-to" for a Windows component.
If you do not understand the scrip tyou posted then I recommend finding someone with sufficient understanding of Windows and the new backup Cmdlets to help you top understand how they work.
Here is the Microsoft description of Windows Server Backup:
Windows Server Backup consists of a Microsoft Management Console (MMC) snap-in, command-line tools, and Windows PowerShell cmdlets that provide a complete solution for your day-to-day backup and recovery needs. You can use Windows Server Backup to back
up a full server (all volumes), selected volumes, the system state, or specific files or folders—and to create a backup that you can use for bare metal recovery. You can recover volumes, folders, files, certain applications, and the system state. And, in case
of disasters like hard disk failures, you can perform a bare metal recovery. (To do this, you will need a backup of the full server or just the volumes that contain operating system files, and the Windows Recovery Environment—this will restore your complete
system onto your old system or a new hard disk.)
You can use Windows Server Backup to create and manage backups for the local computer or a remote computer. And, you can schedule backups to run automatically.
Windows Server Backup is intended for use by everyone who needs a basic backup solution—from small business to large enterprises—but is even suited for smaller organizations or individuals who are not IT professionals.
It specifically states that only a full server or selected file,device backup is possible. There is no statement of incremental backup. Windows Server backup is intended for server recovery.
If you type "help Set-WBVssBackupOptions
-full" you will see that there are only two options "full" and "copy".
Please post your issues in the WS2008 or the WS2012 forum to get more information on how the Windows Server backup service works.
¯\_(ツ)_/¯

Windows server backup

Hello,
I am looking to take exchange DB(600gb appr) backup on windows server back up on to a drive with 1tb size, pls let me know the procedure , is only bacup enough or should i also restore it and what is the procedure for that?
Sumanth.S Exchange Admin

Hi,
The logs of backup are at Windows Logs\Application where the source is Backup. You can use the Optimize Backup Performance dialog box to configure incremental backup.
Optimizing Backup and Server Performance
http://technet.microsoft.com/en-us/library/dd759145.aspx
Windows Server Backup Step-by-Step Guide for Windows Server 2008
http://technet.microsoft.com/en-us/library/cc770266(v=ws.10).aspx
The backup frequency depend on data changed frequency. If data changes frequently, you need to backup your data more often.
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Mount vhdx file from Windows Server Backup 2012

We have a 2012 server with a network share that other servers backup to using Windows Server Backup. To view the files from a windows 2008 r2 backup .vhd file all I have to do is open it in windows explorer and it mounts as a drive and opens. When
I try to do the same with a 2012 backup (.vhdx) it tells me "you don't have permission to mount the file" but if I open disk management I can see the volume, and if I right click on it and select "Change Drive Letter and Paths" and add
a drive letter, then I can browse it. I get the same issue using mount-vhd in powershell.

Hi Adm1nMikeW,
Please try to use disk management --> action --> attach VHD (this way will avoid the error message).
The root cause is the attribute "nodefaultdriveletter" of the backup vhd was not set to "no".
You can try following setps :
1. in cmd prompt type diskpart
2. recognize the problematic volume you want to set via list volume
3. run command select volume "volume number"
4. run command attributes volume clear nodefaultdriveletter
then detach it and reattach the disk again .
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

[Windows Server 2008 R2] [Windows Server Backup] How to remove an old backup set

Hello,
long time ago I made a backup of some files of a server on a network location running manually a command like this one:
"wbadmin start backup -backupTarget:\\Server1\Backup\MyServer\wbadmin_Effe -include:F: -user:DOMAIN\myself -password:******** -quiet"
Now this network location is no more available because that machine is definitely broken.
I have no problems to run and create backups on a local drive or on other network locations.
My only problem is that now, in the main window of Windows Server Backup, when i click "View details" under "All Backups", I can still see that backup as the oldest available... that's a bit annoying.
It appears also if I run the command "wbadmin GET VERSIONS".
Does anybody know how can I remove this backup version set from my server?
Thanks,
Alex.

Hi Alex,
The command will remove all backups existed on your server. If you cannot get Shadow Copy ID and there are "good" backups existed on you server, you could not remove the old backup versions.
How to completely delete the backup file from network share and clean up the backup version for the server?
http://social.technet.microsoft.com/Forums/windowsserver/en-US/2ecc1c25-9308-4c50-be37-9762913cab61/how-to-completely-delete-the-backup-file-from-network-share-and-clean-up-the-backup-version-for-the?forum=windowsbackup
Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server Backup/Restore - mirrored physical to virtual

Similar Messages

Maybe you are looking for