Avatar of tamaneri
tamaneri
 asked on

symantec backup exec 2010 R2 / system state / shadow copy components

Hey guys,

Symantec Backup Exec 2010 R2 trying to back up the following:

1) Server 2008 32-bit
2) Server 2008 64-bit

When it starts backing up system state or shadow copy components from either server, the backup stops running, the byte count decreases to like 800mb/min and never increases/decreases more than that. The backup job never completes. Why could possibly be wrong here? Never seen this before.
Windows Server 2008Storage SoftwareSoftware

Avatar of undefined
Last Comment
Snibborg

8/22/2022 - Mon
Vegadog

It sounds like an error either on teh tapes , or with the device , Have you checked for teh latest drivers ???
Also i had this issue when i upgrade systems , and used Symantec Drivers as apposed to the Device drivers , try swop them around and see if it helps , also use a new tape !!
tamaneri

ASKER
Drivers are the Symantec drives, tapes are brand new :(
tamaneri

ASKER
This is a brand new install, brand new tape drive, brand new tapes :P
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Snibborg

Are you getting any information from the logs on this?  Uusally you will get something from there to work on.

Have you checked that te service account has sufficient permissions?  Try using the domain admin account to find out if it solves the problem, then keep adding permissions on the service account until it works.

Snibborg
Vegadog

When you install Symantec , there is an option for symantec drivers make sure the tick is off , and let windows detect and install the drivers , i had the same issue and then found out it was through the symantec installation ... I had it on a robotic library , the same issue , once i redid it it was fine , also with teh error try doing an update .. .
tamaneri

ASKER
Well it successfully backs up like 150GB+ until it reaches the system state or shadow copy components. The job never fails, obviously, so there aren't any logs I can check. I have to force it to stop. Every time I check what file it has stopped on it's either the show copy components or the system state.

If I check the log after i am forced to stop/restart the services, I get this:

Unexpected end of input.

94: D:\Program Files\Symantec\Backup Exec\Data\BEX_LERCHAD02_00020.xml





Job server: LERCHAD02
Job name: Full Backup
Job started: Monday, March 07, 2011 at 7:00:02 PM
Job type: Backup
Job Log: BEX_LERCHAD02_00020.xml


Drive and media mount requested: 3/7/2011 7:00:03 PM

Drive and media information from media mount: 3/7/2011 7:00:10 PM
Drive Name: IBM 0001
Media Label: LTO000005
Media GUID: {3a8452ae-8b7a-4895-9ab0-87774e49c7b7}
Overwrite Protected Until: 3/7/2011 8:00:10 PM
Appendable Until: 3/7/2011 8:00:10 PM
Targeted Media Set Name: Lerch Media

Media operation - Overwrite media.
Compression Type: Hardware [if available, otherwise none]
Encryption Type: None

LERCHAD02AOFO: Started for resource: "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).
C:
Family Name: "Media created 3/7/2011 7:00:03 PM"
Backup of "C:"
Backup set #1 on storage media #1
Backup set description: "Full Backup"
Backup Method: Full - Back Up Files - Reset Archive Bit
Backup started on 3/7/2011 at 7:00:19 PM.
Backup completed on 3/7/2011 at 7:03:19 PM.
Backed up 5828 files in 1809 directories.
Processed 2,583,389,631 bytes in  3 minutes and  0 seconds.
Throughput rate: 821 MB/min
Compression Type: Hardware
----------------------------------------------------------------------
AOFO: Started for resource: "D:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
D:
Family Name: "Media created 3/7/2011 7:00:03 PM"
Backup of "D:"
Backup set #2 on storage media #1
Backup set description: "Full Backup"
Backup Method: Full - Back Up Files - Reset Archive Bit
Backup started on 3/7/2011 at 7:03:25 PM.
Backup completed on 3/7/2011 at 9:10:24 PM.
Backed up 438481 files in 55612 directories.
Processed 133424554096 bytes in  2 hours,  6 minutes, and  59 seconds.
Throughput rate: 1002 MB/min
Compression Type: Hardware
----------------------------------------------------------------------
AOFO: Started for resource: "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).
Shadow?Copy?Components
Family Name: "Media created 3/7/2011 7:00:03 PM"
Backup of "Shadow?Copy?Components"
Backup set #3 on storage media #1
Backup set description: "Full Backup"
Backup Method: Full - Back Up Files - Reset Archive Bit
Backup started on 3/7/2011 at 9:10:29 PM.
Backup completed on 3/7/2011 at 9:10:38 PM.
Backed up 2 Shadow Copy Writers
Backed up 2 Shadow Copy Components
Processed 31,337,610 bytes in  9 seconds.
Throughput rate: 199 MB/min
Compression Type: Hardware
----------------------------------------------------------------------
AOFO: Started for resource: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The following volumes are dependent on resource: "C:" "D:" .
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
The snapshot provider used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).
System?State
Family Name: "Media created 3/7/2011 7:00:03 PM"
Backup of "System?State"
Backup set #4 on storage media #1
Backup set description: "Full Backup"
Backup Method: Full - Back Up Files - Reset Archive Bit
Backup started on 3/7/2011 at 9:10:51 PM.
The consistency check of the snapshot for the Microsoft Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) database and transaction logs ntds was successful.
VSS Snapshot warning. File d:\program files\arcwarewebserver2\cassiniservice.exe is not present on the snapshot.
Backup completed on 3/7/2011 at 9:20:44 PM.
Backed up 12 System State components
1 item was skipped.
Processed 7,096,759,588 bytes in  9 minutes and  53 seconds.
Throughput rate: 685 MB/min
Compression Type: Hardware
----------------------------------------------------------------------
LERCHTS01Network control connection is established between 192.168.1.250:62727 <--> 192.168.1.251:10000
Network data connection is established between    192.168.1.250:62730 <--> 192.168.1.251:2759
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
Snibborg

This looks more and more like a permissions issue to me.  BE is waiting to backup the system state but cannot because it does not have the rights.  As a result the only answer is to stop the backup.

Snibborg
Vegadog

Assign domain admin rights to the user account doing the backup or use a Enterprise admin account ...
tamaneri

ASKER
I'm using the domain\administrator account. The domain\administrator account has the following permissions groups:

administrators
domain admins
domain users
enterprise admins
group policy creator owners
organization management
schema admins
smsmse admins
users

Is it missing anything?
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
ASKER CERTIFIED SOLUTION
Snibborg

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.