Jump to content

cogswell

Members
  • Content count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About cogswell

  • Rank
    Occasional Forum Poster
  1. Hello; So here's my scenario. 1. Install Windows 7 (32-bit) onto computer (dell GX270). Nothing else installed but retrospect client 7.7 2. Make brand new backup to new backup set using network client with Retrospect 7.7.620 3. Erase hard drive in GX270 (dban). Keep same hard drive in computer. 4. Boot from 7.7 Disaster Recovery CD. Make partition for C and format the hard drive as NTFS. "Restore as client" 5. Log DR client in on Retrospect 7.7.620. Restore and Replace entire volume. "Please reboot the system" 6. GX270: "BOOTMGR IS MISSING" every single time. For fun, try step 4 and don't make a partition that's the whole disk, just in case that "Retrospect has to remake the emergency partition" business is having trouble. This is a 250 GB hard drive and the default win7 install so it's about 11GB taken up. Same result, bootmgr is missing. So, how are you supposed to actually restore a Win7 desktop with 7.7?
  2. Hello; I'm on Retrospect single server 7.7.620. Retrospect crashed, I suspect while grooming this disk dataset (two members, one full, one with 1.5TB of 2TB left). Now I can't verify it (crash on treefat.cpp), and now I can't even rebuild the catalog (crash on treefat.cpp-378, and lots of "Bad Backup Set header found (0x0500f8ff at 485,356)" in the logs). So looks like I have to recycle the backup set (again) and start over (again). I need backups for the backup. I don't really think I'll get a solution, I'm just frustrated.
  3. Hi there; Due to a recent influx of Windows 7 machines I've finally upgraded from 7.6 to 7.7. I upgraded yesterday, did the retrospect update and now it reports as version Single Server 7.7.620. I installed the 7.7.114 client on the Windows 7 machines, and now I have no end of headaches. My 7.6 setup worked perfectly, except for two windows 2000 machines that take about 9 hours to build a snapshot, but I'm not worrying about that here. I previously was backing up Win7 clients with 7.6 but I'm aware you can't do a bare-metal recovery with Win7 and 7.6, so I bought 7.7. Under 7.7.620/Client 7.7.114 the windows 7 machines all fail with error -519. Sometimes it's "Trouble reading files" -519, and sometimes it's "Scanning incomplete" If it was just the windows 7 clients I'd chalk that up to just my luck, but now I have many WinXP clients that I can't backup. It starts, gets the 519 error, then subsequent accesses of the client say "-505 backup reserved" I can't even access those clients again unless I either reboot that remote computer, or go and turn the retrospect client (versions 7.5, 7.6, 7.7) off and on again. Then it will just disappear and go back to -505 backup reserved. My poor sole Win98 client can't be even accessed anymore, "Error -1 (unknown)" I tried updating the client from on it from 7.0 to 7.7.114 and now I get an error message on the Win98's screen "The PCVOLDRIVER.DLL file is linked to missing export KERNEL32.DLL.FindFirstVolumeW" and still Error -1. I installed 7.7 over my old 7.6 setup. I used my old client database, and my existing backup sets (backing up to hard drives, and a NAS). I've tried forgetting and re-adding clients but that doesn't change anything. Retrospect .7.7.620 is running on an AMD 4600+ with 2GB ram, drives are connected via usb docks. This setup worked really well under 7.6. What else can I do? Do I have to go scorched earth and start over everything from scratch?
  4. Hello; Here's an easy question. I have retrospect 7.0 professional (windows) and want to add a couple of client licenses to it. Can I buy the 7.5 licenses and have them work with the 7.0 application? Thanks, Steve
  5. Hello; Here's an odd one I've been running into a few times, so I figured I'd post it. I apologize if this has already been dealt with. Retrospect 5.0.205 workgroup, Retrospect Driver Update, v. 2.7.102, AGP G4/350 (sawtooth), Mac OSX 10.1.5. Tape drive is a Seagate CTL-96G (built-in autooader, one SCSI ID, Retro calls it Driver "Archive Python DDS-DC 5.01", Product Python 28849-XXX, Vendor ARCHIVE) hooked through a Adaptec 2930CU scsi PCI card (Adaptec driver 1.1). Both the card and the drive are 50-pin connectors. I normally don't have any backup problems (except for Retro's ability to correctly find tapes in the autoloader which worked fine in 4.2 that I've detailed before, but this is an unrelated problem I think). The backup server is running normally, and "idle" (not actively backing up a client). With the "Backup Server" window (with the list of clients) in the foreground, I push command-W to close the window (to stop the backup server). I then get the normal "Really stop execution of Backup Server?" dialog box with the No/Yes buttons. The "Yes" button is pulsing blue for the default. This is all normal, and usually I push the enter key or click "Yes" to stop the server. Sometimes though, at this point Retrospect is hung up. The button pulses, but won't accept the Enter to acknowledge, and won't respond to clicks on the buttons. I can't move the windows around with the mouse or change the front/back stack order. If I click and hold on the Retrospect icon in the dock I'll get the "Application not responding" message. So far the only way I've found to get out of it is to force quit. Like I said, it doesn't happen all the time, and so when it does happen I get suprised. Nothing else seems to be out of the ordinary (that I can tell). I have three different scheduled backup server scripts (normal overnight, lunch time for people with laptops who leave, and one special case for a person who usually leaves with his laptop before lunch time) all to the same backup set, and I'm pretty sure this has occurred while any one of them is active (ie - I don't think it's one particular script). The force quit usually goes okay (I rarely try to quit the backup server while an operation is in progress so it's never been writing to the tape when I try) but it's just annoying. Best regards, Steve
  6. I am so damned happy I finally found this one. I've been wrestling for a couple of weeks with one stupid win98 laptop that would not be backed up by Retrospect 5.0 on OSX. This user roams away from the office a lot, so I don't get a lot of chance to fuss with their laptop. As well, it's "their" laptop not the company one so I don't have free reign to maintain the configuration on it, although I do back it up as part of our schedule when it's around. For the last month, on the few occasions the machine has been present, the Retrospect backup server would whine about "505 (client reserved)" errors, 519 errors, 1028 errors. Most times it would stop during the initial scanning files phase with "Net Retry". Sometimes it could scan all the files but never get an actual backup underway without a "505" error. If I went to the client and looked it would say things like "In use by "root" scanning" (I'm trying to remember from memory here, excuse me if I miss some details), even though Retrospect had given up and moved onto another machine or gone idle. Well I knew this was something wrong with the client machine, and not Retrospect, because it had been working fine just a month ago. Something had happened to the client configuration in that time. I uninstalled the 5.6.112 client, I reinstalled it. I even dug out my old floppy and installed the Retrospect Remote 1.1 client on it. None of that worked. I also tried a different brand network card, different network cable segments, different locations in the building (including one across from my own bloody desk so we were on the same hub). Nothing had any success. I had no current backup so I wasn't comfortable with the "reformat and reinstall" solution. So I resorted to Retrospect itself. I had several backups from this machine already, so I exported the huge list into excel and started looking for obvious changes. I will note the user pleaded ignorance saying that nothing had changed on their part (feh). I looked down the list and found a very different looking installation of McAfee Virus Scan Online. Yep, sure enough this user at one point had followed some dialog boxes to "upgrade" their pre-existing mcafee stuff. They now had "Virus Scan Online" and "Privacy" but not the "Firewall" product bought and paid for and installed on the machine. On a hunch, I disabled the auto-startup for the virus-scan, so that I would think it wouldn't be running. That didn't make the situation any better. I disabled all the mcafee startup items I could find in "msconfig", that didn't help either. I was ready to think it wasn't it and it was something else when I read a bugzilla report (#111316, search on http://www.mozilla.org/ ) from mozilla on mcafee. I don't pretend to be an expert on Mozilla, but their problem seemed to be that Mcafee Virus scan was installing a shim against the winsock.dll and intercepting all traffic going through it looking for viruses. That rang a bell in my head, since Retrospect has to talk tcp through winsock as well. The discussion hinges around a dll installed by mcafee called "MCSCAN32.DLL", which sure enough, this machine had now, but didn't have in it's original backup from a month ago. So I took the gamble and uninstalled the Mcafee Virus Scan and Privacy stuff, and after the required I reboot I am happy to report that Retrospect 5.0 on OSX is happily backing this machine up as if nothing was ever wrong. So it appears that not only was it the cause, but just 'disabling' mcafee in it's own control panels wasn't enough to fix it, it had to be uninstalled completely. I don't know if re-installing it will make the problem re-occur, but I do know I'm getting this damned machine backed up before something else goes wrong. Since I de-installed both the Virus scan and the privacy stuff at the same time before trying it, I don't know which one of those it was specifically. I hope someone else finds this useful, and spares them my consternation of the past couple of weeks. Steven Cogswell
  7. Hello again; Here's some further experience with this situation. I had the good fortune last night to be at work while this backup crossed tapes in the autoloader again, so I was able to observe a little more about what's going on during the Backup Server operation. - Retrospect was happily backing up to Tape 6 of this backup set (5,6, and one blank which will become #7 are in the autoloader. Tapes 1-4 are sitting on the shelf since it's only the four magazine unit). During the backup (of about 250MB, coming from an OSX client) #6 filled, it wrote the index and "searched" for tape 7, settling on the blank tape (now #7) and continued on. - When the backup finished and it began the compare, the dialog box for "please insert tape #6" appeared (since this backup had crossed from 6->7). I had the loader button accessible in retrospect, but when I dropped it down the only tape it "knew" about was #7 (the other slots in the loader were marked as "???", except for the one empty slot which said "empty" ), despite the fact it had just ejected #6 from the loader. I selected the slot where I knew #6 was. Retrospect nabbed it and happily started verifying. - That part of the compare progressed as it should, and when it had finished comparing on #6 it again popped up the dialog box asking for tape #7 (to continue verifying). Dropping down the "loader" menu showed that this time it even had #7 still identified (ie - it knew the locations of #6 and #7 in the list, it wouldn't know #5 since it hadn't touched it during this whole operation). I selected the known location of #7, and again it progressed as it should. It finished comparing that machine, then moved on to the next machine in the client list without asking for tapes. It never asks for tapes when it wants to write, it knows to search the autoloader if it hasn't found it. It's been happily backing up to this set since I started this thread, it just whines on the verify stage. I will note I did the upgrade to OSX 10.1.5 (on this backup server, and that OSX client) when it came out, it hasn't made any difference in this (it seems). I hope this is of use to someone.
  8. Hi and thanks for the reply. I should have mentioned that, sorry. I used to use 4.2 under 9.1, but I've been using 5.0 under OSX 10.1.4. I have OSX (and it's 9.2.2 OS9) on a separate drive from my OS9.1 (which I still boot into to use for some day-to-day operations). I don't have the ADK, as I think it was the upgrade from 4.1->4.2 which added support for my Python autoloader. I did the 'import' by copying my old retrospect preferences folder to /Library/Preferences on the OSX drive (I threw away my old retrospect event handler script, since I noted it was making classic boot up when retrospect 5.0 started). My powerdomain 2930 (which has the 4.3 bios from adaptec) card has a 50-pin mini scsi connector and so does the external case the python is in. Also I don't think I can change the autoloader ID separate from the tape mechanism (there's only one set of pins for scsi id, and only one device (scsi ID 5) shows up on the device list in retrospect), but I will check that. Having said that, I can't help but think this is a retrospect issue and not a scsi issue, as the unit changes tapes fine when it wants to get a new tape to write to, it's just when it verifies, and then it pops up the dialog box (which as far as I know, it shouldn't do when doing a backup server operation unless the tape isn't in the magazine). It knows the tape is in the magazine, because when I drop down the menu it's listed. What I have in /Library/Preferences/Retrospect now is: LaunchRetroHlper, Operations Log, Retro.Config (4.2), Retro.config (5.0), Retro.Icons (4), Retro.Icons (5.0), and retrorunfile
  9. Hello; I'm a long time happy user of Retrospect (starting with 3.0), and three days ago I upgraded from 4.2 to 5.0 in order to be able to backup a new OSX client (most of our company is running 7.6-8.6). I imported all my scripts and catalogs from 4.2 to 5.0 using the method in the manual, and I let it loose with my backup server over the weekend. What has happened is that although the autoloader (reported as "Python 28849-XXX, v 5.AC, Archive Python DDS-DC (4.08)", a 4/8GB 4mm dat drive) loads a new tape fine when it needs it, it won't go back and load an old tape during verify (I use the verify in the backup server script). Much to my suprise did I check in on it on the weekend and find it stopped a couple of hours after I started it wanting the tape that started the backup. (i.e. - backup server backs up clients, one client spanned the end tape 1 -> tape 2, when the backup part finished and the verify stage began it couldn't go get the tape 1 from the autoloader, it instead popped up the dialog box wanting it). I was able to do that manually and get through that one. To fix the rest I set the "media timeout" to only 10 minutes, and when the media would time out it would just give up on the verify and go back to backing up. With this it managed to go until the four tapes in the magazine were filled (which I expected). This is retrospect 5.0.205, I'm using an adaptec Powerdomain 2930 scsi card on a Sawtooth G4 with 352MB ram, I started the backup with "recycle backup" (so I wasn't trying to add to an old set, I re-used an old tape set) and I backup lots of different macs and PC's (see rant below). This same setup works just fine with Retrospect 4.2 under OS9 (which is what I've been using), and I'm able to use "Scan Media" on the loader bar without a problem in 5.0. Am I missing something here? The other thing I'm pretty annoyed about, is the dropping of Appletalk support, which I didn't even realize until I had it installed and noticed all my Appletalk clients were removed from the clients list. I still have a half dozen 68040 macs under 7.6.1 that now I can't back up. The TCP client requires PPC, and the Appletalk is unsupported. I still haven't quite figured out how I'm going to get around this, but I must say that for the money I paid this doesn't feel like an upgrade. Are there any plans to return this support, or am I now officially stuck? Steven Cogswell
×