asked on
Backup Exec Backup failing consistantly saying 'e0008821 - Job was recovered as a result of Backup Exec RPC service starting. No user action is required.'
Hi Experts,
We have had a backup job that has (so far) run without too many problems, until a few days ago (with no system or network changes) it started alerting as failing. It fails every day with the following message;
e0008821 - Job was recovered as a result of Backup Exec RPC service starting. No user action is required. For additional information regarding this error refer to link V-79-57344-34849
The backup also seems to be freezing on a certain server, although nothing has changed on this server to cause any failures, However, when i do a restore from any of these 'failed' jobs, it goes through ok. Also the byte count provided by backup exec is at a level seen in previous sucessful backups.
I am running Veritas Backup Exec 11d (rev. 7170) on MS windows server 2003 SP2R2, with a Dell PV132T
any help would be greatly apreciated!!!
We have had a backup job that has (so far) run without too many problems, until a few days ago (with no system or network changes) it started alerting as failing. It fails every day with the following message;
e0008821 - Job was recovered as a result of Backup Exec RPC service starting. No user action is required. For additional information regarding this error refer to link V-79-57344-34849
The backup also seems to be freezing on a certain server, although nothing has changed on this server to cause any failures, However, when i do a restore from any of these 'failed' jobs, it goes through ok. Also the byte count provided by backup exec is at a level seen in previous sucessful backups.
I am running Veritas Backup Exec 11d (rev. 7170) on MS windows server 2003 SP2R2, with a Dell PV132T
any help would be greatly apreciated!!!
Storage Software
Last Comment
daveford123
When you open the job history, what does it say under Job completion status? Or is that where is says the error e0008821.
ASKER
The overal status is 'Failed', giving the reason as the Error above, under the Error Category of 'Job Errors'
Have you looked at this support doc?
http://seer.entsupport.symantec.com/docs/285613.htm
Might be driver issue with your Powervault. Under devices tab, does the powerfault show up correctly under stand-alone drives?
http://seer.entsupport.symantec.com/docs/285613.htm
Might be driver issue with your Powervault. Under devices tab, does the powerfault show up correctly under stand-alone drives?
ASKER
Hi,
I installed the update above last night, but to no avail this morning, backup has still frozen in its usual place with the above message.
I installed the update above last night, but to no avail this morning, backup has still frozen in its usual place with the above message.
Can you create a backup job and have it complete successfully?
How many servers are you backing up?
How many servers are you backing up?
i'm having same exact problem. running 11d with dell lto-3. this is third day in a row.
i'm having the same problem with 2 Win2k3 Proliant servers running 11d and LTO3 drives. was fine until a week ago and no changes that i know of. Backup's were running after server reboot but one has
failed again with the same error..
have found articles on Symantec's site too, but do not match my/ your situatuion.
did anyone find a fix?
failed again with the same error..
have found articles on Symantec's site too, but do not match my/ your situatuion.
did anyone find a fix?
I had this problem in ver.12 and found the drive that held the catalogs were fragmented. I ran a defrag (took some time) and the error went away. I ran the defrag on both the catalog drive and the installation drive as well.
ASKER CERTIFIED SOLUTION
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.