My Tandberg LTO Drive isn't working with Veritas Backup Exec
My Tandberg drive wouldn't install with Veritas Backup Exec v9. I rolled back to version 8.6, and the installation went okay, but now my backups appear to fail everyday, even though the data restores properly. Plus my media keeps being renamed with all sorts of weird characters rather than the names I assign. Can you help?
A 6ya expert can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
The service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones). click here to download the app (for users in the US for now) and get all the help you need. Good luck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
We have had the same problems with HP drives and Veritas. In our case it was not the drive per se. While I am assuming that based on the date of your post that you have moved to another solution, however, I will provide for you what we did.
First shut all down, disconnect the tape drive from the scsi cable, then restart. Go into computer management and turn all your backup exec services from auto to manual. Now go to devices and do a rescan. Once this is done and you see no tape drive whatsoever in the devices shut down the server. Reconnect the scsi cable to the drive and restart.
Go back into computer management, back to devices and rescan for hardware changes. Do you see it? If so, good! Sometimes a re-seating of connectors will do that. On the other hand, it could also be a tape driver from Veritas that just doesn't work (my case), take the original driver cd that came with the unit and start that loading up. Can you see it now? Can you use windows backup to access the tape drive? Now go into services and start the services individually. Go into backup exec and see if you can read your tape. Go back to services and reset all services back to auto. If you ever have to reinstall/upgrade backup exec, think twice about using their drivers.
what drives are inside as these units can come in several configs. For all SCSI units the Adaptec 29320 is good for fiber the qlogic cards are my prefered cards.
Drivers are available from sun for the library and drives although you can sometimes use the standard windows drivers for many drives. (search for LTO as the tape drive manufacturer in win drivers for LTO) Although best to use sun drivers if at all possible.
Library comes up as a medium changer in device manager.
What backup software are you using? If Backup exec then the latest version already comes with their drivers built in
Unfortunately, the data types you described are already compressed.
Your hardware and software cannot compress it any further. In fact, compressing compressed files actually increases the file sizes. Don't worry, Backup Exec knows better than to compress compressed files so you can leave your settings in place.
The compressed capacity of a tape drive is a marketing ploy by the tape backup industry to make them more appealing. Yes, if your backup consisted entirely of uncompressed files you might get close to 75GB but never 80GB. You can only count on getting the uncompressed capacity of a tape.
Obviously, a higher capacity tape drive will resolve this problem.
You could also swtich to using two tapes but you would have to load the second tape when you arrive for work in the morning and your backup would have to finish during the business day.
Finally, if you have some data that does not change frequently you could seperate it from your active data. Backup the active data on your regular backup. Now you can backup the "archived" data manually with a separate backup job. Once backed up you only have to back it up again when new data is added to the archive.
The error is because the driver isn't loaded for the device. Look up how to add the device in symantec help. If windows recognizes it already then usually you can go to devices and add teh device from within symantec.
Same problem with Backup Exec 10d and Superloader 3 LTO-3.
This is not my first problem with this Superloader. I think it is garbage and will likely be in the garbage very soon. Very expensive garbage unfortunately.
The problem you described is not a driver problem. So long as you are using the Veritas drivers you should be good to go.
SCSI time-outs and disconnects are hardware problems.
Sometimes they can be resolved by changing the throughput settings on the SCSI controller connected to the drive. Controllers usually default to very high speeds because they are used for hard drives. Lowering the speeds to support the slower throughput of tape drives can sometimes help.
During the POST there should be a key combination you can press to access the setup for the controller and modify the throughput settings.
Aside from that you have to replace the SCSI controller or tape drive until you figure out which one is causing the problem. Maybe the SCSI card is not seated properly.