khudson

Looking for any information on the Qualstar Q24 LTO-8 Tape Library. Considering a purchase of this system, but was wondering if anyone had real world experience with this tape library. I'm looking for Pros & Cons concerning the hardware reliability and ease of operation. Any info, good or bad will be much appreciated. Thanks.

Anyone currently using a QualStar Q24 Tape Library for backups? Looking for some real world Pros & Cons. Maybe upgrading our old HP Ultrium3 tape drive to a QualStar Q24 2U 24-slot LTO-8 system. It is not currently listed in the Hardware Compatibility List, but have been assured by QualStar and Retrospect that it is compatible. Any information will be much appreciated. Thanks.

Hi David, Thanks for all of your help with this. Seems like everyone used the Exabyte devices with MACs. I did find and print out the Exabyte 110L manual. I have not yet tried to edit the "retro.ini" file.

The Exabyte tape library / drive that I have is an Exabyte 110L Autoloader. I'll check the Advanced Search, see what I can find. Thanks.

Hi David, No problem. Yes, we have the Advanced Tape Support Add-On. It worked great on the old 2008 server, but I can not get it to recognize the Exabyte Tape Library. I have tried changing the SCSI ID's, but that made a bad situation worse. Then the drive disappeared altogether. Set the ID's back to original, rebooted and the drive was recognized again, but still not the library (Tapes).

I have two tape library / drives connected via SCSI. After moving them from our Windows 2008 server to Windows 2012 server, one of the tape library / drives are not being seen by Retrospect V11.5 under Devices. They both were available on the old 2008r2 box. The "drive" is listed, but not the "library", state "Empty". I have check the SCSI ID's, all are correctly set. Anyone have an idea as to why it is not seeing the library, but does recognize the drive? Thanks in advance.

So it seems the problem was more the file server being backed up rather than the server hosting the Retrospect software. It seems the amount of free hard drive space on the file server drive was the cause of the -625 memory error. Total size of the home directory was 500+ GB. Free space on the drive was usually around 20-30GB. It would fail on scanning the drive the majority of the time. When I was able to free up to 40GB, it ran flawlessly. No changes were made to the Backup server. Not sure if this will solve the problem for anyone else having this issue, but it worked for my situation. I tested this multiple times, and it worked every time. As long as the client had more than 40+GB free (may have worked with less, but that is what I used for a target size), it would execute the script as it should. BTW.... I have since installed a new 64-bit Windows 2012 server!

I am receiving this error when I am backing up our home directory to Tape. Running 11.5 for windows. Server is an HP DL350 Gen5, Windows Server 2008 Standard, 4GB RAM, 1TB drive. It happens at random intervals. Sometimes it will backup the directory with no problems, other times it will not backup at all, failing with the -625 error at the scanning stage. Other times it will error out in the middle of the backup run. I have used the resource monitor and physically watched the backup and the used memory never gets about 50%. I have increased the page file size, not much change. The OS is a 32-bit version and will only recognize the 4GB I have installed. Is it possible that it trying to use cache memory and running out? I'm chasing this around and it did not happen with the older version (7.7)that we were running on this same server. Any ideas? (I'm already pushing for a new server with 64-bit OS and lots of RAM). Thanks.

Still no concrete answer to this? I get this error message every time I run a script on my Home folders with a new tape backup set. After the first run on the new set, I no longer get this message.

I am having this same problem. I get the " necoIncoming: empty stream packet, tid 32" error, causing the script to run for hours longer than normal. Has anyone efffectively solved this problem? I'm using Retrospect 7.7.620 on Windows Server 2008 Standard.