Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Full Backup of Backup Server 2012 itself

Created: 10 Jan 2013 • Updated: 29 Jan 2013 | 6 comments
This issue has been solved. See solution.

I want to have full backup of Backup Server 2012. This Backup Server is used for deduplication disk storage (Z:\) and disk-base storage (Y:\) for backup.

Then I create a Full Backup for Backup Server 2012 include all components of Backup Exec Server as below.

  • C:\
  • System State
  • Shadow Copy Component
  • SQL Server Instances (SQL Server express come with Backup Server 2012 installation)  

Except deduplication disk storage (Z:\) and disk-base storage (Y:\).

 

But the following error was found.

 

Job Completion Status 
Job ended: Thursday, January 10, 2013 at 1:38:31 PM
Completed status: Failed
Final error: 0xe000fed1 - A failure occurred querying the Writer status.
Final error category: Resource Errors
 
For additional information regarding this error refer to link V-79-57344-65233
 
Error
V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\BackupSRV.domain.com\Shadow?Copy?Components". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
 
Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status.
 
Check the Windows Event Viewer for details.
 
Writer Name: Backup Exec Deduplication Storage, Writer ID: {55F6D76D-8617-4FC8-81E9-DF0DE529B555}, Last error: The PDDE writer cannot be frozen at this time because queue processing is running.  Schedule backups of large dedup stores before 12:00PM or 12:00AM., State: Failed during freeze operation (9).
 
 
Backup Recommendations 
The following backup sets contain Microsoft SQL data. Symantec recommends that you install and use the Backup Exec Agent Applications and Databases to better manage your SQL data:
 
    \\BackupSRV.domain.com\C:
 
 
Also, I ran the command "vssadmin list writers". The output result is as below:
 
C:\Program Files\Symantec\Backup Exec>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line
(C) Copyright 2001-2005 Microsoft Corp.
 
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: {619a7886-7b80-465c-a65b-6b0130546033}
   State: [1] Stable
   Last error: No error
 
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {89e5a73a-cda1-4c7e-86c9-4565b8089f47}
   State: [7] Failed
   Last error: Timed out
 
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {a21295b2-f7b1-415d-9171-db6cc688f089}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Backup Exec Deduplication Storage Writer'
   Writer Id: {55f6d76d-8617-4fc8-81e9-df0de529b555}
   Writer Instance Id: {04e1b681-5826-4198-8dc5-940c41ea6bdc}
    State: [1] Stable
   Last error: No error
 
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {bfaac295-de3a-4ed8-8a44-63c437a14ec3}
   State: [1] Stable
   Last error: No error
 
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {91e6d8ac-c7de-40f0-83af-42ffbac4f9f6}
   State: [5] Stable
   Last error: No error
 
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {f246c69d-7c9d-4ed6-8349-498c59355311}
   State: [1] Stable
   Last error: No error
 
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {f0945bb8-3777-4ccf-8072-14247ab663a6}
   State: [1] Stable
   Last error: No error
 

I have same issues on several Backup Exec server 2012. How to solve this issue? How to do Full backup for backup exec server?

Comments 6 CommentsJump to latest comment

CraigV's picture

Hi,

 

Check and make sure you haven't perhaps selected the SQL database that BE uses. You would get that error if you did and didn't have the SQL agent installed.

BE by default creates bedb.bak (located in the Data folder) every morning @ 4AM. You can simply back this up if you don't have the SQL agent.

BE would skip any of the SQL flat files.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Gurvinder Rait's picture

Try the backup again after running queue processing manually for dedupe 

Writer Name: Backup Exec Deduplication Storage, Writer ID: {55F6D76D-8617-4FC8-81E9-DF0DE529B555}, Last error: The PDDE writer cannot be frozen at this time because queue processing is running.  Schedule backups of large dedup stores before 12:00PM or 12:00AM., State: Failed during freeze operation (9).

From command prompt go to BE Install Path and execute crcontrol.exe --processqueue twice

Then run crcontrol.exe --processqueueinfo

It would show Busy : Yes

                     Pending : Yes

Wait (this depends on how many tlogs are present in dedupe queue folder) until Busy and Pending both show NO

Rerun the Backup at this point and see how it goes

steven_man's picture

I try to re-run backup.  It take long time to complete. The used disk space of volume C is 30 GB but the backup size of active backup job is 400GB, still not completed yet. Then I cancel the backup job.

 

Then I found the size of Shadow Copy Component in Backup set found in Backup Exec 2012  is larger than the size of volume C:\

In my environment, the volume of C:\ is 70GB. But the size of Shadow Copy Component is 2.3 TB.

 

Why?

CraigV's picture

...do you need to backup the Shadow Copy Components?

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

steven_man's picture

Hi CraigV,

I want to recover whole system of Backup Exec Server in case of software error and hardware error. 

Therefore, I choose all components (include Shadow Copy Components) in the backup selection list?

Is it necessary to backup Shadow Copy Components in case of recover Backup Exec Server?

 

What is best practise to backup Backup Exec server itself? 

I also want to know why the size of Shadow Copy Components is larger than the size of system volume (C:\.

 

 

CraigV's picture

Not sure on the CSS, but to recover the BE server you'd backup the Data/Catalogs folders. The Data folder contains the bedb.bak file (ME-automated backup of the BE database at 4AM every morning), and the Catalogs folder contains all your catalogs.

If you can manage the OS installation and BE installation, this is the least amount of data you need to backup to get BE working again.

This assumes that you have a dedicated media server only.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

SOLUTION