Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Backup Exec 2012 error 0001:2 and 0001:1

Created: 05 Oct 2012 | 4 comments

 

An unknown error occurred on device "Deduplication disk storage 0001:2".
V-79-57344-34028 - A backup storage read/write error has occurred.

An unknown error occurred on device "Deduplication disk storage 0001:1". V-79-57344-34028 - A backup storage read/write error has occurred.  

 

 

Enviorment:
BackupExec 2012 sp1, hotfixes installed (198571, 180964, 194470).
Backup server 2008 R2, remote server that's failing 2003.
Deduplication storage disk.
 
I started recieving the above error 0001:2 on one my servers. I did have succesful backups before the error on this server. I also have 5 other servers working without issue on the same dedup storage disk.
 
I Deleted all the backup sets for the failing server, ran an inventory, delted and recreated the backup job. Now I recieve the second error 0001:1 when attemtping a backup. The job fails within 1 minute and I unable to get any kind of backup on this server.
 
I have seen the below document, however I do not have any kind of encryption so it does not apply. All other docs I've found apply to tape.
http://www.symantec.com/business/support/index?page=content&id=TECH130444&actp=search&viewlocale=en_US&searchid=1349447528828
 
Thank you.
 
 

 

 

 

Comments 4 CommentsJump to latest comment

Donald Eady's picture

Take a look at this technote and please let me know if it applies.. 

 

http://www.symantec.com/docs/TECH129640

 

I hope this posting was helpful

  

Colin Weaver's picture

Just to explain the 0001:2 and 0001:1 actuall refer to how many concurrent writes your DeDuplication folder allows, as each concurrent write is allocated a virtual drive inside the Dedup folder and these virtual drives are given designators such as 0001:1 and 0001:2. The actual error is the  V-79-57344-34028 - A backup storage read/write error has occurred which is basically statring there hjas been a problem accessing the DeDuplication Store folder that has afgfecetd both virtual drives.

 

I would suggest that if you cannot find a Tech Article that discusses the storage error against DeDup and helps that you should log a formal support case as issues within the DeDuplication system can be tricky to resolve.