When veritas backup exec tm for windows servers sees a tape. Compare insightsquared sales analytics to alternative sales forecasting software. Backup exec fails with a failure occurred querying the writer status i have had this situation for a couple of weeks now on my servers, both physical and. Use the manufacturers scsi setup program to disable wide negotiation on the. Symantec backup exec system recovery 2010 users guide thesoftwaredescribedinthisbookisfurnishedunderalicenseagreementandmaybeused only in accordance with the terms. Failure occurred querying the writer status 11 posts. I too tried many fixes through backup exec, but none worked because it wasnt an issue with the software, but the settings on the hardware itself. Dell 1850 server using w2k2003, spectra logic t50 and backup exec 10d adaptec 39160 scsi card with wide negotaion enabled and enable disconnect set support. Event log errors a suggestion would be to uninstall the current veritas tape drivers by running tapeinst. Give the administrators group and system full control. How to migrate move backup exec from one system to another.
How to troubleshoot backup exec deduplication storage folder. The following events are noticed in the windows event logs. Backup exec device and media service fails to start with. The upgrade can be completed by clicking ignore but backup exec services fail to start. About errorhandling rules for failed or canceled jobs. Alternatively, for customers who are using backup exec 12. Windows iscsi san, linux iscsi san, mac os x iscsi san and virtual native san. You can try to get the tape out by powering down the drive if its internal this means powering down the server or library that its located in, press and hold the eject button and then power up the drive. When veritas backup exec tm for windows servers sees a tape device attached to a scsi or to an integrated drive electronics ide controller, it records specific information in a log called adamm. Guide to downloading the latest version of symantec backup exec. We are currently trying to diagnose an ongoing issue with a clients backup in backup exec.
After that i could execute the hp storageworks library and tape tools to check if the problem is in the device or in backup exec drivers. We are using a hp ultrium 3scsi external lto ultrium 920 400800 gb connected to a hp lsi adapter ultra320. A sqlplus script in backup exec allows a default timeout of 10 minutes to handle the changing database state. Aug 02, 2012 hello, i have an issue with symantec backup exec 12. Data error cyclic redundancy check is reported in the backup exec job log. They have an lto4 drive that they are backing up to. As a result, backup exec 15 has a maturity, ease of use and feature set that few other products can equal. Overkill for sure, but when i again have a full current backup i will try reinstalling some of the software to find the cause. Instructions for moving backup exec tm 11d or above to another computer system which has the same version installed. Installing backup exec using the command line silent mode.
Backup exec upgrade to version be 20 involves dedupe storage. Error backup virtual machines using backup exec vmware. V795734434028 optimized duplication fails with read. The backup is over six tapes, all tapes are present and show up in the autoloader tape drive. Item description hardware the speed of the disk controller and hardware errors caused by the disk drive, the tape drive, the disk controller, the scsi bus, or the improper cablingtermination can slow performance. How to migrate move backup exec from one system to another with the same version of be, windows and same or different computer names.
Tape renewal from backup exec im trying to implement veeam 8 patch 3 as my primary backup solution for tape backup after using backup exec for years. I have had the drives replaced in the library, changed the scsi cables and checked that i am using the correct ones. Backup exec 2014 jobs failing on hp proliant dl360 g6 with. Powervault 122t lto, poweredge 2650, windows 2000, backup. Once the tape was replaced, the problem disappeared. It is recommended that a complete backup of the backup exec database be made prior to making any backup exec database changes. We have 2 x hp lto ultirum 5 drives attached to a dl385p g8 server via 2 separate h222 sas cards.
Symantec backup exec for windows servers version 12. How to find out why a backup exec backup or restore job has failed. Server is running windows 2008 r2 and the latest proliant service pack from sep 20. How to improve backup execs performance symantec backup exec. Start off by checking the system logs in the event viewer and the adamm. When im doing backup of virtual machines using backup exec its present the follow errors.
Sep 14, 2010 i too tried many fixes through backup exec, but none worked because it wasnt an issue with the software, but the settings on the hardware itself. Backup exec 20 uses dedupe version 10 and is even better with respect to the older dedupe version 7 which comes with backup exec 2014, 15, 16. Hi, we have a dl380g5 installed with a sbs 2003 sp2. Turns out, the phantom device missing 1 was occuring due to having the library setup for two tape drives, while the system only had one tape drive physically installed inside. Hp msl4048 tape library failure data backup spiceworks. Jan 06, 2011 same three writers fail during the backup after the reboot. The issue is seen if managed backup exec server feature is selected during an upgrade to be 20. Backup exec fails with a failure occurred querying the writer. I get a failed backup every time i backu a shadow copy component, sytem state andor exchange db on a local or remote server. Adamm mover error unload rewind failure is not an option. Mmorse did a good write up on these variables in the forum.
We have connected it to a p800 controller inside of a hp dl360 g6. To find this information, click the backup exec button, select. I had a number of veritas related errors in the event log. Dell 1850 server using w2k2003, spectra logic t50 and backup exec 10d adaptec 39160 scsi card with wide negotaion enabled and enable disconnect set to no sync rate is at 40mb. Backupexec failing after 35 minutes with error code e00084f4. Ok, going to order a separate single channel scsi controller and stick the tape drive on that. Trying a catalog job would fail with a zero byte count after 15 minutes with the error. Backup exec fails with a failure occurred querying the writer status all are server 2012r2 and all are running be 2014. This process takes longer, but in my case, was successful. Backup exec fail every time i backup shadow copy, system states or exchange hi. The next night, the same thing happened 9pm failed, 1am worked. The backup software is symantec backupexec 10d for windows servers the tape unit is a hpfreecom lto3 lto920es external the scsi card on the server is an adaptec 39160.
Backup exec 2012 sp3 is installed and was running fine, howev. The partition where the netbackup processes write temporary files. The timeout for database state change is named sqlplustimeout. This symantec product may contain third party software for which symantec is required to provide. The server running the backup is running windows server 2003 sp2. Using the backup exec utility to do the backups write errors were detected. Delete the tape drive in backup exec right click again, need to disable first this must be done in backup exec. Backup to dltvs160 hardware failure i have a pv110tdltvs160 tape drive, connected to an adaptec 391603960d ultra 160 scsi card, running in a dell 600sc, with sbs 2003. This is because the media server was installed with casomms option and later it was not removed from casomms completely.
Also forget about backup exec for a minute and see if you can download some hp tape tools and just be confident that the library is working so you know if youre faced with a hardware or software problem. Backup exec 20 agents and options articles and howtos. Backup exec database maintenance is failing because the. According to a support forum, this message was recorded on a system using an ibm tape drive. Exec those prior to backup exec 2010 r3 must be uninstalled before installing backup exec 16. Backup exec fails with a failure occurred querying the.
How to migrate move backup exec 2014 from one computer. Hello everyone, recently, we purchased a hp msl2024 ultrium 6520 single drive lto6 tape library. Solved backup exec backing up to removable hard drives. Backup exec 2014 jobs failing on hp proliant dl360 g6. Log file, and what various errors mean within the log. I am thinking about placing the tapestreamer in a testserver and install backup exec on it to check if the problem is hardware or softwarerelated. Jul 04, 2014 problem downloaded and installed backup exec 2014 onto the media server and then went to one of our servers to update the agent for windows. An example of a version and revision number is version 14. More errors data recovery general discussion tektips. Issues with p800 and brand new hp msl2024 ultrium 6520 lto. Why the occaisonal event id 11 in the system log that seemed to support the claim.
We have been using ntbackup to write to this drive since approx. I recently found that my script that pushes jobs to bu with. Backup to dltvs160 hardware failure dell community. Something i am struggling with is a dual move from backup exec 2012 to be 2014 as well as an upgrade to server 2012 from server 2008. Ok, fine, sometimes weird things happen especially in this place and the later job ran fine. Sometimes the value of previousdjmprimaryserver and the value of database server name is the same as seen in the event id description above. Although new this year, the development cycle for the software goes back to the early 1990s. Guide to downloading the latest version of symantec backup exec 11. All device firmare is updated to the latest version. Creating media vault rules to move media to and from media.
Power vault 110t sdlt 320 w hardware compression enabled. It shows errors wich i think may be related to scsi and these errors cause the backup to fail due to a timeout according to backup exec. Retryable error, or 8 error, depending on when i catch it. Backup exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market. We keep getting device errors in the application log when we run backup jobs using harware encryption. Backup exec 2014 or 15 or 16 uses deduplication version 7 and run a lot faster and smoother as compared to previous older be versions.
Hp lto ultrium3 drive with a 1x8 g2 autoloader x86based connected to the scsi adapter windows 2003 r2 server installed with the last drivers of the tape installed. Kernsafe support team iscsi san, iscsi target, iscsi initiator and related technological support. V795734434028 optimized duplication fails with read write errors. Sas tape library is hooked up to the second port on. Everything work fine but i find that the tape that i have used before with be are not usable by veeam. Adamm mover error and low compression ratio, relat. The backup exec agent for vmware and hyperv provides comprehensive protection of vmware and hyperv virtual machines through integration with microsoft volume shadow copy service vss and vmware vstorage apis for data protection vadp. Technical support symantec technical support maintains support centers globally. Backup exec e00084f4 i am having a frustrating problem with backupexec 12. Hp ml350 server with a scsi adapter connected via pci. An explanation of soft and hard write errors visible on the statistics tab of tape drive within backup exec storage view.
The only thing left was backup exec itself and my long history with the software. Tape stuck on an sdlt drive if the 3 leds start blinking you most likely have a dropped leader, broken tape or stuck tape. Also the article referred to above is applicable to windows 2003 so it will likely do me know good to follow it either. Yet, why the very specific adamm errors pointing to hardware. Write down the backup exec version and revision number. Please follow these directions if you have and just skipped over saying so, i apologize. July 2006, but the backups have been failing consistently in the past two weeks. Install a device driver for the specified device using the tapeinst. Backup exec tapes refuse to catalog pc load letter. Troubleshooting the oracle agent symantec backup exec. Powervault 122t lto, poweredge 2650, windows 2000, backup exec 9. Select the option to uninstall veritas tape drivers. All of our backup exec backups are set up to use encryption with software compression.
If the tape drive used for the job has multiple readwrite errors. The optimized duplication fails randomly with read write error. But to install server 2003 and all software on a server will take some time, so quicker solutions would be appreciated. Mar 28, 2019 backup exec has been around in one form or another since the early 1990s and has a reputation as one of the more reliable backup products on the market. Doing the same in windows device manager and rebooting did not fix the problem. Also, you should install all the latest sps and hotfixes for be. The firmware, drivers, os and backup exec are all patched. I have a pv 120t, dds 4 autoloader installed on a dell pe 2500 with windows 2000 sp2. Before the tape was stuck with the solid green lcd. Backup jobs fail with the error message shown above. I do have an interest in changing over to a new backup system and have done a good portion of the research already i discussed two of the solutions in a previous post. Technical supports primary role is to respond to specific queries about product features. For oracle real application cluster rac, a srvctl script is used.
The identifier and type of the device is reported as part of the warning message. Improve error reporting and docs regarding collection backup feature. This log file contains very useful information in configuring robotic libraries and tape drives for backup operations within backup exec. Backup exec hardware error solutions experts exchange. Why would the log dump sent to tandberg data come out clean.
Developing a real backup plan with symantecs backup exec 15. Only an email address is required for returning users. To perform a backup of the bedb stop the sql server service use for backup exec instance and copy the data folder use by backup exec default location is c. If permanent license key is not entered during installation, software will be on 60 days evaluation. Backup exec 2014 jobs failing on hp proliant dl360 g6 with an. Write down the installed backup exec options, their serial numbers, and the. Another backup software is running during the backup exec backups and has control.
I do not believe the original installation of the hp wbem providers caused the issue, i have a feeling a subsequent windows update, backup exec update, other module update, or an update to the hp software may have caused the issue to occur at a later time than original install. I noticed in your comments above that you never say you stopped the backup exec services. When they backup it fills the tape which has a capacity of 800 gb, even though it is only 427 gb of data. More errors more errors edsmikem isitmanagement op aug 03 08. V795734434028 a backup storage readwrite error has occurred. I just installed a server with backup exec, and fought this problem for some days before finding the above. Backup failed data recovery general discussion tektips. Could not write value adammlocal to key \software\symantec\backup exec for windows\backup exec\server. Symantec backup exec 15 agent manual installation on windows server 2003 r2 fails with following error. I recently wasted a fair amount of time when i needed to restore some files which were older than the 60 days of catalog retention on the backup exec media server. Backup exec 15 is the latest version of symantecs versatile backup and recovery software.