Jump to content

leydon

Members
  • Content count

    32
  • Joined

  • Last visited

Community Reputation

0 Neutral

About leydon

  • Rank
    Occasional Forum Poster
  1. Retrospect 7.6.123 Driver 7.6.2.10.1 Win 7, 64 bit I've got a QNAP TS-809PRO NAS device setup with a windows share. From Win 7 I can mount the drive (\\a.b.c.d\backup) with no problems, read, write to it etc. From Retrospect when I try to add it as a volume (Network...Advanced... unc set to \\a.b.c.d\backup it puts up the username/pw dialog, I type in exactly what I used from Win 7 and Retrospect comes back with error: Can't access server using the given username and password, error -1116(can't access network volume) I've triple checked I'm using same username password, it's not a caps lock issue etc. I can use same version of Retrospect from Win XP Pro SP3 and mount the volume with no problems. So I'm guessing this is some odd Win 7/64 bit, Retrospect 7.6 anomaly and I need to get a newer version of Retrospect but I just want to confirm thanks
  2. Tracked it down to a problem with RetroEventHandler.bat. This same batch file works fine on other systems but will frequently (but not always) crash my server. It pops up and down a lot of command windows before crashing. The very same file on another Retrospect server works fine. So it's something about this machine, I have no idea what. I took it out of the Retrospect folder and cobbled together another script to send me the backup log once a day. All is fine since.
  3. I have a similar problem and tracked it down to something with RetroEventhandler.bat. This was provided with an email application mailsndr.exe back in 6.x day's. When my scripts would end and the batch file runs the system would frequently (but not always) fail after popping up and down a series of cmd windows and then crash with the power failure dialog. I took RetroEventhandler.bat out of the Retrospect folder so it doesn't run and everything is fine.
  4. I've got scripts that are set to run in certain windows, for example 7pm to 9am with a 30 min wrap-up time. I noticed when I come in every morning and look retrospect has crashed with the dialog Automatic Execution unexpectedly terminated (possibly due to a power failure or system crash) So I set a script to run from 10am to 4pm (30 min wrap up time) and then came up to watch just before 4pm. I'm transferring some file backup sets to tape. Exactly at 4pm I could see retrospect shutting down the script ( I assume, because I could see the dos box pop up like it does when it executes the events in retroevent.bat) Then the program put up the Automatic Execution unexpectedly terminated.... dialog as if the system had crashed. This is absolutely repeatable. When any script reaches the end of it's alloted time range Retrospect acts as though it's crashed with a power failure or unexpected crash. Nothing gets written to the operator log either just like a real crash. I've reinstalled the program, deleted the old pref's file and recreated. Any idea's how to fix this ?( other than allowing the scripts to run 24/7? Windows XP SP2 1G ram Retrospect 7.0.265
  5. leydon

    Recreate catalog from tapes

    Thanks, it looks like that's the default and so it saved me. It looks like Fast Catalog Rebuild works ( at least for version 7.0.265 and LTO3 tapes)
  6. Retrospect Single Server 7.0.265 running on Win XP PRO sp2 I had a 9 tape LTO3 catalog get corrupted and rebuilt it using the following method Tools/Repair Catalog/Recreate from Tapes. it asked for the last member. I put in Tape 9 it worked for hours on this, I then told it to stop using the Revert option Next day went back and did tools/Repair Catalog/Update Existing, selected the partial recreation above and let it run all weekend. The recreated catalog "seems" to be ok, it shows all 9 members, snapshots look ok, etc. I had to forget it then add it to use it in my backup script. Is the above the proper way to rebuild a tape catalog? I expected to have to feed retrospect all 9 tapes and that this would take days to complete.
  7. Retrospect SingleServer 7.0.x I back up to LTO3 tapes in an autoloader. I've always got verification turned on in the backup script options. Does this essentially do the same thing as using Tools Verify Media? I ask because for all intents and purposes unless I've got a separate Retrospect system and lto3 tape drive there is really no way to use Tools Verify Media with an LTO3 tape. It looks like it will verify around 13G/hour and the tapes have anywhere from 600 to 700G on them (hardware compression). I can't see that there is any way to stop a verification then restart it where I left off. In the best of all possible worlds I would verify each tape as it fills up but can I be "relatively" safe in assuming that if the backup script doesn't report any problems with the tape during the verification phase then the tapes "should" be readable when I need them? Thanks for any insight. How do people handle this sort of thing?
  8. I found in the knowledge base how you can restore a system registry from a snapshot but is there a way to restore ONLY the System file from %WINDIR%\sytem32\config\. The notes say you insure the snapshot you want has the registry by checking the properties, then selecting a full restore and uncheck the hard drive so that NO files are restored, this then (I assume) will restore %windir%\system32\config\... DEFAULT SAM SECURITY SYSTEM Is the only way to be able to restore these files selectively by running regcopy? so they will be backed from the configbk directory?
  9. Retrospect SBS 7.x on XP Home system Client 7.x on Win2k I had a corrupt c:\winnt\system32\config\system file on a win2k box that was being backed up nightly (all files but cache selector) I wanted to grab just the system file to restore it so the client would boot but in c:\winnt\system32\config there was nothing backed up. I thought regcopy was only needed to run if you were backing up a windows client to a mac server. If you're backing up windows client to windows server does regcopy still have to be running on the client? Or....is the registry put somewhere else ? In Retrospect 7.5 Users guide regcopy is not mentioned and in the description for restoring a client it looks like it restores the registry but the snapshot shows nothing in c:\system32\config directory. Where are the files in c:\system32\config copied to ? thanks
  10. Retrospect Server for Mac v 6.1.126 with driver update 6.1.8.101, OS X 10.3.9 Client is Win XP Pro with all MS patches, and Retrospect Client 7.0.107 I've backed up this laptop to this Mac many times in the past, both to a disk based and tape based backup set. Now when I try to run the same backup script it is selecting all the files like the system has never been backed up before. I was having a similar problem about a year ago and updating to 6.1.126 fixed it. Does anyone have any idea why it would do this? Nothing crashed or failed. I successfully ran the same script about a month ago where it selected on the order of 250MB to backup. Now it want's to backup 49 GB which is basically the entire contents of the drive. I have two different scripts, two different backup sets, one goes to a file backup set, the other goes to a tape backup set. Both of them when I try running the script, or set it up manually to use the same selectors and backup sets say that 49 GB needs to be backed up. I sometimes connect both the mac and the laptop behind a linksys router so they both have 192.168.0.x ip's. I've tried running the backup under both conditions, behind the router and just on the lan (i.e. sometimes the client has a different ip...would this make Retrospect think it's an entirely new system or that files previously backed up are not now?) , in both cases the selector is acting like it can't see what has already been backed up.
  11. Retrospect Server for Mac v 6.1.126 with driver update 6.1.8.101, OS X 10.3.9 Client is Win XP Pro with all MS patches, and Retrospect Client 7.0.107 I've backed up this laptop to this Mac many times in the past, both to a disk based and tape based backup set. Now when I try to run the same backup script it is selecting all the files like the system has never been backed up before. I was having a similar problem about a year ago and updating to 6.1.126 fixed it. Does anyone have any idea why it would do this? Nothing crashed or failed. I successfully ran the same script about a month ago where it selected on the order of 250MB to backup. Now it want's to backup 49 GB which is basically the entire contents of the drive. I have two different scripts, two different backup sets, one goes to a file backup set, the other goes to a disk backup set. Both of them when I try running the script, or set it up manually to use the same selectors and backup sets say that 49 GB needs to be backed up. I sometimes connect both the mac and the laptop behind a linksys router so they both have 192.168.0.x ip's. I've tried running the backup under both conditions, behind the switch and just on the lan (i.e. sometimes the client has a different ip...would this make Retrospect think it's an entirely new system or that files previously backed up are not now?) , in both cases the selector is acting like it can't see what has already been backed up.
  12. I've got a Belkin UPS attached to a system running retrospect single server 7.0. I've also got version 7.5 but I've not installed it yet. The Belkin Bulldog software allows me to run batch files and I assume (hope) there is a way I can tell retrospect to stop executing the current script if the UPS has kicked in and the system is running on Batteries. Is there a way to do this from a batch file (or any other way)? I see that I could do it on the Mac server by writing an applescript and using "stop execution" command. Are there general tips for setting up Retrospect preferences for working with a UPS and shutting down gracefully in the event of power failure. A search of the knowledge base using UPS is pretty useless as it hits backups etc... thanks
  13. Mac OS X 10.3.9 Retrospect Backup 6.0.204 Client is Windows XP SP2 laptop running client 7.0.107 I have a script to do a full backup of this laptop. The first time I run it with a documents, no cache selector it grabs 43GB of files. That's fine. If I wait 24 hours with NO changes to the laptop and then run the exact same script it wants to copy 43GB , it doesn't seem to be doing any matching. I can physically browse the backup set ( it's a file backup set) and see that a given file is in the backup set and has not been changed on the laptop but retrospect still wants to copy it. If I run the script above and let it go for 10 gigs or so. Then tell it to stop. Then have it run again it seems to do the right thing...(i.e. it will say 33 GB to copy). So....it looks to me like this is somehow date related Anyone have any ideas? thanks
  14. Retrospect Single Server 7.0.326 running on XP Pro SP2 client with all current win patches The transfer backup sets feature either is not working or doesn't do what I thought it did. I have a Disk backup set with many clients backed up set to groom to 5 so each client disk has a max of 5 snapshots. When I do transfer backup set to tape with options (copy snapshots, verification) it DOES NOT copy all the snapshots. On the tape backup set I get 1 Snapshot for each client disk. I thought the transfer function would transfer all the snapshots so that using this as well as disk grooming you can keep a running backup on tape of all your snapshots that got "groomed" off of the disk. I assume there's something I'm missing
  15. Retrospect Single Server 7.0.326 running on XP Pro SP2 client with all current win patches The transfer backup sets feature either is not working or doesn't do what I thought it did. I have a Disk backup set with many clients backed up set to groom to 5 so each client disk has a max of 5 snapshots. When I do transfer backup set to tape with options (copy snapshots, verification) it DOES NOT copy all the snapshots. On the tape backup set I get 1 Snapshot for each client disk. I thought the transfer function would transfer all the snapshots so that using this as well as disk grooming you can keep a running backup on tape of all your snapshots that got "groomed" off of the disk. I assume there's something I'm missing
×