Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About WRShaw

  • Rank
    Occasional Forum Poster
  1. We're up and running, but I have lots of manual work to do before we are whole. Thanks for your assistance! Bill
  2. Here is the log in case it helps you figure out what the problem is, I need to restore the last working config75.dat and get my backups running again. Thanks, Bill
  3. I tried that and it didn't work, so is there something else I can try? Thanks, Bill Details: Clear all devices, logoff. Retrospect hangs nothing happens. Logoff again and restart Retrospect - same condition as before (no devices, Retrospect will not completely shutdown). Second attempt: On restart wait 5 minutes - Retrospect will come up, but the condition hasn't changed.
  4. Removing the Config75 files gave me back my drives, but of course lost all my scripts, etc... How do I recover from this? Do you have magic tool to fix the config75 file? thanks, Bill
  5. The first drive is the CD-rom. In my attempts to diagnose/correct. I disabled it, nothing changed and then attempted to re-enable it. One other cute thing is happening. Retrospect is not stopping. You can exit the application, but it remains in task manager. An attempt to relaunch gives you the running in another session. the only way to clear is to logoff and back on between attempts.
  6. Running Retrospect MSVP 7.5.508 & Everything has been running well for over one month, and then this weekend for no explaination you see the situation now depicted in the PDF. The Environment sees the devices, but the status tab doesn't. I have rebooted including POR every device and cannot get this situation to change, including removing,disabling the devices which do appear in the Windows Device Manager. any help would be appreciated. thanks, Bill Windows 2003 on HP DL380... Server has been in place for one year, we have been using Retrospect since 2003.
  7. WRShaw

    Loosing License/Server association

    I think we have the association, but I am interested in why. Removal of the proactive backup appears to have stopped the loosing the license issue. Here is the history on this problem with a focus on Proactive backup (not normally used for SQL backups). In the beginning our SQL databases were backed up daily to a NAS device and then finally to tape. We have discovered an issue not related to Retrospect that prompted us for more frequent backups directly to tape; once per 4 hours to capture start, midday and end of day to reduce our exposure. These backups do not replace but rather augment our SQL backup strategy. Proactive backup seemed to be the easiest way to accomplish this. We started having random unlicensing issues but didn't see the relationship. Then we added two SQL servers to this strategy and saw them occur more frequently (once every one or two weeks). To reduce our exposure of missing a backup, we increased the frequency of the proactive solution. Now our failures came at a more rapid pace, less than a week to fail. Now we start running deep traces with Dantz support and increase frequency to 1 per hour (per database) and we couldn't make it through 24 hours without failure. Now that we have stopped the Proactive backup, all is well... Thoughts anyone?
  8. WRShaw

    Loosing License/Server association

    The problem is reoccuring on the same two servers, but there is a potential relationship that I have found. I have now gone over 24 hours without loosing a license and the only significant change made was to remove a SQL backup out of our proactive backup and created a scheduled task. This relationship makes no sense to me, but if we can go another day or two... Thanks, Bill
  9. WRShaw

    Loosing License/Server association

    Hi and thanks for the responses, I'll try to answer both sets of questions. 1). The servers are 7.0.107. 5 of the 6 are SQL 2000 SP3 and one is SQL 7. The problem servers are our biggest 2K servers and don't know if there is any relationship there. 2)I input the license codes in the same order as they were originally, but they were applied in a different order than they were originally. We have had several incidents of one or two servers becoming unlicensed but I haven't had the ability to narrow it down, except to say that it is related to backup activity. We ran no backups using Retrospect for 48 hours (weekend) and didn't loose a license. We have only noticed the unlicensing to occur after one or more backups have run. I'll add more when I have something and I will check back here more often. Thanks, Bill
  10. WRShaw

    Loosing License/Server association

    Update... Still having problem even after I dropped all associations (release license from server) and then reapplied.
  11. We have Retrospect MSVP 7.0.326 with with 6 (1 + 5 addtional) SQL agents installed. We are having a problem with two servers loosing their association with the license. When you view properties of the client (server) you may see the SQL container but it is now unlicensed and it will ask you if you want to use the available license... When this occurs the license manager window will state you have 4 used and 2 available. The tempo of this problem is increasing, it never occurred with 4 agents, we seem to recall it happening with 5 agents installed but with 6 installed it is now happening almost daily. It also appears to be the same two servers. The order in which our servers have been added to the system is as follows: SHISSRV4 - NT4 SQL 7 (OK). OPPDB02 - W2K SQL2K SP3 (PROBLEM) OPPDB03 - W2K SQL2K SP3(PROBLEM) OPXIS00 - 2003 SQL2K SP3(NO PROBLEM) OPPDB04 - 2003 SQL2K SP3(NO PROBLEM) OPPDB05 - 2003 SQL2K SP3(NO PROBLEM) Any assistance would be appreciated. Thanks,
  12. Just moved tape, tape drive etc from the server platform where it fails back to Workstation where it had historically worked well. The process worked as expected, so the problem must be related to the platform. Obvious differences between platforms: Server vs. Workstation OS. Triple Xeon vs. uni-p4. Compaq SCSI Controller vs. Adaptec 29160 Three HP Nics vs. One Intel NIC. Any ideas? Bill
  13. I am also having this problem, didn't appear in the beta and may be machine specific. Here is why. I performed the beta testing on a Windows 2000 professional desktop and then downloaded the version 7 MS eval when it became available. Everything seemed to work as expected. When I moved it into my acceptance testing environment, the software was installed on a Compaq Server running Windows 2000 server and has exhibited the same behaviour that you have listed. In all cases we are running with downlevel clients 6.5.136, but why would that change when we went to the server. The other difference with the server is that it has multiple NIC cards installed and we are backing up through the secondary network interface. I too am very anxious, hopefully we will hear something soon.
  14. Just checking in, the problem continues has anybody have any ideas? Thanks, Bill
  15. I also think this would be a nice feature, but you cannot base it upon capacity. If your tape drive is streaming then it will take a known amount of time to use a tape and if it isn't streaming then that should be an item of concern. In the meantime, perhaps you can use this approach to your advantage. Determine how long it takes for your tape drive to go from BOT (begining of tape) to EOT (end of tape). That will be your change interval, by adding it to your current time you will have a good estimate of when you will need to return to change tapes. For example, when I used DAT tapes each one would take about 2 hours to write (regardless of the amount of data stored which varies by compression) so I knew that I would need to feed the machine some multiple of 2 hours later (depending on the number of available tape drives). An an example of loading a one tape drive system at 4:15pm would indicate that I'll be changing tapes a bit after 6:15pm. -Bill