I have a new Dell R710 that I have 2008 Server R2 64-bit installed. It's role is file server. I first noticed there were VSS initialization issues in BackupExec and that the system state wasn't getting backed up.
 
Then I would run "vssadmin list writers" from CMD and system writer would be timing out....
 
Writer name: 'System Writer'
    Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
    Writer Instance Id: {18370018-3454-46cf-a352-db13b2536aa6}
    State: [7] Failed
    Last error: Timed out
 
I would also get Event ID 12289 Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} - 0000000000000140,0x0053c020,00000000003BDFD0,0,00000000003BBFA0,4096,[0]).  hr = 0x80070057, The parameter is incorrect.
 
I would also get Event ID 12293 Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details IVssSnapshotProvider::IsVolumeSupported() failed with 0x8000ffff [hr = 0x8000ffff, Catastrophic failure
 
Also event ID 22 for volsnap The shadow copy storage volume specified for shadow copies on volume\\?\Volume{caaccaea-2a96-11e1-b14b-806e6f6e6963} could not be added.
 
Also I can't configure shadow copies due to error 0x8004230f "Failed to retrieve volumes that are eligible for shadow copies.

PLEASE HELP!

Hello!

I have a problem with two VM´s on a HP Proliant ML350p Gen8, that has Windows Server 2012R2 operating system with Hyper-V role installed.

Both VM´s are also 2012R2, one is DC/DNS/FILE/PRINT and the other one is Exchange 2013.

The problem itself is that, when Windows backup (wbengine.exe - Block level backup engine service) inside VM starts, it uses almost maximum CPU resource, so the VM´s CPUs are 100% used. Backup itself is not working, there is no network trafic. Only way to get rid of 100% CPU usage is to restart the server.

When i start backup manually (Backup once - scheduled backup options), it is working and the CPU usage is around 20-30%.

One VM (DC/DNS/FILE/PRINT) has 2x vCPU and Exchange has 4x vCPU.

The problem started suddenly, the backup were performing slowly and failed.

Backups are scheduled on different time. Host level Hyper-V backup of VM´s works without any problem.

The backup location is Synology DS414 NAS and the servers are set up using iSCSI, for connecting separate backup lun´s for each server.

The Hyper-V host and both VM´s are patched up-to-date. Ofcourse i have tried a lot of restarts, looking event log, VSSADMIN - cannot find any errors...

The network setup:

Hyper-V host has a team of two physical adapters, that is set up with a external virtual switch (shared with management operating system) and used by the VM`s normal network trafic.

Hyper-V host itself is using separte physcial network card, for connecting with iSCSI to Synology NAS.

I tried to set up another physical network card on the host and create a new virtual swich, add extra virtual nic to VM`s and use this for iSCSI traffic for Windows backup and it didnt make things better.

I need to find a solution, because i cannot restart the server every night for the backups to work.

Server 2012 R2 Datacenter

Source : volsnap

event id : 20

The shadow copies of volume C: were aborted because of a failed free space computation.

Please Help

Server 2012 R2 Datacenter

Source : volsnap

event id : 20

The shadow copies of volume C: were aborted because of a failed free space computation.

Please Help

Hi,

 I am backing up virtual machines by Windows Server Backup and everything work with exception of one server - RDS. The machine is backed up but Windows server backup keeps only last six copies altough there is 272GB of 459GB of free space. This is not he case for other servers(file, print, database, dc,...).

 Is there a way how to force WSB to use all the space?

Thank you.

Pete

sfs

I have a Lenovo Yoga 2 Pro laptop that will not backup to my Windows 2008 R2 Storage Server.

These are the most recent events:

Log Name:      Application
Source:        .NET Runtime
Date:          10/2/2014 11:06:10 AM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SMOSA03
Description:
Application: SharedServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssComponent..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssWriter..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssExamineWriterMetadata)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet.CreateShadowVolume(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[])
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[], Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.IBackupReportProgress)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.RunWithoutCatch()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.Run()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.BackupTask.OnBackupStart(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-02T16:06:10.000000000Z" />
    <EventRecordID>28116</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SMOSA03</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: SharedServiceHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent.GetFile(UInt32)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssComponent..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssWMComponent)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.VssWriter..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.IVssExamineWriterMetadata)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet.CreateShadowVolume(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[])
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.VSS.ShadowVolumeSet..ctor(Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.VolumeInfo[], Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.IBackupReportProgress)
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.RunWithoutCatch()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupOp.BackupSetOperation.Run()
   at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.Provider.BackupTask.OnBackupStart(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
</Data>
  </EventData>
</Event>

------------------------------------------------------------------------------------------------------------------------------

Log Name:      Application
Source:        Application Error
Date:          10/2/2014 11:06:11 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SMOSA03
Description:
Faulting application name: SharedServiceHost.exe, version: 6.1.1839.0, time stamp: 0x4d38a956
Faulting module name: msxml3.dll, version: 8.110.9600.17120, time stamp: 0x536da0ed
Exception code: 0xc0000005
Fault offset: 0x00000000000194ea
Faulting process id: 0x2600
Faulting application start time: 0x01cfde4c9ff44873
Faulting application path: C:\Program Files\Windows Server\Bin\SharedServiceHost.exe
Faulting module path: C:\windows\System32\msxml3.dll
Report Id: 06387ec6-4a4e-11e4-827a-8cae4cfd34be
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-02T16:06:11.000000000Z" />
    <EventRecordID>28117</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SMOSA03</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SharedServiceHost.exe</Data>
    <Data>6.1.1839.0</Data>
    <Data>4d38a956</Data>
    <Data>msxml3.dll</Data>
    <Data>8.110.9600.17120</Data>
    <Data>536da0ed</Data>
    <Data>c0000005</Data>
    <Data>00000000000194ea</Data>
    <Data>2600</Data>
    <Data>01cfde4c9ff44873</Data>
    <Data>C:\Program Files\Windows Server\Bin\SharedServiceHost.exe</Data>
    <Data>C:\windows\System32\msxml3.dll</Data>
    <Data>06387ec6-4a4e-11e4-827a-8cae4cfd34be</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

-------------------------------------------------------------------------------------------------------------------------------

Log Name:      Application
Source:        Windows Error Reporting
Date:          10/2/2014 11:06:19 AM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      SMOSA03
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SharedServiceHost.exe
P2: 6.1.1839.0
P3: 4d38a956
P4: msxml3.dll
P5: 8.110.9600.17120
P6: 536da0ed
P7: c0000005
P8: 00000000000194ea
P9:
P10:

Attached files:
C:\Windows\Temp\WER975A.tmp.appcompat.txt
C:\Windows\Temp\WER9807.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\triagedump.dmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805

Analysis symbol:
Rechecking for solution: 0
Report Id: 06387ec6-4a4e-11e4-827a-8cae4cfd34be
Report Status: 4
Hashed bucket:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-10-02T16:06:19.000000000Z" />
    <EventRecordID>28118</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SMOSA03</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>SharedServiceHost.exe</Data>
    <Data>6.1.1839.0</Data>
    <Data>4d38a956</Data>
    <Data>msxml3.dll</Data>
    <Data>8.110.9600.17120</Data>
    <Data>536da0ed</Data>
    <Data>c0000005</Data>
    <Data>00000000000194ea</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Windows\Temp\WER975A.tmp.appcompat.txt
C:\Windows\Temp\WER9807.tmp.WERInternalMetadata.xml
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\memory.hdmp
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805\triagedump.dmp</Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_SharedServiceHos_ab5d84ebb13ea4375c1a3ac86cd4049e7ce1d_5bed2e30_cab_24ee9805</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>06387ec6-4a4e-11e4-827a-8cae4cfd34be</Data>
    <Data>4</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Hi

I have a Windows Server 2012 that is running HyperV and two virtual machines. I set it up with Windows backup when I installed the machine about 6 months ago and it all worked fine (backing up to external hard drives on rotation).

Recently backups have not been working properly. The backup is configured to backup everything (except for the backup target) as follows:

• Bare metal recovery
• System state
• Hyper-V
• - VM1 (Backup using child partition snapshot)
  
• - VM2 (Backup using child partition snapshot)
• (Disk does not have drive letter) - boot partition by HP
• Local Disk (C:)

The backup is now not working properly, with the message "Completed with warnings"

Drilling down to the logs shows that although it is backing up the C drive, it is not correctly backing up the virtual machines which means I will have a lot of trouble when I want to restore them. Here's the full log:

Backup of volume \\?\Volume{e30e3fba-40c1-11e3-93e8-806e6f6e6963}\ succeeded.

Backup of volume C: succeeded.

Application backup
*-----------------------------*

Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Error in backup of C:\ during enumerate: Error [0x80070003] The system cannot find the path specified.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 128700EA-A66A-4722-9757-9473AE8E46F0
   Caption     : Backup Using Child Partition Snapshot\VWL-EX
   Logical Path:
   Error           : 8078010D
   Error Message   : Enumeration of the files failed.

   Detailed Error  : 80070003
   Detailed Error Message : (null)


Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: CD8B7B3E-BF81-4A62-B7AB-FC0BD40AA2B1
   Caption     : Backup Using Child Partition Snapshot\VWL-DC
   Logical Path:
   Error           : 8078010D
   Error Message   : Enumeration of the files failed.

   Detailed Error  : 80070003
   Detailed Error Message : (null)


Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: Host Component
   Caption     : Host Component
   Logical Path:
   Error           : 8078010D
   Error Message   : Enumeration of the files failed.

   Detailed Error  : 80070003
   Detailed Error Message : (null)


*-----------------------------*

What is causing this to happen please? I have completely re-setup the backup routine and am using a brand new external hard drive.

Hi



In windows 2008 server R2, it is connecting to production network through the teamed network adapter.Ip of the teamed adapter is 10.157.86.31 255.255.255.0 and its gateway is 10.157.86.1



And the server is getting backed up with the backup interface configured with 10.128.141.64 255.255.248.0 in one of the nic in the server connected to the NAS Drive with the ip address 10.128.141.28 .The backup was happening perfectly as the backup is a non-routed network.



Once the motherboard of the server is changed, suddenly the backup stopped worked failing in authentication to the NAS drive because in NAS Drive authentication is setup based on the ip addresses of the servers connected to the NAS Drive.

What I have found is that even though the server's backup ip address is not changed , still the NAS drive ip 10.128.141.28 is reached via another network gateway 10.157.86.31 even though the NAS DRive is connected in the same subnet.

Since the NAS DRive is reached by the server through the ip address of the gateway 10.157.86.31, the authentication fails with the NAS drive because it expects the ip address to be as 10.128.141.64

how to force the traffic to the ip 10.128.141.28 to initiate through the nic 10.128.141.64 ?


Any suggestions please

Below is the answer for the problem ; already implemented and backup is working

But needed the clarification

Below is the solution too:

In spite of rebuild of the server from scratch by freshly installing the operating system , the backup vlan is not connected.So I decided to connect the cable coming from the switch port to the unused nic port of the server and it solved the issue by reconfiguring the ip address to the new nic port.

But needed one clarification here:

Before swapping the cable to spare nic the picture is below


Highlighted above is the nic connected to the backup vlan through which no communication happens.

So decided to swap the cable from lan1 (backup) which is a separate nic to the spare nic available in the server which is higlighted below





After configuring the backup ip address to the new spare nic also resulted in the traffic routed the production vlan which should not be the case.And moreover my observation from the above screeshot , why swapping the cable from the lan1(non-teamed adapter) is showing that lan4 (teamed adapter)as disconnected .

And moreover , currently the setup is working as below with the backup traffic happening through the backup vlan when it is configured in the above manner

Thanks & Regards S.Swaminathan Live & let others live!!!

Hello,



I am looking at changing out an older Windows 2003 Standard server and installing a new HP Proliant 310 server that will  run Windows 2008 R2.

I did not setup the 2003 server and have not installed Terminal Server before. All the users RDP into the current server for everything - email (Outlook and Outlook Express), applications (Church application that handles all aspects of the congregation), files documents. 

My purpose of this is inquiry is to make sure everything gets backed up properly.

The proposed new server would be setup without Terminal Services. The clients would login to the domain and gain access to shared files on the server and have all the apps installed on their computer(s). 



What is the best way to backup the existing server and make sure all the user profiles data get backed up?



Doing some research on this I was thinking of connecting an external hardrive that is formatted as FAT32. Then open a Remote Desktop to the server under each client or profile, back up each clients files, PST files and so on to the external drive. Then transfer all the backup and move the files to their folder on the server and also the public folder as well. The main church application is in its own folder and I can move the entire folder to a backup drive per the software company.



Is this the best way to accomplish the backup of their data? Will it work?



Any thoughts tips, suggestions would be helpful.



Thanks,

Paul

PAUL

Hello,



I am looking at changing out an older Windows 2003 Standard server and installing a new HP Proliant 310 server that will  run Windows 2008 R2.

I did not setup the 2003 server and have not installed Terminal Server before. All the users RDP into the current server for everything - email (Outlook and Outlook Express), applications (Church application that handles all aspects of the congregation), files documents. 

My purpose of this is inquiry is to make sure everything gets backed up properly.

The proposed new server would be setup without Terminal Services. The clients would login to the domain and gain access to shared files on the server and have all the apps installed on their computer(s). 



What is the best way to backup the existing server and make sure all the user profiles data get backed up?



Doing some research on this I was thinking of connecting an external hardrive that is formatted as FAT32. Then open a Remote Desktop to the server under each client or profile, back up each clients files, PST files and so on to the external drive. Then transfer all the backup and move the files to their folder on the server and also the public folder as well. The main church application is in its own folder and I can move the entire folder to a backup drive per the software company.



Is this the best way to accomplish the backup of their data? Will it work?



Any thoughts tips, suggestions would be helpful.



Thanks,

Paul

PAUL

I have a 2012 DC that crashed during a System State restore..the server hardware vendor believes my original issues and reasons for initial problems were caused by a bad raid card.

I am now trying to get this DC back in a functioning state so I can demote it gracefully and remove some services from it (DNS/DHCP).

If I boot the computer to DSR it will reboot sporadically.  Is there a way to do a system state restore besides this?  From a command prompt? 

Thanks for any assistance.

Hello,

I'm novice to this area, after the execution of all the instructions for setting up the backup agent gives an error message: "Microsoft Azure Recovery Services Agent was unable to create a snapshot of the selected volume. Please try the operation again. If the issue persists, contact Microsoft Support(0x186C2)".

So,I experience a problem making a snapshot of selected volume.

Operating System Windows Server 2012 installed on the virtual machine in the cloud, on the server the agent is installed and the file backup is also on this server.

Thanks in advance for your help!

Vyacheslav.

I wrote a program to copy server A’s volume 0 to server A’s volume 1.

Volume 1 is then moved from server A and placed in server B.

When server B is started I get the error: Windows failed to start. Status: 0xc000000e.

http://support.microsoft.com/kb/2261423

Running X:\Sources\Recovery\StartRep.exe will fix this problem.

This will not be an option for my disaster recovery plan as no one will be there to enter this command.

The above url indicates that I can run bcdedit to fix this problem. 

On server A, once the volume copy is complete, drive letter I is assigned to the volume. I run the three bcdedit commands against drive I:

bcdedit /set {default} device partition=i:

bcdedit /set {default} osdevice partition=i:

bcdedit /set {bootmgr} device partition=i:

This does not resolve the Windows failed to start. Status: 0xc000000e error.

We've got a 2008 R2 server connected via iSCSI initiator to a Readynas 3200 device, and Windows Server Backup is configured to backup to that disk nightly. Weeks will go by and it will work great... all backups appear in the history when the "View Details" link is clicked in the Destination Usage section. The last time I checked, we had 27 backups available.

Our server had 2TB mirror'd drives that both failed at the same time. Mirror / RAID 1 is software based.  Backup's partition is single mirror 1863GB and 332GB actual data.

We're attempting to restore off a saved backup over the network using two new 3TB drives connected in the same way as the previous ones.

Restore is being done with DVD of OS and selecting Repair Your Computer and going through all the steps. Everything is located and seems fine right up

to where Restore attempts to prep the disks to write on.  (Same result with 1 physical disk connected too.)

"Failed to update disk partition layout 0x0C0380037".  Disks seem fine and can be accessed and manipulated with diskpart. 

Happens with clean / RAW state drives or even simple volume formatted ones of correct size.

I have a fresh install of Windows Server 2012 R2 on an IBM x3530 M4 server.  I'm trying to do a full bare metal backup to a local volume, which is presented from a SAN.

The backup fails stating that there isn't enough disk space.  This is very misleading as the OS on the C:\ is only taking up 15GB and the free Space on the SAN volume is 800GB.

From doing a little reading online i have found others who have had problems backing up Recovery Partitions, click here.  So i just did a backup of the C:\ to the same SAN volume and that works fine so i have a feeling this is something to do with the Recovery Partition.  I also have a partition which is called the EFI System Partition which i'm unsure what this is.  Below is a screen grab of the Disk Management on the system.  Can someone give me a way to do a full Bare Metal backup without having to reinstall the whole OS.  Thanks

Hi,

Firstly I'd like to mention that I have found posts with the same question-error, tried everything that was proposed as a solution and still face this situation. I have a windows 2008 server with AD and client PCs all living together on the same domain. This backup error is present at some client Pcs while others run the backup scheduled flawlessly.

Once again I mention that I have double checked that I have correct Time Zones, correct date and time, both in Windows and BIOS. Have tried to change the scheduled tasks' "configure for" part to windows 7 and so, with no result. And generally everything else that was proposed at this post, http://answers.microsoft.com/en-us/windows/forum/windows_7-system/next-backup-date-reads-12301899-1200am/62637bf9-7de4-446a-be51-f68e299c9ea1?rtAction=1411015328406 , I have tried to do with no luck. So I am asking for help on this issue, because it can't be that some PCs of mine work fine and some are not. Thank you in advance for your support.