hi,

I have a Windows Server 2008 R2 and I use the Windows Server Backup Tool for my backups. The backups are stored on a QNAS NAS iSCSI LUN. The backups were performed daily and so I have a huge number of versions on that drive (i.e. as far as I know, the versions are stored in the volume shadow copies). I'd like to mount this drive on another Win 2k8 R2 server and still be able to access all the previous versions.

My questions are:

- in general, is this possible?

- what steps do I have to perform the also "mount" the shadow copies when mounting the iSCSI target.

best regards,

thomas

InitializeForRestore
GatherWriterMetadata
SetSelectedForRestore
PreRestore
SetFileRestoreStatus
PostRestore
Release

.dev

I'm using Windows Server Backup (incremental) to backup the most important data daily. 

Lately I added another dedicated harddisk for a daily disk-rolling. 

With only 1 disk, I remember that the incremental backup hold an infinite amount of "copies", allowing to go back in time for files. Now, with the second disk added, the biggest copy-count I saw per disk is somewhere around 2. 

Both the disks have around 2 TB Free Disk Space, while the data beeing backed up is at about 350GB now. 

So, what is happening here? 

The Message Log shows that within the last 2 days, disk "01" has been used 2 times for backup - however it just reports one copy of backups available

Is it possible that "prior" copies are getting purged, when you roll the disk?

We have Windows 2012 Server hosting 2 VMs - Domain Controller & RDS.  We have been doing Windows Server Backup incremental and have an ongoing issue with scheduled backups each night.  The backup shows completed with warnings and generates 2 log files.

The first log files shows:  

Backup of volume \\?\Volume{5d46f853-5db2-11e2-93e7-806e6f6e6963}\ succeeded.

Backup of volume C: succeeded.

Backup of volume F: succeeded.

Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: ACBCD71E-A8CA-4672-B951-52C1BE8444BE
   Caption     : Backup Using Child Partition Snapshot\FMLRDS1
   Logical Path: 


Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: Host Component
   Caption     : Host Component
   Logical Path: 

The 2nd log file more often than not shows:  

Backup of volume E: has failed. Backup failed as shadow copy on source volume got deleted. This might caused by high write activity on the volume. Please retry the backup. If the issue persists consider increasing shadow copy storage using 'VSSADMIN Resize ShadowStorage' command.

Error in backup of E:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 2B4A9541-C88B-442E-9A7A-6D8A27342C11
   Caption     : Backup Using Child Partition Snapshot\FMLDC1
   Logical Path: 
   Error           : 8078010D
   Error Message   : Enumeration of the files failed.

   Detailed Error  : 80070003
   Detailed Error Message : (null)

We had been getting a successful backup once or twice a week which showed completed (with no mentioned of warnings) but now it regularly shows completed with warnings as noted above.  

We did a manual full backup of the DC to a different external drive a few days ago and that completed without warnings and the backup shows:  E: Completed 63.38 Full - VSS Copy Backup Successful, 8/27/13 3:35 PM - 4:43 PM. Data Transferred 63.38

On a side note, we can view the logs in the windows/logs/windowsserverbackup directory but when we attempt to view the details of a log file through the Local Backup Console for any log which shows completed with errors, we get a "MMC has detected an error in the snapin and will unload and then it shows Object referenced not set to instance of an object."  The manual backup noted above that was successful is able to be viewed through the Local Backup Console without this error.  

Any idea as to why this is failing during the scheduled backups?  This hosts a database that we need to have regular successful backups.

I installed a dedicated disk in a Windows Server 2012 R2 server and configured Windows Server Backup to use it.  This works great until the disk fills up.  When it does, an error is logged "The shadow copies of volume \\?\Volume<GUID> were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."

I've read that when the disk fills up, WSB is supposed to delete the oldest backup and continue, but it is deleting everything and starting over. 

I've seen other posts indicating that this behavior was observed in Windows Server 2008 R2, but is broken in 2012+.  Is there some way to get automatic retention working in 2012 R2?

I am experiencing a problem with Windows Server Backup where previous backup versions (copies) are lost if the connection to the iSCSI target, where the backups are stored, is dropped and remains disconnected for a short time.  

I have configured the Windows Server 2008 server to connect to a QNAP iSCSI NAS device using the built in iSCSI Initiator.  I have also configured Windows Server Backup to use the iSCSI volume as the backup target disk.  Periodically, for reasons not yet understood, the server loses connectivity with the iSCSI device.  When this happens I often find that the backup copies that had existed on the target volume are no longer there and the backups have to start again.

Today I discovered that the volume ID of the target disk seems to change, without manual intervention, when the iSCSI initiator reconnects to the target and Windows Server Backup is refreshed.  This is demonstrated by the output of the WBADMIN GET VERSIONS command, e.g.:

Backup time: 18/05/2011 23:30 

Backup target: Fixed Disk labeled ATEGO-M 2010_03_17 08:29 DISK_01(\\?\Volume{a79ff0ae-2cbb-11df-8798-005056bb11b1})

Version identifier: 05/18/2011-23:30

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 19/05/2011 23:30 

Backup target: Fixed Disk labeled ATEGO-M 2010_03_17 08:29 DISK_01(\\?\Volume{a79ff0ae-2cbb-11df-8798-005056bb11b1})

Version identifier: 05/19/2011-23:30

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 20/05/2011 23:30 

Backup target: Fixed Disk labeled ATEGO-M 2010_03_17 08:29 DISK_01(\\?\Volume{a79ff0ae-2cbb-11df-8798-005056bb11b1})

Version identifier: 05/20/2011-23:30

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 14/11/2011 10:53 

Backup target: Fixed Disk labeled ATEGO-M 2011_05_22 13:08 DISK_01(\\?\Volume{32077493-83cc-11e0-931b-005056bb11b1})

Version identifier: 11/14/2011-10:53

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 23/12/2011 20:34 

Backup target: Fixed Disk labeled ATEGO-M 2011_11_14 17:43 DISK_01(\\?\Volume{c253b27d-0dd8-11e1-bab4-005056bb11b1})

Version identifier: 12/23/2011-20:34

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

Backup time: 30/01/2012 09:20 

Backup target: Fixed Disk labeled ATEGO-M 2011_12_24 10:41 DISK_01(\\?\Volume{62330671-2d51-11e1-b23e-005056bb11b1})

Version identifier: 01/30/2012-09:20

Can Recover: Volume(s), File(s), Application(s), Bare Metal Recovery, System State

You can see that the label (ATEGO-M 2011_12_24 10:41 DISK_01) remains constant throughout, but the volume GUID changes.  I suspect that this causes Windows Server Backup to lose its backup history as it no longer recognises the volume as being the same - although it quite clearly is.

The question is:  Is this behaviour to be expected?  

Should the volume GUID change each time the volume is disconnected and reconnected?

I suspect that it shouldn't.  So, is there a way to fix the GUID so that it remains constant even if the volume becomes disconnected for a short while?

Thanks

Hello,

Alert: The backup operation for the cluster configuration data has been canceled due to an abort request

Alert description: The backup operation for the cluster configuration data has been canceled. The cluster Volume Shadow Copy Service (VSS) writer received an abort request.

This is the backup of VSS which is sending this alert every morning.

Event ID 1544

All fixes I found are applied..

any other id

Cluster Node /Status gives both nodes up A & B

The error is coming only on Node A...

Any idea?

Thanks,

Dom

System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

We just stated noticing that we are getting these 2 errors in the
Application log on one of our 2008 R2 servers. We have found suggestions
that apply to Server 2003 but we have not found anything for Server
2008 R2. We have tried rebooting the server and
still have the same issue. When we run "vssadmin list writers" it hangs
and does not complete. When we try to create a new shadow copy we get a
message saying "Another Shadow copy creation is in progress. Wait a few
minutes and try again." If we wait a few
minutes and try again we get the same message. We found a suggestion
saying to re-register some DLL files but we would not like to do that.
We have also looked at this ->
http://support.microsoft.com/kb/956136.  but that does not apply to R2.
All updates
are installed on the server. Also, the hard drive has around 280 GB of
free space.

Has anyone seen this issue on Server 2008 R2? Does anyone have a fix for it?

Log Name:      Application
Source:        VSS
Date:          4/3/2012 9:08:27 AM
Event ID:      12305
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server

Description:

Volume Shadow Copy Service error: Volume/disk not connected or not
found. Error context:
CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy26,0x00000000,0x00000003,...).

Log Name:      Application
Source:        VSS
Date:          4/3/2012 9:07:32 AM
Event ID:      7001
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Server

Description:

VssAdmin: Unable to create a shadow copy: Another shadow-copy creation
is in progress, so the current shadow copy cannot be created.  There are
a number of common scenarios causing this problem:          * If
Shadow Copies of Shared Folders is set up, ensure that no two volumes
have schedules that lie within five minutes             of each
other.          
* If automatic backup of any form is scheduled, ensure that the backup
schedule does not overlap with the schedule            used for Shadow
Copies of Shared Folders.    Generally, retrying
the operation after a few minutes or changing the schedule of an
automatic task should fix this problem.


Command-line: 'vssadmin   create shadow /For=E:'.

Hi guys,

I seem to be having an issue with our Windows Server Backup running on Windows Server 2012 R2. The backup appears to be completing with warnings and some VM's are being skipped. There are 3VM's in total being backed up but 2 are being skipped during the snapshot phase.

The errors in wbadmin are:

• The component [VM Name] was skipped during the snapshot and will not be available for recovery. Error: The writer experienced a non-transient error. If the backup is retried, the error is likely to reoccur.

I get the same warning for both VM's. 

In event viewer I get the following warning:

XML version:

Has anybody seen this before. Could any-one offer any insight as to what may be causing the issue?

Regards

J

I'm using the built-in "Backup and Restore" utility to back up my Library to an external drive. At some point the external drive becomes full and the backing up process silently fails. So I'm assuming that I need to free up some space.

My question is how do I delete more than one backup at a time, because I have like 100+ of them in the list?

Dear Windows Expert,

I have a task from my boss to perform a backup of the whole windows server due to some cease of the branch. I don't have any access to the server remotely, hence will need to go to remote to perform manual backup. it is a windows server that have Navision database inside. there is no other backup software that being installed into the server too as there is no license being purchased.

My intention is to use windows backup for the backup since it is come free with windows server. My question is which option to choose to allow the backup to be performed fully, so it can be restored on another server at HQ? is this utility enough for this task?

If you guys have any other recommendation about the powerful free backup software, kindly let me know.

Appreciate your help.

Thanks.

Regards,

I have arcserver backup software and it is failing on the system state so I ran a windows backup just for system state and it failed also with only 2 informational events as follows:

=============================event 1=====================================

Event ID 1001 / Source Windows Error Reporting / Log Name: Application

Fault bucket , type 0
Event Name: Windows Server Backup Error
Response: Not available
Cab Id: 0

Problem signature:
P1: 2
P2: 1
P3: 0x80780102
P4: 0x8078001d
P5: 0x00000000
P6: 0x8078001d
P7: 0x80780064
P8: 0x00000000
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2_eb4095c0d039d80764d38dbbea8fdad2a78b745_00000000_2e4eb9ec <SEE FILE CONTENTS BELOW>

Analysis symbol:
Rechecking for solution: 0
Report Id: ade020c0-b5be-11e5-813a-fc15b421aaed
Report Status: 4100
Hashed bucket:

=================================event 2===============================

Event ID: 517 / Source: Backup / Log Name: Application

XML DATA

start backup -backupTarget:\\WDMYCLOUD\administrator\automat\ -include:"D:\AGRO" -quiet

I have this problem since about 23rd December on a 2012 R2 Essentials Server.

Using a VSS backup application (Macrium Reflect 5.3).

It sometimes works now, but mostly fails to backup. I have rebooted etc.

What is happening, is that during shadow copy creation, Active Directory database engine ESENT seems to switch to using the shadow version of the active directory database (ntds.dit), but then decides that the edb.log has range checksum mismatches.

The system is running fine but will not do backups! Maybe 1 in 20 will succeed.

Shadow creation starts, then I see these events:

Information09/01/2016 00:22:11ESENT102General

lsass (588) The database engine (6.03.9600.0000) is starting a new instance (1).

Information09/01/2016 00:22:11ESENT216Logging/Recovery

lsass (588) A database location change was detected from 'C:\Windows\NTDS\ntds.dit' to '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Windows\NTDS\ntds.dit'.

followed by:

Information09/01/2016 00:22:11ESENT300Logging/Recovery

lsass (588) The database engine is initiating recovery steps.

Information09/01/2016 00:22:11ESENT216Logging/Recovery

lsass (588) The log range read from the file "\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Windows\NTDS\edb.log" at offset 9007104 (0x0000000000897000) for 4096 (0x00001000) bytes failed verification due to a range checksum mismatch.  The expected checksum was 0 (0x0) and the actual checksum was 9442647854575 (0x89689abcdef). The read operation will fail with error -501 (0xfffffe0b).  If this condition persists then please restore the logfile from a previous backup.

Error09/01/2016 00:22:12ESENT465Logging/Recovery

lsass (588) Corruption was detected during soft recovery in logfile \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy28\Windows\NTDS\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 2199 (0x00000897). This logfile has been damaged and is unusable.

Error09/01/2016 00:22:12ESENT454Logging/Recovery

lsass (588) Database recovery/restore failed with unexpected error -501.

I'm not sure if it is supposed to switch database location to shadow copies during shadow creation? Does anybody know?

I've exhausted all of my Googling powers now, hence the post! I did wonder if it was a 4kb issue or something. It's a Lenovo TS140 server, 2012 R2 Essentials, 2x 1tb SATA on Intel C600 RSTe RAID1 (motherboard/soft/fake raid). The volume is reported as 4kb physical and 512 logical (i.e. 512e), which is about the norm nowadays.

Grateful of any help!

I use "windows server backup" to backup my Windows Server 2008R2 and Windows Server 2012 R2 boxes.
Using the GUI interface to "windows sever backup" I can:
o find the various instances of disk backups
o drill down into the directory structure of a given instance of a disk backup
o select a single file to be recovered

I want to look at all instances of a file that are available to be recovered.  This feature is offered in "windows explorer" via the "previous versions" tab.  How do I get that same "previous versions" capability via the "windows server backup" recover gui?

Are there other utilities (other than the "windows server backup" recover gui) that allow me to peruse the backup catalog?

Is there any way to peruse the catalogue using powershell cmdlets?

thanks