Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Darrin

  • Rank
    Occasional Forum Poster
  1. Why would anyone design something that is normally run when no one is around to require someone be around Back to Veritas product on 2 of the "upgraded" RetroSpect servers. Working 100% every op, no errors. I can't in good conscience recommend Dantz product to any future customers. You've just admitted that this operation is intentional. It's true, you get what you pay for and RetroSpect is much less expensive than Veritas' offerings
  2. Exactly. This breaks unattended operation. I've gone back to Backup Exec on one of my servers. When the correct tape is placed in the drive, guess what? It reuses it. No buttons, no pre-erases. If there is ANY workaround or patch that Dantz can offer for version 6.0 and 6.5 (since Mayoff confirmed it is broken in 6.5 also), it would be VERY well received! This is the last nagging issue with Retrospect that I need to work out, and also the most brickwalling.
  3. So for me it's back to step 1, that RetroSpect cannot run unattended? a. I need to erase tapes manually before the scheduled script = not unattended. Or b. I need to click proceed when the correct tape is already inserted = not unattended. Or c. I need to wait for the media timeout and then the next scheduled script that uses the same set will correctly use the tape that is in the drive, even though the previous script requested a proceed click that was never given = not unattended because the current script doesn't finish. Could someone from Dantz please confirm if version 6.5 exhibits the same unattended limitations?
  4. Quote: Mayoff said: If you use the Check Script>Check Media command, and the check completes successfully then your unnattended backup should take that tape. If the unnattended (scripted) backup fails to take the tape, then that could be an indication of a device communication issue of some type. Run a test. Go to Configure>Preferences and set all preferences to Use Default Create a new backup script. Create a new backup set as the destination Don't schedule the script Go to Configure>Devices and erase a tape Go to the Run menu and Run the new script. What happens? Retrospect should take this tape. If it does not, then something in the device communication path is preventing us from correctly identifying this as a valid tape to use. Yes, takes the tape fine (automatically use new or erased media, that's a given). I understand that we could manually erase tapes ahead of time but that's very inconvenient and should be unneccessary for unattended backups.
  5. Quote: Mayoff said: If you do not use an erased tape during the process of doing a recycle backup, Retrospect will display a media request confirmation dialog to proceed and erase the tape. These are set members, but not erased. They are the correct members though. I don't think erasing tapes manually ahead of time is unattended operation. Similarly, if Retrospect cannot take the correct tape to recycle it without requiring a proceed button be clicked, how is that unattended operation either? I want it to proceed and use the correct tape that is inserted without asking for proceed to be clicked, regardless if the tape is empty, erased or full, but as long as it is the correct member that Retrospect is requesting at the time. Again, it seems to take the tape fine after a media request timeout occurs, then the next job that needs that set takes the tape in the drive fine, without proceed button even coming up. Why would it ask during the running script, then not again for the next script's execution? Thanks for your help, I'd really like to finally resolve this because it is the last (large) issue I am having, and I don't want to have to remotely log into these servers multiple times every week just to click proceed.
  6. Quote: Mayoff said: When using a script, Retrospect will automatically take any tape that is erased or named identical to what it is looking for, like 1-backup set A (at the time of a recycle backup or when requesting a new tape). You should not need to set any other options. If Retrospect is not automatically taking a tape like that, then a rare device communication could be involved. Please give me more details about this. It's a standard Seagate DDS4 SCSI drive that has worked 100% with Veritas software for years. Actually, the drive was just replaced in-warranty because the previous motors failed. Brand new drive, same model and config. Brand new tapes, all verified, cleaning at greater-than-recommended frequency (all this was before Veritas was removed and Retrospect was installed). Quote: A normal "backup" script has the "check media" option available when you do a "Check Script" form the directory. This will often help. If you turn on auto-skip to blank media in the preferences, we will take any erased tape at any time. Check media under devices shows the correct media in the drive, but grey member logo. I have not yet checked the media manually because it is always mid-script when it asks for additional tapes and I have to manually click proceed. Skip to blank is currently enabled, but this behavior occurrs regardless of this setting. Thanks for your help and further info, this is the last workaround I need to do in order to finally get the software running as I would like it to be. I found it hard to believe Dantz wouldn't make the software run properly unattended, so perhaps I am affected by this 'rare device communication' issue. Please give me more details. Thanks, D
  7. Hi, this is version 6.0.
  8. This is a single DDS4 DAT drive. How can I have it complete the current script when the media is inserted, without pressing proceed? Why is it interactive for the current (what matters) script, yet runs properly and unattended for the following script? All in all, not unattended operation. Thanks, D
  9. Darrin

    REALLY messing up!!!

    I'd set up auditing of security permissions changes on those shares to see what or who is making the changes. Probably a user who is incorrectly granted full control. Users should never be granted full control. Also, scan for viruses.
  10. The plot thickens. I have three backup scripts: 1. Server (local hard disks) 2. Workgroup 1 (5 workstations) 3. Workgroup 2 (7 workstations) Last night, Server ran as scheduled, no errors. It then ran Workgroup 1 as scheduled. It filled tape 2 of the 3 tape set and requested tape 3. Tape 3 was placed in the drive but I didn't click proceed. 12 hours later the media request timed out (I have my media request timeout set to 12 hours). BUT It failed the Workgroup 1 script with "execution incomplete" because I didn't click proceed on the tape, but it ran Workgroup 2 immediately following the media timeout and it worked properly, using tape 3 without me needed to click proceed. It changed the set member logo from grey to black. So it appears there is a glitch in that Retrospect DOES know the right media is in the drive but has to timeout the request before it will go ahead and use the media correctly anyway. Could someone at Dantz please test this and let me know how to get around it? This is the last of the bugs I've worked around on my own and it would be utterly fantastic to finally have it running truly unattended.
  11. Hi askirkland, In my other thread you asked: Quote: Darrin, What are your talking about with your multi-tape recycle issue? I have multiple tape backups and recycle them every 6 weeks... I have never had an issue where the backup job sits and waits for me to hit proceed. Am I misunderstanding you? What is your config and backup type... possibly there is some other work around... Here's what I'm doing: At one location, standalone NT4 SP6a server with single DDS4 drive, no autoloader. Retrospect Small Business Bundle (Single server and Open File Option). I have two 3-tape sets: 1-week1, 2-week1, 3-week1 2-week2, 2-week2, 3-week2 I have each set recycle on every second wednesday, respectively. Eg. 1-week1 in Wednesday June 4. It runs that evening and requests 2-week1. 2-week1 is inserted ~6 hours later (my media timeout is set to 16 hours), and then it needs to be selected and proceed clicked before it will use it, even though it shows in the media request window as 2-week1. This then happens again when 2-week1 fills and it requests 3-week1. The whole process recurrs with the other set when Wednesday June 11 comes around and 1-week2 tape fills. It always properly takes the 1- tapes without further confirmation, but the 2- and 3- tapes always require proceed be clicked, even though they always show properly in the tape request window. They do show up grey in that window though, probably because I told it to recycle the 1-tape and it 'forgets' the set catalogue at that point. Are you running the same sort of backups without this media request happening? If so, we should compare preferences and settings 1-1 all the way through, if you have time. At another location I have a standalone Windows 2000 Pro workstation with a Travan 40 drive, running Retrospect Single Server and it exhibits precisely the same behavior with tape requests. Thanks for your help, D
  12. Darrin

    6.0 to 6.5

    Hi Mark, AmyC had already told me that autoloaders aren't affected by this issue, although in your example yes, tape 5 with a new magazine will probably sit and wait for a proceed button. We don't have an autoloader, nor does it say in any documentation that autoloaders work differently than single drives in this regard. Thanks for your feedback though, it's nice to know someone's interested