Jump to content

algilson

Members
  • Content count

    17
  • Joined

  • Last visited

Community Reputation

0 Neutral

About algilson

  • Rank
    Occasional Forum Poster
  1. algilson

    Windows 2003 SP2

    Update: sorry, I should have added that I run Retrospect through a terminal session. I just realized that if I run Retrospect from the local machine, not through RDP, it runs fine. Not ideal, but it runs. - Al
  2. Over the weekend we installed Windows 2003 Service Pack 2 on our Retrospect Server host. + $[15]Retrospect$[16] version 7.5.370 Launched at 4/2/2007 7:23 AM + Driver Update and Hot Fix, version 7.5.10.104 Exit at 4/2/2007 7:24 AM Now every time I launch Retrospect it appears to render the screen as if it's loading, and the freezes. See: If I delete the config75.dat and .bak files, and launch Retrospect it will start properly. I then enter my access codes, and arrive at the proper Activity Monitor screen. If I quit Retrospect and relaunch, it freezes on launch again. Help? - Al
  3. Follow up post -- I removed the check box specified above: Script -> Options -> Windows Security -> "Back up file security information from servers" and now the script has skipped that file. Guess that's a "fix" for this.
  4. We're having the same problem. When I drill down on a file that definitely has not changed, but yet has been backed up 4 times, I get: Drill down on first backup: 001H1202.JPG Flags: Marked, Archive Type: File Size 1,905K total (1,941,818 bytes used) Location: Clipart\ December 2002\ Photos\ Created: Friday, September 26, 2003, 7:13:25 AM Modified: Friday, November 01, 2002, 10:15:40 AM Accessed: Friday, March 03, 2006, 5:43:18 AM Backed up: Sunday, April 02, 2006, 11:16:56 PM Drill down on second backup: 001H1202.JPG Flags: Marked, Archive Type: File Size 1,905K total (1,941,818 bytes used) Location: Clipart\ December 2002\ Photos\ Created: Friday, September 26, 2003, 7:13:25 AM Modified: Friday, November 01, 2002, 10:15:40 AM Accessed: Wednesday, April 05, 2006, 7:42:34 AM Backed up: Friday, April 21, 2006, 8:07:23 AM Drill down on third backup: 001H1202.JPG Flags: Marked Type: File Size 1,905K total (1,941,818 bytes used) Location: Clipart\ December 2002\ Photos\ Created: Friday, September 26, 2003, 7:13:25 AM Modified: Friday, November 01, 2002, 10:15:40 AM Accessed: Wednesday, April 05, 2006, 7:42:34 AM Backed up: Monday, April 24, 2006, 8:29:50 AM Drill down on fourth backup: 001H1202.JPG Flags: Marked, Archive Type: File Size 1,905K total (1,941,818 bytes used) Location: Clipart\ December 2002\ Photos\ Created: Friday, September 26, 2003, 7:13:25 AM Modified: Friday, November 01, 2002, 10:15:40 AM Accessed: Tuesday, June 20, 2006, 3:29:44 PM Backed up: Monday, June 26, 2006, 11:33:33 AM Really hoping I don't need to back this up AGAIN. Verification on the set is set to: Thorough verification. - Al
  5. Nate, We started a new backup set, and it has worked fine for 5 days. The other backup set throws the error still. We're going to start a new one for it as well. The backup sets must have been corrupted at some point -- as we did not start new backup sets when we rebuilt the server. We're going to run two new backup sets and see what happens. If you don't hear from me, then that's what it was. Thanks for your help! - Al
  6. Nate, Here is what we are using: User account is currently running in an admin account with: admin / domain admin / backup operator privileges. We did have it running in the RBU acct as the manual suggested, but have since moved to the admin acct to see if extra privileges help. The Windows drivers are disabled. No errors in MS event log around crash periods. Does any of that help? - Al
  7. Hi Nate, Here's the hardware specs: Acer Veriton 7200 P4 1.6 GHz desktop box, acting as a server in a small branch office (2 users). Sony SDX-500C AIT tape drive that we've had for a year or two. LSI Logic SCSI card running the tape drive. 1 EIDE Western Digital 120GB hard drive 1 GB of Ram. (just replaced with 2 brand new 512 MB sticks today with same results) Oh, and we replaced the CPU fan today too, as a safety measure. Still no luck. About 2 months ago this box existed as a Windows 2000 server and ran for several years without any problems. The HD then was an old scsi drive that finally decided it had rotated its platters enough and quit spinning. During the rebuild we installed a new drive, and installed a new Windows 2003 Server OS on that drive. All hardware otherwise stayed the same. During the install, we upgraded to Retrospect 7.0 and the SQL backup client as this system hosted a pretty important SQL db that we couldn't back up reliably from our main shop over the DSL connection to this shop. (I can't remember now, but i don't believe we could back up SQL with version 6.? that had been installed?) Needless to say, we haven't had much luck backing up with any version of 7, including the newest 7.0.326. I've watched the screen for hours in case I missed something, and there really isn't any particular time that this happens. Sometimes the backup will run 1/10th (rare) of the way through before crashing and throwing the assertion errors, other times it'll make it ~9/10th (more common) of the way through, other times it'll complete the backup successfully (rare). We've tried backing up just the server without the 2 clients, no luck. We've tried backing up the server without the SQL license and without the clients, no luck. We have not tried a new catalog set, as the set that we're currently using is a continuation of the previous set that was running on this machine. We have uninstalled Retrospect countless times, while blowing away the Retrospect folder and the Documents and Settings/... folder. (Can't remember specifically right now). We've rebooted the server, no luck. The error is always the same: elem.cpp-1000. And the event viewer always states after the crash that it may have been caused by a power failure. Hope that helps? - Al ============================= Note from Moderator : Assert logs don't provide troubleshooting info us mere mortals can use. Its all debug info for engineers - It has been removed it for clarity.
  8. Add us to this list as well. Same error. Windows 2003 SP1, SQL, Retrospect 7.0.326. - Al
  9. Me again. For reference to those who care: We upgraded from version 6.52 to version 7.0.249 Multi Server -- and we have since added two external USB DVD burners. When loading version 7.0.249, the error came back. If you install Retrospect driver update 7.0.1.103 (which I assumed was included in the original 7.0 installer as they have the same release date -- but, it's not) the problem will go away. Hope that helps someone. - Al
  10. At the beginning of January we've started backing up to DVD as well as our AIT autoloaders. My question: is there a way that I can make a duplicate of each DVD that Retrospect fills? I'd like to take one copy home and leave one copy here. My small disaster recovery plan. I've tried Nero 6.6.0.3 DVD copy, but the copy was considered unrecognized content. I have restored from the original discs and I know that they're good. Anyone? Server: 6.5.350 Multi-Server Value Package Driver update: 5.2.106 OS: Windows 2003 Server Drives: Sony AIT-SA300C and SA500C USB Drives: External 2 BenQ USB DVDs Thanks - Al
  11. Not to bring an old thread back to life again, but for reference for any other customers with this problem: RDU48 fixed the error on our server. Everything's ok now. - Al
  12. Thanks Nate, Here's the chain: Adaptec 2940 UW Pro, SDX-500C, SDX-300C, Active Terminator. All cables are 2' long or less. I disabled both drives in the hardware manager of Windows, and it was still crashing. After changing cables, and terminators I thought I found the problem with a pinched pin 2 on the 68-pin cable -- but that was a no go. So I went direct into the 500C. No problem. Direct into the 300C -- problem came back. So, I know now that it's the 300C. We just received it back from Sony after going in for repair (it was eating tapes, not ejecting, etc.) On the work order, it mentions that they updated the firmware. I checked, and it's now version L202. This 300C used to be our only drive and I know that it worked with Retrospect -- as it's been running for a couple years. The 500C was ordered to replace the 300C while it was in the shop. I updated the Retrospect drive to 4.7, from 4.6, but that didn't make a difference. We're going to run with just the 500C for the time being, but the 300C would sure be helpful to get running. - Al
  13. algilson

    Problems with 1000's of small files

    Just a suggestion, as we do this ourselves: I've set a schedule to winzip an entire directory of small text files into one zip file every night. Then when the backup runs, I've set it to not backup that text file directory, but it does backup the zip file which resides outside of the text file directory. Voila, no slow down. - Al
  14. Quote: algilson said: I'm now getting that error on my Win2003 Server as well. I'm running 6.5.336. Retrospect has encountered a serious error: Assertion failure at "provider.cpp-989" The backup hardware is TWO Sony AIT Autoloaders -- a SDX-300C (scsi ID 5 and active terminator) and a SDX-500C (scsi ID 4) connected to an Adaptec 2940UW. Both are connected to a Dual Xeon 2.4 Ghz Acer Altos G510 with 4 GB Ram. The machine also has an Adaptec 29160 with a 2 TB external Raid 5 chassis connected. Help? - Al Just to troubleshoot this a little more -- I turned off the SDX-300C, and left everything plugged in the way that it was. Retrospect now runs fine. But when I turn both drives back on it throws the error. - Al
  15. I'm now getting that error on my Win2003 Server as well. I'm running 6.5.336. Retrospect has encountered a serious error: Assertion failure at "provider.cpp-989" The backup hardware is TWO Sony AIT Autoloaders -- a SDX-300C (scsi ID 5 and active terminator) and a SDX-500C (scsi ID 4) connected to an Adaptec 2940UW. Both are connected to a Dual Xeon 2.4 Ghz Acer Altos G510 with 4 GB Ram. The machine also has an Adaptec 29160 with a 2 TB external Raid 5 chassis connected. Help? - Al
×