cancel
Showing results for 
Search instead for 
Did you mean: 

Backups frozen @ Shadow Copy Components

Gordon_Smith
Level 3
I have taken over from a VAR that originally had all machines backing up in one job.

I have created a new job to backup our Terminal Server and it is almost identical in every way to the selections in the original job. I have not changed anything in the original job yet until I feel the new job is working correctly.

The first few nights I came in the next morning and the job was frozen @ Backup of "\\servername\Shadow?Copy?Components..." I tried cancelling the job, but it would just sit there in "cancel pending" state. To kill it I have to stop the BE services.

After a couple of nights of this, the backups started running smoothly and did so for over a week. Last night they started to freeze again. As I mentioned before, the original backup is still running without this issue.

We currently run BE v10.0 Rev. 5520

Thanks for your help.
6 REPLIES 6

priya_khire
Level 6
Hello,

Since when does the problem occur? It seems the b ackup of shadow copy components hangs in pending state. Does the backup of other drives on this server succeed?

When the issue occurs, check if you get any errors in the alerts tab in backup exec. Also look for errors in the Windows event logs.

Revert with details.

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.

Gordon_Smith
Level 3
It appears I created the job a few days before 1/25/2005. As I mentioned in my original post, the job immediately started having this problem, but cleared up after about 2-3 days.

Nothing appears in the Alerts tab when the job hangs.

The backup of C:\ is sucessful.

After stopping and restarting services, the last locked up backup actually gave me a failure notice. When opening the Job History, I get an "Unexpected end of input" error. Here is what exists of the log:



======================================================================
Job server: DC1
Job name: TS1 Backup
Job started: Friday, February 10, 2006 at 2:31:35 AM
Job type: Backup
Job Log: BEX_DC1_00606.xml
======================================================================

Drive and media mount requested: 2/10/2006 2:31:35 AM

Drive and media information from media mount: 2/10/2006 2:31:35 AM
Drive Name: HP 1
Media Label: LTO000002
Media GUID: {95ed0dda-497f-478a-9175-2b079a57c075}
Overwrite Protected Until: 12/30/9999 6:00:00 PM
Appendable Until: 12/30/9999 6:00:00 PM
Targeted Media Set Name: MED_MEDIA
======================================================================
Media operation - append.
Hardware compression enabled.
======================================================================
TS1AOFO: Started for resource: "\\TS1\C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
AOFO: Started for resource: "\\TS1\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
Network control connection is established between xxx.xxx.xxx.xxx:32881 <--> xxx.xxx.xxx.xxx:10000
Network data connection is established between xxx.xxx.xxx.xxx:32905 <--> xxx.xxx.xxx.xxx:3431
\\TS1\C:
Family Name: "Media created 2/10/2006 12:00:04 AM"
Backup of "\\TS1\C: "
Backup set #9 on storage media #1
Backup set description: "TS1 Backup"
Backup Type: Full - Back Up Files - Reset Archive Bit
Backup started on 2/10/2006 at 2:33:16 AM.
Backup completed on 2/10/2006 at 2:45:51 AM.
Backed up 36557 files in 4674 directories.
Processed 5,823,888,841 bytes in 12 minutes and 35 seconds.
Throughput rate: 441 MB/min
----------------------------------------------------------------------
Network control connection is established between xxx.xxx.xxx.xxx:32881 <--> xxx.xxx.xxx.xxx:10000
Network data connection is established between xxx.xxx.xxx.xxx:33168 <--> xxx.xxx.xxx.xxx:3529
\\TS1\Shadow?Copy?Components \\TS1\Shadow?Copy?Components
Family Name: "Media created 2/10/2006 12:00:04 AM"
Backup of "\\TS1\Shadow?Copy?Components \\TS1\Shadow?Copy?Components"
Backup set #10 on storage media #1
Backup set description: "TS1 Backup"
Backup Type: Full - Back Up Files - Reset Archive Bit
Backup started on 2/10/2006 at 2:45:53 AM.

Gordon_Smith
Level 3
They are currently hung up again. Current job status is Running.

Job Activity:
Job Activity for TS1 Backup


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


TS1 BackupJob name : TS1 Backup
Job log : BEX_DC1_00619.xml
Status : Running





Operation : Backup
Server name : TS1



Device name : HP 1




Source : \\TS1\Shadow?Copy?Components \\TS1\Shadow?Copy?Components
Destination : Media created 2/15/2006 12:00:02 AM
Current directory : System?State\System Files
Current file : System Files

StatisticsDirectories : 4,779
Files : 37,425
Skipped files : 0
Corrupt files : 0
Files in use : 0


Job rate : 17.0 MB/min
Bytes : 6,626,005,709 bytes
Start time : 2/15/2006 2:45 AM
Elapsed time : 6:06:13
Percent complete : N/A
Estimated total bytes : N/A
Estimated time remaining : N/A
NOTE: Estimates require enabling pre-scan


Any suggestions???

Asma_Tamboli
Level 6
Hello,


Could you please run the following test to check if any of the VSS writers are giving any errors:

http://support.veritas.com/docs/261993

- also please run a backup of the system state with the help of the ntbackup utility of Windows to isolate the issue. Please let us know the result of the backup run with NTbackup.



NOTE : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Gordon_Smith
Level 3
Results of VSS test:
C:\Documents and Settings\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-lin
(C) Copyright 2001 Microsoft Corp.

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {be1fbe79-6d3b-4ac5-9a9b-4eab63a71d34}
State: Stable
Last error: No error

Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {19a6957c-094d-4c39-a0ba-c78b0bad6b08}
State: Stable
Last error: No error

Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29}
Writer Instance Id: {65ebd337-3f81-41c3-bd89-fee1ea69a2dd}
State: Stable
Last error: No error

Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
Writer Instance Id: {fd9d5775-2ad9-4a9f-a498-4a0311ea95e2}
State: Stable
Last error: No error

Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {381dfa78-a5d1-4e60-a9da-41fd879440c8}
State: Stable
Last error: No error

Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {3bb41229-ea17-48af-8ebd-d441ef755565}
State: Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {af6d6f44-51af-43d1-b95e-409719c114c6}
State: Stable
Last error: No error

Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741}
Writer Instance Id: {53835cd2-5366-4dab-88de-a5d263b21cbf}
State: Stable
Last error: No error

Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {461636bf-6880-420e-b628-98f8ec823364}
State: Stable
Last error: No error

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {2089bded-3960-4a64-99e5-ea704a0756da}
State: Stable
Last error: No error

Writer name: 'TermServLicensing'
Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
Writer Instance Id: {cd59ea96-cbac-40c1-8fa4-7d471f20b930}
State: Stable
Last error: No error

Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
Writer Instance Id: {59501338-8673-4f00-a58d-b95aebe5eea0}
State: Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {113f5999-571f-4ca1-adce-ad3e97604050}
State: Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ec72e7a-f81e-4472-ac86-15f79ae4969d}
State: Stable
Last error: No error


System State backup via NTBACKUP worked correctly.

Job is currently hung up again this morning.

Mark_Hoffman
Level 2
What was the outcome of this thread? I am having the same problem.

I don't see a resolution here.

Mark Hoffman