I have a Windows Server 2008 R2 machine being backed up using Backupassist but also utilizing VSS.  The backups destination drive is iScsi drive (qnap). Recently I discovered that my previous backups were deleted and I am getting below log. The shadow copies were deleted during backup process.

Event ID:25  Source: volsnap

The shadow copies of volume Y: 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.

Hello,

Last few days our backups (Veritas NetBackup) no longer work for Exchange 2010 server on Windows 2008 R2 SP1.VSSis still in error:

Microsoft Exchange Writer State [5]Waiting for completion / Last errorRetryable error.

After complete reboot it returns tostate [1] Stable / Last errorno error

Begins to turn again Veritas NetBackup and same error occurs.

I see also that my sevrver owns 2disks (in disk manager) with the following data

volume:<blank>/ Layout Single / Type Basic /File System <Blank> / Status Healthy / Capacity 0MB

Other disks are OK and DISKPART does not show this 2 disks.

Symantec tells us that the problem comes from VSS / Microsoft.

Any idea of the problem? How to troubleshoot VSS with Exchange provider/writer?VSSseems verypoorly explained by microsoft. Many problems andveryfew solutions (reboot and see)

Thank you in advance

Hi,

Just wondering if anyone knows how to create a scheduled backup in Windows Server 2012 R2 that will store a backup copy on both an internal drive and an external drive?

Windows backup makes a copy on the internal 1TB drive (incremental) but does not store a copy on the external drive (yes both are added in as destination drives). I get the feeling it only sees the external as additional space.

Cheers.

When I run the configuration for the native backup in SBS 2011 I get a warning saying "Warning cannot disable circular logging for backing up Exchange".

I did not setup this system originally. Exchange is not used for this company.

When I open up Exchange I get the following message: Connecting to the remote server failed with the following error message  The WinRm Client received an HTTP error server service error (500).

If Exchange is not active on this server, can I disable it entirely?

Thanks,

Paul

PAUL

Prezados,

Gostaria de saber se tem algum patch e/ou programa para que eu possa restaurar no Windows Server 2003 R2, backup gerado pelo Windows Server 2012 Fundation ?

Desde já agradeço a atenção,

Alexandre Delgado
Analista de TI

The Windows Server Backup is forcibly closed. When I try to open it from the administrative tools I get the error "MMC can not open the file" and the file path with the error present in the print screen.
Check the path and this program, double click and give me actually get the error, the user that has execute permissions high, then the program was abruptly halted.
In the server manager can display the windows server backup no errors, it's just when I try to open it directly.
I want help resolving this error, the eventviewer presents no mistake.
  I attached the message ....

thanks

Hello!

I need to move/migrate a Windows Server 2008 R2 (Domain controller, alone) to new hardware.

So to do this i have:

* Maked a full backup of the old server, with Windows Server Backup
* Restored the backup on the new server, using a Windows Server 2008 R2 install disc.

But when i start the new server this is happening: http://goo.gl/2TcaUQ (Skip to 1:30)
Here you see at the last second that the server is rebooting.

* I tried to start the server with boot logging, but the log file is empty.
* I tried startup repair, but i did not find any tool (used a tool to remove local password) See here: http://goo.gl/NOg7Yb

But if i do a new install of Windows Server 2008 R2 the server it starting just fine.

But I needall applications,SQLServer,domainsetupetc. onthe old server.

What to do?

Environment:

Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.

Background:

My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.

I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.

For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.

Problem:

When I try to run the Backup Once operation to test my backup, I get the following error message:

"Windows Backup cannot read the backup destination."

What I've tried:

I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.

Adding the backup user to the Administrators group did not have an effect.

Update 2014-02-18

I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully.However, Backup Once always results in the above error message. So the problem is confined to the "Backup Once" operation.

I have two Hyper-V 2012 Servers on which I have scheduled a number of backup jobs using the SCHTASKS command. The backups have been running fine since I created the tasks on 2/26/2014 until last night. On one of the servers the backup was supposed to run at 6:00pm last night and on the other one it should have run at 7:00pm. On both of them the backup task was apparently not triggered, when I view the event logs for the task manager there is no entry there at all for those times.

On the server where the backup was supposed to run at 6:00 last night I brought up the task manager and see this for the job.

Name: WeeklyBackupMonday

Status: Ready

Triggers: at 6:00 pm every Monday of every week starting 2/26/2014

Next Run Time: 3/17/2014 at 6:00pm

Last Run Time: 3/3/2014 at 6:00pm

Result: The last job finished successfully.

Clearly the job that was supposed to run on the 10th did not run, the same thing is happening on both servers. The other server has a backup job that is supposed to run on Sunday and it also did not run. The history shows that prior to Sunday the jobs were running normally.

I find it very strange that both servers started exhibiting the same issue simultaneously and am having a difficult time knowing how to troubleshoot the issue as I can not find anything in the logs regarding why it may have failed. Can any one point me in the right direction for troubleshooting this issue?

Thanks in advance.

Hi all,

Background of problematic server - Server 2008 R2 SP1 running as a Hyper-V host. Runs 1x guest. Backing up full server using Windows backup to a 2TB SATA harddisk. Backup used to work until an ISCSI connection is disconnected in the guest. BackupWORKS if guest is turned off

Background of guest server - Server 2008 R2 SP1. DC and Exchange 2010 installed. It's backup target used to be a NAS via ISCSI. Now it is backing up to an attached VHD file

Error on host

In event viewer > Windows Log > Application :

Event 521, Backup-

The backup operation that started at '‎2014‎-‎02‎-‎23T10:00:15.400000000Z' 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 '2155348129'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

In event viewer > Applications and Services logs > Microsoft > Windows > Hyper-V-VMMS :

Event 10112, Hyper-V-VMMS-

The number of volumes reverted does not match the number of volumes in the snapshot set for virtual machine 'GUEST-OS' (Virtual machine ID 30437CA0-AD79-4ADD-81A7-F52D3EA9C5BB).

After a failed backup, "VSSadmin list writers" shows the below:

Writer name: 'Microsoft Hyper-V VSS Writer'
   Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
   Writer Instance Id: {7ef38770-bb0c-4ad3-8628-6e2c2a6a5873}
   State: [5] Waiting for completion
   Last error: Unexpected error

Have tried applying the hotFix KB975354 (http://support.microsoft.com/kb/975354/en-us) only to be told that it isn't applicable to my system.

I can also confirm that the ISCSI connection is definitely dropped in guest. Also, I've disabled the service "Microsoft ISCSI initiator Service" in guest.

Would appreciate if anyone let me know what else to be looking out for.

Cheers,

Chriso

hello everyone

when i run wbadmin with the -authsysvol switch to do a system state restore of a 2008 domain controller once restarted netlogon and sysvol are not shared. dsa.msc wont start and everything is a bit of a mess. if i then go in and change the lastrestoreid in HKLM\SYSTEM\CurrentControlSet\Control\BackupRestore to another unique string and restart the server sysvol and netlogon are shared again and everything works normally. basically doesnt look like the authsysvol switch is working properly. does anyone have any ideas whats going on or what ive done wrong?

steps:

start dc in dsrepair mode

restore system state using wbadmin start systemstaterecovery -authsysvol version:"date" -backuptarget:"path" 

reboot

point dns to server ip

try and launch dsa/ type domain name\sysvol

get interface not found etc

the keys from this article are in the registry http://jorgequestforknowledge.wordpress.com/2010/08/12/restoring-the-sysvol-non-authoritatively-when-either-using-ntfrs-or-dfs-r-part-3/

i rename the restoreid to the string in the article reboot and everything is ok

thanks

Hi, trying to backup system image using SCDPM 2010 RTM.Most of the server are getting healthy backups except for this one server which is giving error:

Affected area:	Computer\System Protection
Occurred since:	1/27/2014 2:43:27 PM
Description:	The replica of System Protection Computer\System Protection on server.DOMAIN.COM is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent. 

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
	DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x80070057). (ID 30229 Details: Internal error code: 0x809909FB)
	More information
Recommended action:	For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.
	Synchronize with consistency check.
	Run a synchronization job with consistency check...
Resolution:	To dismiss the alert, click below
	Inactivate alert

On the server, event viewer show the following events:

1. Backup Log:

Backup started at '2014-01-27T11:26:21.356950100Z' failed with following error code '2147942487'.

2. Application Log:

The description for Event ID 517 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

27-Jan-14 11:26:21 AM
2147942487
%%2147942487

The resource loader failed to find MUI file

However, when I observe the backup process using "wbadmin get status", it reaches 99% then stops.

Running backup of volume Local Disk(C:), copied (97%).
Running backup of volume Local Disk(C:), copied (98%).
Running backup of volume Local Disk(C:), copied (99%).

Backup stopped before completing.

Summary of backup:
------------------


Backup stopped before completing.
The parameter is incorrect.

The server hardware is HP blade with two disk which are mirrored, and has 12 GB free space. below is the output from systeminfo command:

Host Name:                 server
OS Name:                   Microsoftr Windows Serverr 2008 Enterprise 
OS Version:                6.0.6002 Service Pack 2 Build 6002
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Member Server
OS Build Type:             Multiprocessor Free
Registered Owner:          Admin
Registered Organization:   -
Product ID:                55041-339-7818202-76771
Original Install Date:     04-Aug-08, 3:15:18 PM
System Boot Time:          21-Jan-14, 3:58:47 PM
System Manufacturer:       HP
System Model:              ProLiant BL460c G1
System Type:               x64-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
                           [02]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
BIOS Version:              HP I15, 02-May-11
Windows Directory:         C:\Windows
System Directory:          C:\Windows\system32
Boot Device:               \Device\HarddiskVolume1
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (GMT+03:00) Kuwait, Riyadh
Total Physical Memory:     16,381 MB
Available Physical Memory: 8,320 MB
Virtual Memory: Max Size:  21,821 MB
Virtual Memory: Available: 13,722 MB
Virtual Memory: In Use:    8,099 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    DOMAIN.COM
Logon Server:              N/A
Hotfix(s):                 157 Hotfix(s) Installed.
                           [01]: {47740627-D81D-4A45-A215-03B075A18EC7}
                           [02]: {3D019598-7B59-447A-80AE-815B703B84FF}
                           [03]: {A8E86480-A9C1-4414-8AA2-B05A485C82F0}
                           [04]: {C444285D-5E4F-48A4-91DD-47AAAA68E92D}
                           [05]: {DB33A524-845E-4855-9E90-A5619BCDD527}
                           [06]: {ECC3A660-90E3-4A89-9FE8-F8B3C633B12E}
                           [07]: {65AFCB03-3111-47E2-B1ED-198D6B0BC96E}
                           [08]: {F5E29D9D-519A-36C7-87E3-9A22A8180B1B}
                           [09]: KB971513
                           [10]: KB971512
                           [11]: 944036
                           [12]: 982861
                           [13]: KB960362
                           [14]: KB2079403
                           [15]: KB2117917
                           [16]: KB2141007
                           [17]: KB2160329
                           [18]: KB2183461
                           [19]: KB2207566
                           [20]: KB2286198
                           [21]: KB2296011
                           [22]: KB2296199
                           [23]: KB2305420
                           [24]: KB2345886
                           [25]: KB2347290
                           [26]: KB2387149
                           [27]: KB2388210
                           [28]: KB2416400
                           [29]: KB2416470
                           [30]: KB2419640
                           [31]: KB2423089
                           [32]: KB2436673
                           [33]: KB2442962
                           [34]: KB2443685
                           [35]: KB2447568
                           [36]: KB2467659
                           [37]: KB938464
                           [38]: KB942288
                           [39]: KB948609
                           [40]: KB948610
                           [41]: KB949189
                           [42]: KB950762
                           [43]: KB950974
                           [44]: KB951066
                           [45]: KB951698
                           [46]: KB951978
                           [47]: KB952004
                           [48]: KB952287
                           [49]: KB953733
                           [50]: KB954155
                           [51]: KB954459
                           [52]: KB955020
                           [53]: KB955069
                           [54]: KB955302
                           [55]: KB955430
                           [56]: KB955839
                           [57]: KB956250
                           [58]: KB956572
                           [59]: KB956744
                           [60]: KB956802
                           [61]: KB957097
                           [62]: KB957200
                           [63]: KB957321
                           [64]: KB957388
                           [65]: KB958481
                           [66]: KB958483
                           [67]: KB958623
                           [68]: KB958624
                           [69]: KB958644
                           [70]: KB958687
                           [71]: KB959130
                           [72]: KB959426
                           [73]: KB960225
                           [74]: KB960803
                           [75]: KB961371
                           [76]: KB961501
                           [77]: KB967190
                           [78]: KB967723
                           [79]: KB968389
                           [80]: KB968537
                           [81]: KB969058
                           [82]: KB969897
                           [83]: KB969897
                           [84]: KB969947
                           [85]: KB970238
                           [86]: KB970430
                           [87]: KB970653
                           [88]: KB971468
                           [89]: KB971486
                           [90]: KB971557
                           [91]: KB971657
                           [92]: KB971737
                           [93]: KB971930
                           [94]: KB971961
                           [95]: KB972036
                           [96]: KB972270
                           [97]: KB972636
                           [98]: KB973346
                           [99]: KB973507
                           [100]: KB973525
                           [101]: KB973565
                           [102]: KB973687
                           [103]: KB973917
                           [104]: KB974145
                           [105]: KB974318
                           [106]: KB974455
                           [107]: KB974470
                           [108]: KB974571
                           [109]: KB975364
                           [110]: KB975467
                           [111]: KB975517
                           [112]: KB975560
                           [113]: KB975759
                           [114]: KB975929
                           [115]: KB976098
                           [116]: KB976264
                           [117]: KB976470
                           [118]: KB976662
                           [119]: KB976749
                           [120]: KB976768
                           [121]: KB976772
                           [122]: KB977165
                           [123]: KB978251
                           [124]: KB978262
                           [125]: KB978542
                           [126]: KB978601
                           [127]: KB978886
                           [128]: KB979099
                           [129]: KB979306
                           [130]: KB979309
                           [131]: KB979482
                           [132]: KB979687
                           [133]: KB979688
                           [134]: KB979899
                           [135]: KB979910
                           [136]: KB980182
                           [137]: KB980195
                           [138]: KB980218
                           [139]: KB980232
                           [140]: KB980248
                           [141]: KB980302
                           [142]: KB980436
                           [143]: KB980842
                           [144]: KB981322
                           [145]: KB981332
                           [146]: KB981793
                           [147]: KB981852
                           [148]: KB982132
                           [149]: KB982214
                           [150]: KB982519
                           [151]: KB982664
                           [152]: KB982666
                           [153]: KB982799
                           [154]: KB983589
                           [155]: KB948465
                           [156]: KB960568
                           [157]: KB968930
Network Card(s):           1 NIC(s) Installed.
                           [01]: HP NC373i Multifunction Gigabit Server Adapter
                                 Connection Name: Local Area Connection 2
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: x.x.x.x
                                 [02]: fe80::f494:43c2:7d90:e774
Hyper-V Requirements:      VM Monitor Mode Extensions: No
                           Virtualization Enabled In Firmware: No
                           Second Level Address Translation: No
                           Data Execution Prevention Available: No

Things I have tried:

1. I tried to backup manually to external HDD using wsb snap-in, but it has failed in the same way.

2. Stop and re-add protection.

3. I have researched the error, some results suggest that some bad sectors might exist, however, when I run the command, it forces me to schedule the command on next boot. when I reboot, it loads windows after that gives a message "Cannot open the volume for direct access"

How to end this loop? please help. Thanks for considering my question ...

I have a Windows Server 2008 R2 machine being backed up using Backupassist but also utilizing VSS.  The backups destination drive is iScsi drive (qnap). Recently I discovered that my previous backups were deleted and I am getting below log. The shadow copies were deleted during backup process.

Event ID:25  Source: volsnap

The shadow copies of volume Y: 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.

Win Srv 2012 Essentails backup runs fine for several days, then hangs and adds "new virtual drives # 6 and #7 or similar". At the same time the server manager hangs with loading storage pool and further disk/drive - information.

Completely disconnecting / shut off and reconnecting the external USB-backup drive stops the error with an unsuccessful backup. 

Hi

We are having issues on one of our Windows 2008 servers with Windows Backup. The backups are failing on Sunday night through to Thursday night with the error "The system cannot find the file specified". However, the backup on a Friday and Saturday night run fine.

The backup starts at 10pm and the last member of staff leaves site at 6pm so there is no-one on the system using the files. I have also ran a chkdsk on each volume and they do not have any errors. I have also recreated the backup jobs without success.

I've about ran out of ideas and I'm hoping someone may be able to offer some ideas.

Thanks in advance

Rob

I set up a backup on my Windows 2012R2 Essentials server using the dashboard and this has been running (logs show so) for a couple of months. I thought I'd try to check out what I'd set to back u, maybe try a restore and maybe change the external disk.

However, when I go to the dashboard, devices select the server and the click on "Restore files or Folders" or "Customise Backup for this server" the "Set Up Server Backup" window pops up with "Loading Data. This can take a few minutes" and the ... just stays there. For ever.

I've rebooted, run chkdsk, but cannot get past this point (I have to shut down the Dashboard to clear it)

I have a service pack from HP to apply but I don't want to do anything until I know I have  agood backup.

Hello.

I am trying to create a powershell script that will check the last 3 backups taken om my domain controllers and send the result of that to chosen recipients with e-mail.

 The main problem i have noticed is that when i run get-wbjob -previous 3 command it will only generate the result on the local server. Is there any way to query cross server or will i have to create a scheduled task for each DC?

Thanks

/Lee