11-03-2014 10:52 PM
Hi All,
i have some problem with Symantec backup exec 2012 installed in windows server 2012 and backing up virtual machines.
sometimes backup running full or incremental the results succes with exception. but today backup failed with error :
Backup- \\[Server_backup]\C:
Storage device "Deduplication Storage:4" reported an error on a request to read data from media.
Error reported:
No more data is on the tape.
V-79-57344-34029 - A hardware error occurred.
Storage device "Deduplication Storage:4" reported an error on a request to write data to media.
Error reported:
0x17
V-79-57344-34028 - A backup storage read/write error has occurred.
If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean the tape drive, and then try the job again. If the problem persists, try a different tape. You may also need to check for problems with cables, termination, or other hardware issues.
If the storage is disk based, check that the storage subsystem is functioning properly. Review any system logs or vendor specific logs associated with the storage to help determine the source of the problem. You may also want to check any vendor specific documentation for troubleshooting recommendations.
please help me,
thank you for kind attention and support.
regards,
ridho
Solved! Go to Solution.
11-04-2014 12:18 AM
i have some problem with Symantec backup exec 2012 installed in windows server 2012
BE 2012 doesn't support Win 2012 as a media server OS.
11-04-2014 12:43 AM
...you might just be lucky that it works intermittently. But if you're having issues then you need to move onto BE 2014 which does support Windows Server 2012 as a media server.
Thanks!
11-03-2014 11:00 PM
...please read below and see if this is relevant for your issue:
http://www.symantec.com/docs/TECH130444
Also, if you are duplicating off to tape, make sure that there are no hardware errors with your drive by running the manufacturer's utility.
Thanks!
11-03-2014 11:03 PM
11-04-2014 12:17 AM
how to check my dedup damage?
if dedup damage, why another job still running successful?
backup still failed for this job backup with virtual machines.
11-04-2014 12:18 AM
i have some problem with Symantec backup exec 2012 installed in windows server 2012
BE 2012 doesn't support Win 2012 as a media server OS.
11-04-2014 12:41 AM
if BE 2012 doesn't support Win 2012, another job still running successful.
because I have a 9 on the backup server with OS windows server 2012 as a media center. fifth successful backup server, another the backup job always with exceptions and failed with the error.
11-04-2014 12:43 AM
...you might just be lucky that it works intermittently. But if you're having issues then you need to move onto BE 2014 which does support Windows Server 2012 as a media server.
Thanks!
11-04-2014 12:49 AM
what is solution for my case? besides to the upgrades to Symantec be 2014.
11-04-2014 12:51 AM
you can see like this.
11-04-2014 12:52 AM
Well, you're on an unsupported OS...your only options would be:
1. Downgrade to a supported OS for BE 2012 which would be Windows Server 2008 R2;
2. Upgrade to BE 2014 which means no OS reinstall (and subsequent BE reinstall).
Thanks!
11-04-2014 12:53 AM
screenshot
11-04-2014 01:10 AM
11-04-2014 01:28 AM
I could not choose between the two solutions above. as interconnected.
Here we can not downgrade because there is a configuration that has been set up.
and also can not upgrade to sym BE 2014 due to several considerations.
any solution other than technical?
untuk BE 2012 for last idea :)
11-10-2014 02:38 AM
...choose between the 2 solutions as in not sure which 1 will work? If both worked, then split the solution.
That said, you only really have 2 options for what you need to do in order to be supported.
Thanks!
11-29-2014 10:07 AM
i had exact problem with Backup Exec 2014 SP1 on Windows 2012 R2 .
backup job for all servers is ok but just one windows server 2008 r2 with sql 2008 r2 is failing with :
V-79-57344-34028 - A backup storage read/write error has occurred. If the storage is tape based, this is usually caused by dirty read/write heads in the tape drive. Clean......
after 3 weeks of troubleshooting , problem disappeared.
on that server 2 sql instances (2008 R2 & 2012) was installed ,2008 R2 instance was in the recovery state , after excluding sql 2008 R2 instance and folder from backup job , job completed successfully.
11-29-2014 10:08 AM