Windows Server 2012 Backup Issue

Hi Guys

We an issue with a newly installed VM running server v2012 R2, we are trying to backup to NAS however it always fails with the following error
"The backup operation that started at '‎2015‎-‎06‎-‎03T09:58:25.197049600Z' has failed with following error code '0x807800C5' (There was a failure in preparing the backup image of one of the volumes in the backup set.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

We cant understand why as we have a second VM running server 2012 backing up to the same NAS without any problem.

Any ideas?
Daniel BertoloneAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mark BillExchange, AD, SQL, VMware, HPE, 3PAR, FUD, Anti MS Tekhnet, Pro EE, #1Commented:
Hi,

1. We are using Windows Backup here right?

1. What does the event log say? any errors or warnings related to this backup or VSS. Application and System Log.

2.  What is the backup schedule?

3. What are you backing up in the backup config?

4. What size is a full backup of this data?



Thanks
noxchoGlobal Support CoordinatorCommented:
Run chkdsk x:/f on all partitions first then retry backup.
Daniel BertoloneAuthor Commented:
Hi guys

Apologies with the delay. I tried to run a chkdsk however i receive the following "Cannot open volume for direct access."
Active Protection takes the fight to cryptojacking

While there were several headline-grabbing ransomware attacks during in 2017, another big threat started appearing at the same time that didn’t get the same coverage – illicit cryptomining.

noxchoGlobal Support CoordinatorCommented:
Does it suggest that you plan the check for next restart?
Daniel BertoloneAuthor Commented:
no it never gave me the option to run upon restart, I did however manage to run chkdsk without any additional parameters and the results looks fine:

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          06/06/2015 16:59:03
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      UKSRV01.contoso.local
Description:


Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.                        

Stage 1: Examining basic file system structure ...
  284928 file records processed.                                                        

File verification completed.
  4120 large file records processed.                                  

  0 bad file records processed.                                    


Stage 2: Examining file name linkage ...
  347398 index entries processed.                                                      

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      


Stage 3: Examining security descriptors ...
Cleaning up 403 unused index entries from index $SII of file 0x9.
Cleaning up 403 unused index entries from index $SDH of file 0x9.
Cleaning up 403 unused security descriptors.
Security descriptor verification completed.
  31236 data files processed.                                          

CHKDSK is verifying Usn Journal...
  323247872 USN bytes processed.                                                          

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 733642751 KB total disk space.
  16866944 KB in 116244 files.
    127128 KB in 31237 indexes.
         0 KB in bad sectors.
    690243 KB in use by the system.
     65536 KB occupied by the log file.
 715958436 KB available on disk.

      4096 bytes in each allocation unit.
 183410687 total allocation units on disk.
 178989609 allocation units available on disk.

Internal Info:
00 59 04 00 25 40 02 00 99 9f 04 00 00 00 00 00  .Y..%@..........
45 24 00 00 56 00 00 00 00 00 00 00 00 00 00 00  E$..V...........

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-06-06T15:59:03.000000000Z" />
    <EventRecordID>8478</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>UKSRV01.contoso.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.


A disk check has been scheduled.
Windows will now check the disk.                        

Stage 1: Examining basic file system structure ...
  284928 file records processed.                                                        

File verification completed.
  4120 large file records processed.                                  

  0 bad file records processed.                                    


Stage 2: Examining file name linkage ...
  347398 index entries processed.                                                      

Index verification completed.
  0 unindexed files scanned.                                        

  0 unindexed files recovered.                                      


Stage 3: Examining security descriptors ...
Cleaning up 403 unused index entries from index $SII of file 0x9.
Cleaning up 403 unused index entries from index $SDH of file 0x9.
Cleaning up 403 unused security descriptors.
Security descriptor verification completed.
  31236 data files processed.                                          

CHKDSK is verifying Usn Journal...
  323247872 USN bytes processed.                                                          

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 733642751 KB total disk space.
  16866944 KB in 116244 files.
    127128 KB in 31237 indexes.
         0 KB in bad sectors.
    690243 KB in use by the system.
     65536 KB occupied by the log file.
 715958436 KB available on disk.

      4096 bytes in each allocation unit.
 183410687 total allocation units on disk.
 178989609 allocation units available on disk.

Internal Info:
00 59 04 00 25 40 02 00 99 9f 04 00 00 00 00 00  .Y..%@..........
45 24 00 00 56 00 00 00 00 00 00 00 00 00 00 00  E$..V...........

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>
noxchoGlobal Support CoordinatorCommented:
Are you imaging entire drive or a selected partition? Try partitions one by one. So you can narrow it to a problem partition.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Daniel BertoloneAuthor Commented:
I have selected all active partitions using the windows backup, I will try each partition and let you know. Strange thing is we have another VM setup exactly the same on the host which backs up without any issues.
Daniel BertoloneAuthor Commented:
I tried what you mentioned by selecting each partition individually and running a backup which worked each time. I then selected the option to backup all partitions as I initially set the backup and it worked first time and has been running for over one week. Running the backup manually against each partition must have cleared something?

Thanks again
noxchoGlobal Support CoordinatorCommented:
Pretty possible. Maybe the old snapshot file was not cleared by some interrupted snapshot procedure. Anyway, glad to hear you got it resolved finally.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.