Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About KingMongo

  • Rank
    Occasional Forum Poster
  1. Hello, We have a Windows 2000 Server box which hosts a SQL Server. When the Server is up, naturally most of the tables and databases are in use, and cannot be backed up. We rely on the SQL Server application to manage live backups of the databases to another location, which Retrospect backs up. However, I'm wondering if this machine's backups take longer to complete because these files are failing to be backed up. It's obviously a waste of time for Retrospect to back up these folders, but how *much* of a waste of time? Is there a way to quantify this? Should I actually exclude the directory holding all of the databases from being backed up, and if so, would that appreciably increase the speed of my backups for this machine?
  2. Hi, this surely can't be that hard to answer? I've already looked in the KnowledgeBase and I'd like a definitive answer, rather than the half-hearted answers provided by the KB.
  3. I get this error on a Windows 2000 Server. This is kind of a bummer, since all I'm doing is closing Retrospect. Sometimes, Retrospect hangs on a job, or it hangs when ejecting a tape. So, I then try to close or shutdown the application. Retrospect then crashes, but leaves the retrospect.exe process running. I can't kill the retrospect.exe process, so it starts eating memory, until it blue-screens the server. This is pretty bad, is there any solution for this? Retrospect really works well for us, but the fact that it can bring down the server when it's having a problem is a serious concern.
  4. I am completely unable to do a full disk restore of my mac clients which are dual-boot OS9/OSX machines. The backup server runs OS9, as do all the clients. I've tried the restores to OS9, and to OSX, with failures in both cases. What must the environment be for this to succeed? Must both the Client AND the Server be OSX? Must the Retrospect Client be running *under* OSX and the restore done *to* OSX for this to work? Or, am I just doing something wrong and my setup *should* work? Please to advise. Thanks.
  5. Thanks for your reply! So, if you restore a Windows Server for which folder permissions were backed up (which happens by default), but individual *file* permissions were not, would the files inherit permissions from the folder in which they reside, or per whatever inheritance there was? What if inheritance was disabled? Would the files then revert to default (Everyone group has Full Control), or have no permissions applied at all? Thanks again.
  6. One of the more disapointing aspects of Retrospect 5.6's performance for us has been the length of time that it takes to back up permissions. On a large File Server, this results in extremely long backups, and extremeley low throughput, which I felt was injurious to the mechanism of our tape drives. Has there been any improvement to this, i.e., are there some specific, quantifiable reductions to the length of time it takes to backup up file & folder permissions?
  7. I'm curious about the new Advanced Tape Support in Retrospect 6.5, but would like some clarification. Can you run separate jobs simultaneously, one to drive A & one to drive B? Is this Advanced support literally for tapes only? Or, can you run simultaneous backup jobs to multiple physical/logical drives, too? If you have two jobs that you wish to run simultaneously (one of computer A, one of computer , but both will be writing to the same catalog (say, All Computers), can they do this, or will they queue up and only one job will be able to update the catalog at a time?
  8. Hello, I just updated our version of Retrospect Workgroup for Mac, from version 4.3 to version 5.0. The update appeared to be successful, my catalogs, script, and client connections are all intact. However, when I went back to review my logs, to my surprise I found that illegal characters were appearing at the beginning of my catalog and client names, as they appear in my Log. For example, I have a set called Mac Weekly B. It should appear in the Log as "Weekly B." It now appears as: $[*!s321,,14,+3]Mac Weekly B And I have a client called MacRetro, which now appears as: Copying $[*!s312,,14,+3]MacRetro Whatt the hell? It looks like this is where the icon representing the type of client or volume should be going--how in the heck did this get screwed up? And, what can be done to fix it? I'm assuming that this isn't going to destroy my backups, since they appear to be working normally, but this really makes a mess out of my reports...
  9. in reviewing my logs, I see that Retrospect spends an incredibly long time on "Idle/Loading/Preparing." There isn't any detail provided in the log about what *exactly* is going on during this period, so I have to ask--what's going on during this time? For example, I have a server which gets backed up; it has 4 logical drives. In total, the data transfer takes about 2 hours; however, the backup in total takes about 10 hours. why is this, and what can be done to make it stop? is this the result of teh compare taking a really long time? Is there anything that i can do to speed up this process? It's frustrating to see my backups taking so long on something that I can't explain.
  10. Hello, We're having a lot of problems with a Quantum SDLT drive. How come Dantz doesn't have a download page, where users can search for and download updated drivers for their devices? The last time I had problems with a drive, Dantz's support suggested this, that, then the other, and finally suggested that I try their new drivers. It seems really...*cutthroat* that I should have to purchase a technical support ticket in order to get an updated driver for your product.
  11. Hello, This is sort of an informal poll... I get widely varying transfer rates from my Retrospect clients, but there are some patterns emerging... 1. Windows 98 clients are stuck between 40-70MB/minute 2. Windows 2000 clients get between 100-150MB/minute 3. Windows XP clients get as much as 250-300MB/minutes (!) What is itthat most other Windows 2000, Retrospect Server 5.6 administrators are getting? And, what *should* we be getting? What can be done to improve the performance of 98 clients? Does overall communication speed improve with a server-side CPU/RAM upgrade, or is the bottleneck the client? Or, is it the network interface?
  12. Hi Melissa, It's a Quantum L500 tape library, with a DLT8000 drive. I can send a Scan command to the library, but the tapes don't actually move around. I have to add some MORE information at this point, however. One of the other techs (in my office) had talked to Retrospect support & ended up disabling the Drive & the Library in the Windows Device Manager. I felt that this was incorrect, and just re-enabled the Library in Windows; now, everything appears to be working correctly. Can you confirm whether this should be happening? Should both the Library & the Drive be disabled within Windows? Or, just the Drive? last question: if everything is working okay with SCSI passthrough, should I bother installing ASPI? Or, is ASPI preferrable?
  13. Thanks for your reply, Melissa! I'm using scripted jobs. I've got some more information about the problems that I've been having, as well. It appears to be that Retrospect simply can't communicate with my tape library; the drive, yes--but not the library. I get errors whenever I'm moving tapes to & from the library, and often, Retrospect will just crash. however, I can manually load & unload tapes from the library console. Any ideas?? Thanks in advance...
  14. Using a Quantum PowerStor L500 with Retrospect 5.6 on a Windows 2000 server. Having a problem where either Retrospect or the device is not "keeping track" of what tapes are in the magazine. For example, Tape 1 fills up, so Retrospect moves it back into the magazine and takes one of the blank tapes and starts writing to it, calling it Tape 2. However, Tape 1 does not show up in the magazine as Tape 1; it shows up as (erased)! If I do a scan on the magazine, then Tape 1 is found. BUT, until that tapes is *manually* fed into the drive, Retrospect will simply ask for that tape. Any ideas as to what's going on? I've never had to "instruct" the Retrospect software to "remember" what it has named a tape when it moves it from the drive into the library.