Jump to content


  • Posts

  • Joined

  • Last visited

johnxsmith's Achievements


Newbie (1/14)



  1. I frequently encounter Error -102 (trouble communicating) when appending to a 35GB DLT tape after writing approximately 30GB during the initial backup. I found an old forum subject which deals with the same message at http://forums.dantz.com/ubbthreads/showflat.php?Cat=&Board=professional&Number=19627&Forum=professional&Words=-102&Match=Entire%20Phrase&Searchpage=0&Limit=100&Old=allposts&Main=17597&Search=true#Post19627. It contains some obvious boilerplate about how to handle the issue, so I'll describe the problem by referencing items discussed by the boilerplate. 1) The tape drive heads have been cleaned. The failure has occurred before and after the cleaning. 2) The SCSI bus contains only one device, an external tape drive. 3) Originally, ASPI was not installed correctly according to ASPICHK, so I ran ASPIINST.exe. A rerun of ASPICHK confirmed that ASPI was then installed correctly. The problem still occurs. 4) The failure occurs whether or not NT SCSI Passthrough is enabled. 5) I'm running Windows XP. The manufacturer (Adaptect) does not have any Windows XP drivers for the card, so I can only assume that the drivers which come with Windows XP are adequate and current. When I run Windows Update, it does not recommend any SCSI driver updates. 6) That's impractical 7) Believe it or not, but I have had this problem with three different tape drives. Because of this message, I had assumed that the problem "must" be hardware. Now I think otherwise. Here are some more pieces of information: 8) The failure has occurred when using several different tapes. 9) In an attempt to resolve any SCSI voodoo issues, I have tried different cables and cable adapters. That didn't make a difference. 10) Sometimes, I can append once or twice to a tape before the problem occurs. Once it begins, it seems to be persistent no matter what I do. 11) I have tried other backup software, and it has yet to encounter an analogous problem. Of course, there is no way of knowing if it encoutered the same situation with the tape drive. I did find it strange to see that it can take nearly three hours to find the end of the tape. Retrospect does not seem willing to wait that long. Preferences + Media + Request specifies a "Media request timeout" value of (never).
  2. I have several backup scripts which are scheduled to run at 3:00 AM. After installing the Driver Update 3.5 to go from version to they no longer run on schedule. If I launch Retrospect manually, they start immediately.
  3. I changed the properties of the client's NIC to be 100Mbps/Full duplex, but Retrospect was as slow as it was before. I then changed it to100Mbps/Half duplex. Retrospect was a little faster but still way too slow. I then changed it to10Mbps/Full duplex. Retrospect was reasonably fast (about 4Mbps across the LAN) given its 10Mbps limitation. For now, this was fast enough to complete a backup in about two hours, but I'd still like to get a full 100Mbps. I suppose this is now my problem for sure, but I'd appreciate any suggestions you have about how to get the other 90Mbps.
  4. Wow! With a crossover cable, the backup flies at about 15-40Mbps as measured by a network speed tool I have. Retrospect reports the overall performance as 172MB/min. Configure > Clients reports the speed as 10909, 9524, 6667 and 5714 (changing every time I hit the Refresh button). Thinking that the problem could be the standard Ethernet cable, I tried another standard Ethernet cable, but the Retrospect backup was still dreadfully slow. So the problem isn't simply a bad cable. What next?
  5. Configure > Clients, Get Properties shows (on the General tab) a Speed of 21, 67, 53, 5, 12 or 34 K Bytes/sec. (It changes each time I do it. Those are the numbers I saw during several Refreshes.) On the Access tab, it shows the Protocol as TCP/IP. I'm not sure what you want me to say about TCP/IP transfers, but I can download files from the Internet at full cable modem speed, which for me is 1.5Mb/sec. I suppose I could connect the computers with a crossover cable for testing purposes, but I sure can't run that way in real life.
  6. I have the Windows version Retrospect Backup Desktop Edition 5.6.127 and a 5 client license. I have a 10/100 network with a Mac desktop, an old Windows 98 laptop and a brand new Windows XP laptop. Each client is running the latest client software (5.0.201 for the Mac) and (5.6 for Windows). Performance is fine for the Mac and the old Windows 98 laptop, but a backup of the new Windows XP laptop is so slow as to be impractical. If I'm reading the dialog box correctly, the estimated time to completion is over six days for less than 3GB of data. To make matters even worse, if I let the backup run for a while, it will fail with error -519. The problem is not raw network speed since Internet access works fine at cable modem speeds of 1.5Mbps and a Windows file transfer goes quickly at 20Mbps.
  7. I assume that there is no decent workaround. Is there any hope for an improvement in the future e.g. Mac OS X or Retrospect 5.x?
  8. I am running Retrospect Backup 5.6 Desktop on Windows XP with Retrospect Client 4.3 on a Mac running MacOS 9. Whenever I try to back up a file which is greater than 2GB, it fails with: MapMacError: unknown macintosh error -1,310". File "xxxxx": can't read, error -1002 (unknown Mac OS error)
  9. Welcome to the world of advertizing. The 20GB number is pretty optimistic. YMMV. It all depends upon how compressible your files are. In my experience, I get about 11.5GB on an NS20 tape. I would not expect Retrospect's software compression to be significantly better or worse than any hardware compression provided by the drive, so that isn't your answer. The 9.6GB figure is actually the same as 10GB. It just depends upon who's doing the counting. The hardware manufacturers define a GB as 1,000,000,000, but software typically defines it as 1024 * 1024 * 1024. I would suggest using Retrospect's selectors to specify that certain files do not need to be backed up regularly with the others.
  10. Every night I do a Normal backup to disk of all the important files on my system. If I continue to do this for several months, will I reach a point where the backup set contains so many snapshots that it becomes unwieldy? I am considering periodically copying my disk backup set to tape and then doing a Recycle backup of the disk backup set. Do you have any suggestions as to how often I might do this e.g. monthly, yearly, etc.?
  11. OK. That looks promising. Let's say that my input backup set has been written and updated several times over a period of several weeks so that the changed files on my hard drive have been backed up many times. Will all of those file versions be transferred to the output backup set, thereby making the output backup set exactly equivalent to the input backup set?
  12. I am considering switching from an NS-20 tape drive to a DLT tape drive and then selling the NS-20 drive. Is there a way that I can copy my existing NS-20 tapes to DLT tapes? If so, it is possible to copy several NS-20 tapes to a single DLT tape?
  • Create New...