Jump to content

FuzzyJohn

Members
  • Content count

    156
  • Joined

  • Last visited

Everything posted by FuzzyJohn

  1. FuzzyJohn

    Check Media When Quitting with OnStream DI-30

    Hi Amy, and thanks for your reply. I will try to make it short. Altogether I have 15 machines that use the OnStream DI-30 and DI-30 FAST drives. These machines run Windows 98 SE, Windows 2000, Windows XP Home and Windows XP Professional. All drives have their firmware up to date. All drives are installed on the secondary IDE controller as slaves to the CD-ROM or CD-RW drive as the case may be. I don't remember where I read that this is the prefered setup for the DI-30 drives. The IDE drivers are as installed by the respective version of Windows. The ASPI drivers are either at the version distributed with Retrospect Professional or the newest from the Adaptec site. The Windows 2000 and Windows XP machiens are using SCSI Passthru. Cables are OK (unless I have 15 bad cables). Moving the drive(s) to another machine is a moot issue, as I already have several machines with these drives. I know that the OnStream DI-30 drives take longer to mount a tape compared with the only non-OnStream drive I have used (Sony SDT-10000). Maybe Retrospect should wait a little longer before giving up. It should detect that the drive is busy and give it a chance to mount the tape. Are you aware of any other OnStream DI-30 user who does not have this problem? Who knows... maybe I am jinxed.
  2. I have Retrospect setup to run a script. 1. Start Retrospect. 2. Quit Retrospect. I get the window asking whether I want to quit, check media or cancel. 3. Select Check Media. 4. Retrospect starts to access the tape drive, and while it is still accessing I get a message saying that the media required for the next backup is not available. 5. I select "Don't Quit". 6. Retrospect finishes accessing the tape drive and reading the tape. 7. Quit Retrospect again. and select again to check media. This time around Retrospect accepts the tape and quits. I tried these steps with a Sony SDT-10000 tape drive and in that case Retrospect accepts the tape at step 4 and quits. Why is it behaving different with the DI-30 drive? John
  3. FuzzyJohn

    Check Media When Quitting with OnStream DI-30

    Hello... anybody home?
  4. FuzzyJohn

    Error 102 - Revisited

    bhaidacher, In my case Stratus was able to change some settings or configuration on a SCSI card (they would not elaborate what) and sent me the card to replace the one in the system. This solved the problem and I have Retrospect running without a problem for over a week now. John
  5. FuzzyJohn

    Error 102 - Revisited

    My original post for this problem is Error -102 (Trouble Communicating). Please refer to that post if you want to see some of the Retrospect logs. Computer: - Stratus, fully redundant (4 CPUs, RAID) Operating System: - Windows 2000 Advanced Server The drive (from device properties in Retrospect: - Sony DAT DDS-DC - Vendor: SONY - Product: SDT-10000 - Revision: 02n5 - Location: Bus 4, ID 4 Note here that when I look at the drive properties in the Windows 2000 Device Manager, I see Bus 0, ID 4, LUN 0.color=red> The problem is that I am getting Error -102 messages at various stages when I am trying to backup the C: partition (operating system). So far I never got these messages while backing up the E: partition. Stratus, the computer manufacturer has checked all connections and terminators and found everything to be in working order. Stratus also confirmed that the Sony tape drive is connected to Bus 0, ID 4, not to Bus 4, ID 4color=red> as indicated by Retrospect. Since the operating system is Windows 2000, Retrospect uses the NT Passthrough by default. According to the Retrospect User's Guide, ASPI is not required for Windows NT/2000/XP. We did not move this drive to another computer. We did not try a different drive in this computer. But, since I have performed SEVERAL backups of this system using the Windows Backup program in Windows 2000 without any errors (except for the open files), and all of these backups also verified, I am confident that the drive is NOT defective. Unfortunatelly my boss gave me a deadline for today to either get Retrospect running on this very critical application that currently does not have a backup, or to return the whole package and look somewhere else. I recommended Retrospect over other backup solutions based on the good experience I have had with your program ever since version 5.1 when I started using it. John Castravet Port Authority of NY & NJ Communications, Security and Electronics Group Public Safety Department
  6. I checked all cables and terminators for this drive and I am still getting the Error -102 (trouble communicating) message. I got the message using 2 different tapes. The message comes up at different times while backing up, not at the same file or the same number of bytes. I also tried turning the hardware compression off. The drive is brand new as is the computer (Stratus). RDU.RPX in use is v3.5. I would appreciate it if you could point me in the right direction. Thank you, John Operating System: - Windows 2000 Advanced Server The drive (from device properties in Retrospect: - Sony DAT DDS-DC - Vendor: SONY - Product: SDT-10000 - Revision: 02n5 - Location: Bus 4, ID 4 Note here that when I look at the drive properties in the Windows 2000 Device Manager, I see Bus 0, ID 4, LUN 0. Error Message from the Retrospect log: - 11/13/2002 8:43:50 AM: Copying OEM (C:) Trouble writing: "1-Test Backup Set A" (396132352), error -102 (trouble communicating) - 11/19/2002 1:00:37 PM: Copying OEM (C:) Trouble writing: "1-Test Backup Set A" (446103552), error -102 (trouble communicating) - 12/04/2002 12:57:55 PM: Copying OEM (C:) Trouble writing: "1-Test Backup Set A" (115507200), error -102 (trouble communicating) - 12/04/2002 1:04:10 PM: Copying OEM (C:) Trouble writing: "1-Test Backup Set A" (588021760), error -102 (trouble communicating)
  7. FuzzyJohn

    Check Media When Quitting with OnStream DI-30

    Any thoughts on this yet?
  8. FuzzyJohn

    How to create alternating backups

    Docfxit, this should help you create a script that alternates between 2 backup set, Monday thru Friday. I use this script with my tape backup. You have to use 2 backup sets for this script, one for each drive and 4 schedules, 2 schedules for each backup set. See my note at the very end. - Create 2 backup sets. Name them "Backup Set A1" and "Backup Set A2" (or as you wish). - Go to Automate | Manage Scripts and create a new script. Select "No" when it asks if you want to use the EasyScript Wizard. Select a "Backup" kind of script. Name it "Alternating Daily Backup". - Select your sources. - Click the "Destinations" button and select both backup sets you created earlier. - Click the "Selecting" button and apply the selector of your choice. - Click the "Options" button and apply the options of your choice. - Click the "Schedule" button. ~ Start of schedule #1 ~ - Click "Add..." to create a new schedule. - Select "Day of week" (Run on specified days of the week). - Set the date when you want this schedule to become active. There are some minor quirks here, but to be on the safe side you should set the date to the next Monday. Example 01/20/2003. - Set the time when you want the backup to run. - Select this schedule to run on Monday, Wednesday and Friday. - Enter a 2 in Weeks to make this schedule repeat every 2 weeks. - Action should be "Normal Backup", to "Backup Set A1". - Click "OK" ~ End of schedule #1 ~ ~ Start of schedule #2 ~ - Click "Add..." to create a new schedule. - Select "Day of week" (Run on specified days of the week). - Set the date when you want this schedule to become active. Set the date to the Tuesday, the week following the start day for schedule #1. Example 01/28/2003. - Set the time when you want the backup to run. - Select this schedule to run on Tuesday and Thursday. - Enter a 2 in Weeks to make this schedule repeat every 2 weeks. - Action should be "Normal Backup", to "Backup Set A1". - Click "OK" ~ End of schedule #2 ~ So far these 2 schedules will run every other day on weekdays, on "Backup Set A1". You have to create 2 more, similar schedules that will run on the days the previous 2 schedules miss, on "Backup Set A2". ~ Start of schedule #3 ~ - Click "Add..." to create a new schedule. - Select "Day of week" (Run on specified days of the week). - Set the date when you want this schedule to become active. Set the date to Tuesday, the day after the start of Schedule #1. Example 01/21/2003. - Set the time when you want the backup to run. - Select this schedule to run on Tuesday and Thursday. - Enter a 2 in Weeks to make this schedule repeat every 2 weeks. - Action should be "Normal Backup", to "Backup Set A2". - Click "OK" ~ End of schedule #3 ~ ~ Start of schedule #4 ~ - Click "Add..." to create a new schedule. - Select "Day of week" (Run on specified days of the week). - Set the date when you want this schedule to become active. Set the date to the Monday, the week following the start day for schedule #1. Example 01/27/2003. - Set the time when you want the backup to run. - Select this schedule to run on Monday, Wednesday and Friday. - Enter a 2 in Weeks to make this schedule repeat every 2 weeks. - Action should be "Normal Backup", to "Backup Set A2". - Click "OK" ~ End of schedule #4 ~ - Click "OK". - Close the Backup script window and let Retrospect save the changes. - Go to Automate | Preview and make sure that the schedules are as you wanted and that the backup sets are rotated daily. - Go to Preferences | Execution | Unattended and enable the "Retrospect Launcher service" and "Automatically launch Retrospect". - Click "OK" and you should be all set. Note: Theoretically you should be able to get by with only 2 schedules that run every 2 days and then in Preferences you restrict Retrospect to running only on weekdays. However, when you do that, on Monday Retrospect seems to want to make up for the the weekend and will run a schedule at 12:00 AM which you did not set. AmyC, is this a bug? Also, any restrictions you set in Preferences will affect other scripts that you may create in the future and which you may want to run on weekends too.
  9. FuzzyJohn

    Error -102 (trouble communicating)

    Good to see Retrospect working once again. That said, I have to take a little time to wipe the egg off my face. The problem indeed turned out not to be Retrospect. Stratus did more in-depth investigating and they ended up changing some settings on the SCSI controller card for the tape drive. That done, everything worked like a charm. John
  10. FuzzyJohn

    Error 102 - Revisited

    I just downloaded and installed the newest RDU.RPX (v3.6.104). Same problem. John Castravet
  11. FuzzyJohn

    Error -102 (trouble communicating)

    Hi Amy, Doesn't the fact that I was able to use Windows Backup several times to do full backups of the machine (except for the open files) tell anything?
  12. FuzzyJohn

    Error -102 (trouble communicating)

    The system manufacturer also confirmed that the Sony tape drive is installed on Bus 0, ID 4 not on Bus 4, ID 4 as reported by Retrospect Drive Properties. I would appreciate a solution to this problem, as this system is already in production, in a critical application, and the costly Retrospect software that we purchased (Single Server + Open File Backup + Disaster Recovery) does not do anything to protect this system. Thank you, John
  13. FuzzyJohn

    More Than One Snapshot?

    Why is it that my backup sets (OnStream DI-30 FAST) show more than one snapshot for each drive? One is dated 10/26/2002 and the other is dated 11/28/2002. This seems to happen every now and then, but it also seems to happen around the same time on several machines where I use Retrospect. It also happened with Retrospect Desktop v5.x. John
  14. FuzzyJohn

    Error -102 (trouble communicating)

    The system manufacturer (Stratus) checked the cables and terminations. They reported everything OK. I ran Microsoft Backup in Windows 2000 Advanced Server repeatedly on all drives with verify turned on and there were no problems. If Microsoft Backup can keep communications with the drive during full system backups, why does Retrospect lose communications? John
  15. FuzzyJohn

    More Than One Snapshot?

    Well... so far this seems to be a mistery. <<< You can check the properties of the snapshots in Configure > Backup Sets by getting properties on a given backup set to see if anything stands out. >>> Checking the properties of both snapshots reveals no changes: Snapshot 1: Backup Set: John Backup Set D Type: Volume User: John Created: Saturday, October 26, 2002, 09:10:09 AM OS: Windows XP File System: NTFS Attributes: startup volume Contains: Registry, COM+ Class Registration database, WMI Repository, Disk Quota Information Snapshot #2 Backup Set: John Backup Set D Type: Volume User: John Created: Thursday, November 28, 2002, 09:54:49 AM OS: Windows XP File System: NTFS Attributes: startup volume Contains: Registry, COM+ Class Registration database, WMI Repository, Disk Quota Information <<< Another possibility is that something changed on the drive that made Retrospect think it wasn't _exactly_ the same drive again. It could be something as simple as a name change. >>> I don't know what to say about this. I did not change the name of the drive. And besides, that hard drive has 4 partitions and each partition shows 2 snapshots in the backup set. The log does not show any kind of problem during the October 26, 2002 backup or during the next backup.
  16. FuzzyJohn

    More Than One Snapshot?

    Unfortunatelly that is not the case. Most computers that I have seen this on, only have one user and on most of those, only manual backups are performed. However, one thing that I seem to notice when I looked back in the logs, the last time this happened on 2 computers that I have access to at this moment was after I updated RDU.RPX from v3.3.105 to v3.4.106. Does this mean anything? John
  17. FuzzyJohn

    Error # -102

    Is it possible that this error is also because of a bad media (tape)? I came across Error # -102 when I installed a new Sony drive. I only have one tape available (more on order). I repeatedly erased the tape and tried the backup and the problem seems to happen around the same place during the backup (about 1 GB into it). I should get more tapes next week and I'll give it another try. John
  18. FuzzyJohn

    Error 505

    One day last week I got Error -505 message for any client that I was trying to back up. The only reference I found to this error in the knowledge base is in Home > Support > Retrospect 4.x (Macintosh) >: -505 client reserved This error occurs when a client is in use by another backup computer A client may be used by only one backup computer at a time. This can also happen when the backup computer or client computer crashes during an operation. Restart both computers. Why am I getting a Mac error when I have no Macs on the network? I am using Retrospect Desktop v5.6 with RDU 3.1, running on Windows Me, backing up to an OnStream DI-30 drive set up as a slave on the secondary IDE channel (CD-ROM is master). John
  19. I see that Adaptec has updated their ASPI Layer to v4.72. Does Dantz have anything against installing the new ASPI Layer on a Windows ME machine running Retrospect Backup 5.6? How about on Windows 98 machines running Retrospect Professional 6? John
  20. FuzzyJohn

    Update Clients to v6

    When I update the clients to v6 from v5.6 do I have to do that at each workstation or can I simply update the clients from Retrospect Professional? If I have to update each client locally (at the workstation) should I uninstall the v5.6 clients first? John
  21. Can Retrospect Professional v6 coexist with CD Packet Writing Software such as Direct CD and B's CLiP?
  22. FuzzyJohn

    Retrospect under XP SP1?

    So far so good running Retrospect Professional 6 under Win XP Pro SP-1. No problem with the OnStream DI-30 drive that I use. John
  23. FuzzyJohn

    RDU 3.2

    Can RDU 3.2 be applied to Retrospect Desktop 5.6 as well or is it only for Retrospect 6? John
  24. FuzzyJohn

    Version 6...

    ...err...umm...argh... Why use custom titlebars for the child windows? I am using Windows XP and the program interface looks kind of ugly. Version 5.6 was better in this respect. John
  25. FuzzyJohn

    Verison 6

    Can you also post the "patch.rpx" file for users who do not have a broadband connection? That is the file I got in email from Tech Support and all I had to do was to place it in the program folder. As far as I could tell a few days ago the only difference between the new download (30+ MB) and the previous one, was the addition of this file. John
×