Solved: Split the backups (such as

TRIPLE_M · ‎10-01-2014

On the server I have BE 2012 SP2 loaded the backup of itself keeps failing.

I keep getting VSS snapshot unexpected provider errors. Am getting two event ID errors ...these follows

Event ID : 12293

Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details EndPrepareSnapshots({791dcfa9-a2f8-4bb5-9673-5f08e9dfa089}) [hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
Check the Application event log for more information.
].

Operation:
Executing Asynchronous Operation

Context:
Current State: DoSnapshotSet

Event ID:8193

Volume Shadow Copy Service error: Unexpected error calling routine Cannot find anymore diff area candidates for volume \\?\Volume{82dc8839-533f-11e2-86ad-e4115bde935d}\ [1]. hr = 0x8000ffff, Catastrophic failure
.

Operation:
Automatically choosing a diff-area volume
Processing EndPrepareSnapshots

Context:
Volume Name: \\?\Volume{03e7b482-50c5-11e2-bb72-806e6f6e6963}\
Volume Name: \\?\Volume{82dc8839-533f-11e2-86ad-e4115bde935d}\
Volume Name: \\?\Volume{82dc8842-533f-11e2-86ad-e4115bde935d}\
Volume Name: \\?\Volume{82dc884b-533f-11e2-86ad-e4115bde935d}\
Volume Name: \\?\Volume{03e7b481-50c5-11e2-bb72-806e6f6e6963}\
Execution Context: System Provider

The backup job completes with errors after backed up upto 1400GB, Plz help me put to solve this problem.

VJware · ‎10-08-2014

Split the backups (such as one separate backup for System State) and then probably best to enable debugging and rerun the backup jobs.

View solution in original post

CraigV · ‎10-01-2014

Hi,

Have you tried to restart the server in question? Also, have you specified a VSS provider in the options for the job, or left it at Automatic? If you did specify which VSS writer to use, change this to the Automatic option and try again.

Thanks!

TRIPLE_M · ‎10-01-2014

Ya i done restart and VSS service set to automatic, although the job fails. We are using MS VSS provider only .. The system writer is not stable ..It is in Timeout only where i checked with vssadmin list writers in cmd .

VJware · ‎10-01-2014

Set the shadow copy configuration of each drive to no limit.

Once the VSS writers are in a stable state (usually a reboot does this), are you able to get a successful backup using the native Windows backup utility ?

TRIPLE_M · ‎10-03-2014

I Am not configure shadoy copy configuration of any drive , before twoo weeks it works fine ...And also that job bakedup up to 1400GB at the end only our job fails and gives above error on event viewer.

TRIPLE_M · ‎10-03-2014

I found one article , http://support2.microsoft.com/kb/2009272

I enter following commands in command prompt , then system writer is in stable and local system state backup is working fine now .

To resolve this issue, type the following commands from an elevated command prompt:

Takeown /f %windir%\winsxs\temp\PendingRenames /a
icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\temp\PendingRenames /grant BUILTIN\Users:(RX)
Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)

net stop cryptsvc
net start cryptsvc

Type the following command to verify that the system writer is now listed:
vssadmin list writers

If the system writer is missing, check the Application event log for the following event:

Log Name: Application
Source: VSS
Event ID: 8213
Level: Error
Description:
Volume Shadow Copy Service error: The process that hosts the writer with name System Writer and ID {e8132975-6f93-4464-a53e-1050253ae220} does not run under a user with sufficient access rights. Consider running this process under a local account which is either Local System, Administrator, Network Service, or Local Service.

Operation:
Initializing Writer

Context:
Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Name: System Writer

The Details section of the event (Binary Data\In Bytes) would show up as:

0000: 2D 20 43 6F 64 65 3A 20   - Code:
0008: 57 52 54 57 52 54 49 43   WRTWRTIC
0010: 30 30 30 30 30 37 32 39   00000729
0018: 2D 20 43 61 6C 6C 3A 20   - Call:
0020: 57 52 54 57 52 54 49 43   WRTWRTIC
0028: 30 30 30 30 30 36 34 39   00000649
0030: 2D 20 50 49 44 3A 20 20   - PID:
0038: 30 30 30 30 31 30 38 34   00001084
0040: 2D 20 54 49 44 3A 20 20   - TID:
0048: 30 30 30 31 38 39 37 36   00018976
0050: 2D 20 43 4D 44 3A 20 20   - CMD:
0058: 43 3A 5C 57 69 6E 64 6F   C:\Windo
0060: 77 73 5C 73 79 73 74 65   ws\syste
0068: 6D 33 32 5C 73 76 63 68   m32\svch
0070: 6F 73 74 2E 65 78 65 20   ost.exe
0078: 2D 6B 20 4E 65 74 77 6F   -k Netwo
0080: 72 6B 53 65 72 76 69 63   rkServic
0088: 65 20 20 20 20 20 20 20   e
0090: 2D 20 55 73 65 72 3A 20   - User:
0098: 4E 54 20 41 55 54 48 4F   NT AUTHO
00a0: 52 49 54 59 5C 4E 45 54   RITY\NET
00a8: 57 4F 52 4B 20 53 45 52   WORK SER
00b0: 56 49 43 45 20 20 20 20   VICE
00b8: 2D 20 53 69 64 3A 20 20   - Sid:
00c0: 53 2D 31 2D 35 2D 32 30   S-1-5-20

Open Regedit and navigate to the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl.
Change the value of NT AUTHORITY\NETWORK SERVICE (REG_DWORD) to 1.
You may also want to check the entry for other services (LOCAL SERVICE, NetworkService) as indicated by event 8213.

The 'System Writer' should now show up in the "vssadmin list writers" command:

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {04cf6316-f0c5-4ce7-bbe4-e56e6334124c}
   State: [1] Stable
   Last error: No error

TRIPLE_M · ‎10-06-2014

Yup , Am able to get a successful backup using the native Windows backup utility, Although the B2D job fails with above error . I Attached one file for your reference . That job backing up upto 1330GB after that fails. Kiindly give solution for this.

TRIPLE_M · ‎10-07-2014

Am able to get a successful backup using the native Windows backup utility, Although the B2D job fails with above error . I Attached one file for your reference . That job backing up upto 1330GB after that it fails. Kiindly give solution for this.

CraigV · ‎10-07-2014

...check the link below for Error 0x8004230f:

http://www.symantec.com/business/support/index?page=content&id=TECH159538

Thanks!

TRIPLE_M · ‎10-07-2014

I check wtih DISKPART , all volumes have lables and online too ...This is what mentioned in that article,

Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- ------
Volume 0 S System Rese NTFS Partition 100 MB Healthy System
Volume 1 C System NTFS Partition 59 GB Healthy Boot
Volume 2 E DS1 NTFS Partition 930 GB Healthy
Volume 3 F DS2 NTFS Partition 930 GB Healthy
Volume 4 G DS3 NTFS Partition 930 GB Healthy
Volume 5 H DS4 NTFS Partition 930 GB Healthy
Volume 6 J B2D NTFS Partition 3725 GB Healthy
Volume 7 D B2D NTFS Partition 1863 GB Healthy

VJware · ‎10-07-2014

Would you post the complete job log. Does the backup to tape complete successfully ?

TRIPLE_M · ‎10-07-2014

Yes sir, The backup to tape is completed successfully . PFA ,in that job log the backp to disk is failed but it backup upto 1204GB , and disk to tap job was completed succesfully .

VJware · ‎10-07-2014

Can you post the complete job log (not the screenshot). And would you pls verify the following:

Is the option to preallocate disk space enabled for the B2D storage ?

What is the shadow copy limit set for each volume ? Or is set to no limit ? (Even when shadow copies are not being used by you, set the maximum size to no limit)

Do any vss writer come up in a failed state post the backup failure to the disk ?

TRIPLE_M · ‎10-07-2014

Find attachement of job log whick bakup failed and successful respetively.

TRIPLE_M · ‎10-07-2014

1.We are not set shadow copy volume limit for any volume and there is no preallocate disk space in B2D storage, Before one month the backup job completed without no error ( that time also we are not set shadow copy limit ) .

2. System writer in stable only but when B2D job runs, the system writer is in failed state, below i copied current status of system writer

Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error

Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error

Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {3f796a20-5fb2-472a-b6fc-eab02b9e4b3c}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {4612ee48-c5cc-4bdf-b6fa-35007150e5c9}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {13a28037-0459-416e-a0f7-9146c42d10ce}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {8c3a9ce1-559f-4278-b385-3bf2b42b6743}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {b5838ad0-cb62-4d19-9e82-6b60456cfbbe}
State: [1] Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {5dd506de-eaa0-45f5-ad1c-f4d8e29c46ff}
State: [1] Stable

VJware · ‎10-07-2014

The successful job log is of a duplicate to tape, not a direct backup to tape.

Would you pls confirm the other 2 points asked earlier, i.e.

" What is the shadow copy limit set for each volume ? Or is set to no limit ? (Even when shadow copies are not being used by you, set the maximum size to no limit)

Do any vss writer come up in a failed state post the backup failure to the disk ? "

TRIPLE_M · ‎10-07-2014

1.We are not set shadow copy volume limit for any volume and there is no preallocate disk space in B2D storage, Before one month the backup job completed without no error ( that time also we are not set shadow copy limit ) .

2. System writer in stable only but when B2D job runs, the system writer is in failed state(Timed out ), below i copied current status of vss writer