Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1329
  • Last Modified:

Backup Exec 11d is ignoring Shadow Copy Components/DFSR

I am running Backup Exec 11.0 rev. 7170. Installed updates are Service Pack 5 and Hot Fix 70.

 

We have DFS Replication running on two machines, one of which is backed up by a third computer running Backup Exec. We had a full backup succeed, but since then, every backup skips over the Shadow Copy Components. There isn't an error, they just don't back up more than a few kilobytes per replicated folder. I am able to browse the replicated folders inside of shadow copy components in the selection list.

One thing that changed between the monthly that worked and now is I deleted the replication group, and recreated it. Perhaps something in Backup Exec's own database is confused? Even so, why do Full test backups I try to perform on portions of the Shadow Copy Compnents fail? Well, they say they complete, but they don't back up anything recoverable except DFSRPrivate.

Just to confirm: I am not selecting the replicated folders directly, I'm selecting their equivalents inside of Shadow Copy Components. vssadmin list writers and vssadmin list providers succeeds on the agent. Also on the agent, the event logs seem to confirm that it is shutting down replication and making a snapshot.

DFSR event id 1102 "The DFS Replication service has temporarily stopped replication because another application is performing a backup or restore operation. Replication will resume after the backup or restore operation has finished."

DFSR event id 6102 "The DFS Replication service has successfully registered the WMI provider."

And then one second later,

DFSR event ID 1104 "The DFS Replication service successfully restarted replication after a backup or restore operation."

If anyone has ideas about how to fix this, or even get, I'm very grateful.

 

Here is a portion of one of my test's log.

 
Set Detail Information - Backup \\xxxx\Shadow?Copy?Components

Set type               : Backup
Set status             : Completed
Set description        : Backup 00093

Resource name          : \\xxxx\Shadow?Copy?Components
Logon account          : System Logon Account
Encryption key         : No

Agent used                     : Yes
Advanced Open File Option used : Microsoft Volume Shadow Copy Service (VSS)
Image used                     : No

Byte count             : 92,304 bytes
Rate                   : 1.00 MB/Min

Files                  : 0
Directories            : 3
Skipped files          : 0
Corrupt files          : 0
Files in use           : 0

Start time             : Thursday, February 10, 2011 3:56:29 PM
End time               : Thursday, February 10, 2011 3:56:34 PM

Media used             : 000025L3

Thanks,
Jeff
0
kzsigo
Asked:
kzsigo
  • 2
1 Solution
 
Rodney BarnhardtServer AdministratorCommented:
This may have been caused by your changes. See if this technote relates to the changes you made: http://www.symantec.com/docs/TECH141181 


Or, you changes may have affected the selection list:
http://www.symantec.com/docs/TECH88068 


0
 
Rodney BarnhardtServer AdministratorCommented:
To see if there is some confusion in the job itself, you could try recreating it.
0
 
kzsigoAuthor Commented:
rbarnhardt, thanks for the link! The location of the staging folders was indeed the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now