Jump to content

mbennett

Members
  • Content count

    66
  • Joined

  • Last visited

  • Days Won

    5

mbennett last won the day on January 13 2020

mbennett had the most liked content!

Community Reputation

10 Good

About mbennett

  • Rank
    frequent Poster

Contact Methods

  • Website URL
    http://www.claritysoftwaresystems.com

Profile Information

  • Gender
    Male
  • Location
    Fair Grove MO

Recent Profile Visitors

544 profile views
  1. mbennett

    Disaster Recovery doesn't support high DPI screens

    The only possible idea I can offer is that if you can plug an external, lower resolution monitor into your laptop, and it it lights up (both very big "ifs" I realize) that may give you the ability to view a screen. I assume the second monitor is made accessible in the BIOS, so it's something to try.
  2. This is how I've been able to use the Disaster Recovery CD. I found my notes, so this should be pretty good, but I'm made a few edits. 1. Boot up with Retrospect emergency CD. Make sure you use the correct 32 / 64 bit version for the crashed system. 2. Initialize the drive every single time. If you completely start over for some reason just init the drive again, but make sure your situation is unrecoverable. Read the last paragraph. 2a. The biggest problem I've had at this point is obtaining the correct Network card driver. You can find that somewhere on the internet and put it on another CD or USB drive and load it as part of the initialization procedure. 3. Select to restore as client. The IP address will be displayed (requires DHCP to be running on the network.) 4. Go to the Retrospect server. Select to restore from the left menu bar, and create a new client during that process. It will find the client running, named "minit-xxxxxxx" and do not rename. Don't worry about the drive letters. (I have also gone to Configure | Clients and setup a new client there.) 5. Select the PC snapshot you want to restore, with the temporary client name as the target. Select the second bullet to restore the system state, registry and all files. 6. Once the restore is complete, reboot the client computer. If it doesn't boot it may be because the bit version was incorrect at step one, so try using a Windows emergency disk for the correct 32 / 64 bit system and repair the system. Generally speaking this works fine. The last time I used it the restore hung at about 98% complete and never finished. After almost an hour I eventually rebooted the client, cursing under my breath, and restarted the whole procedure. After I launched the restore job (new client name) Retrospect chewed for a few minutes and decided almost all of the files had been restored already, restored the very few remaining and the job was completed in less than ten minutes. I was extremely grateful. I hope some of this is useful for you. Good luck. Mark
  3. I think having duplicate names may be the issue, and it's ambivalent from the Retrospect POV. I'd rename the backup drive on the Retrospect server to "Backup2" in Windows. Then you'll need to rebuild the catalog for all of the backup sets. I think I'd do one as a test, since the rebuild will take a long time. This is just an opinion. The closest I've come to this is making a backup on a Windows 7 system where Drive C had one name, then installing Windows 10 on the same system overwriting everything. W10 uses a different drive naming convention, so I had to adjust a lot of scripts.
  4. mbennett

    Proactive job scheduling

    In addition to what Nigel and David have mentioned above, there is a tunable in Preferences | General that limits the number of executions that can run at once. I think 16 is the default, but if you have the resources you can bump it up.
  5. If you got the simple restore to work and saved the job, you should be able to toggle back over to the advanced restore and look for differences. I don't do a whole lot of restoring. The most fun I've had with this type of thing was to define my Downloads directory and exclude it from being backed up. I took several runs at that before I could get it to work.
  6. I haven't tested this, but using the "Condition" dialog can be very tricky. I think instead of "Starts with" I would instead use "Match". Keep experimenting in that dialog because that's where the problem lies. In fact, I would delete the other conditions and do this as a building block. Start with one line and make sure it gets the results you expect, then add one more condition, test the results, then another until you see the only results you want. Also, when the restore starts pay close attention to any prompts, because there may be a question in there with a "Do you want to overwrite" with a reverse logic default answer. Newer versions haven't changed this that I know of.
  7. mbennett

    cannot find Catalog File

    I think I'd call support on crossing platforms. But here are two things to try if you want. 1. Even going from one Windows system to another, the only sure fire way is to use the Transfer Backup Sets tool. I'm successfully moved the manager server setup, configuration and catalogs. But when you move the backup set to a new repository it won't work. Transfer takes care of that, but I'm not sure you can do that unless you can map a drive on Windows to the Mac's SMB share. 2. You should be able to create a new catalog from a backup set, simply by using the Repair a Catalog tool. If it repairs the catalog or creates a new one, you should then be in business. Running either function should be expected to take hours or days. Good luck.
  8. mbennett

    Stop "catchup" backups after starting Windows 10

    I suggest you simply remove the systems from the backup schedule on the weekend, therefore when you boot the systems on Monday morning there won't be a slowdown. You obviously already know how to launch a backup job manually, so just do that.
  9. mbennett

    Unable to bypass frozen Dashboard

    In case you haven't solved this already, start services.msc and stop all Retrospect services. Then the primary Retrospect program will start without the Dashboard loading.
  10. mbennett

    Half the time I get the Dashboard

    I can't explain why the Dashboard hangs when loading, but it has done that to me on occasion. If the Retrospect service is running, when you try to launch the program itself the Dashboard will launch instead. If no jobs are currently executing, you can click the power button in the top right corner and launch the program. If you do that, close the dashboard as soon as the program starts. If you try to start the program with a job executing it will kill the job or jobs. The same thing happens if you use services.msc and stop the Retrospect services, the jobs die immediately. This is sometimes not a bad thing, but you should know it's coming. A lot of people aren't happy with the Dashboard, but it does give you a way to monitor when jobs are executing, completed, failed, etc. without stopping the program from functioning. You can also simply launch the program once and minimize it. The big issue they're working around is how Windows services work.
  11. Oh, and one more thing. Restore something off your backups on a regular basis. Put it on you calendar. It's easy to restore an entire directory of pictures or documents to a new directory, check that it worked then delete them. A backup is only valuable if it works and the only way to know it works is to restore it.
  12. If you just bought an upgrade then you qualify for support. Submit this to Retrospect support via their website, or call them. They work pretty long hours and they can probably get this straightened out in a few minutes.
  13. mbennett

    Yet another -530 client not found error

    I experience this too, on a regular basis. Yes, it used to work and stopped being reliable a couple of years ago. Tried using a static IP address but that's inconvenient for a laptop that frequently travels to other locations and networks. Nothing else works. When it breaks I use ipconfig on the laptop and reset it to that address on the client setup in Retrospect. It's annoying, but nothing else seems to work.
  14. On the recovery disk and Windows one size does fit all, with the exception of bit size. You need a recovery disk for 64-bit and one for 32-bit if you have such systems. The much, much larger issue you have here is that your laptop won't boot the disk, which should take only a few minutes. Ten minutes is too long. Your laptop is likely dead, unless you can prove otherwise by booting from a recovery partition or a Windows installation image. If this is Windows 10 you can download a bootable image from Microsoft, burn it to a thumb drive and boot off that. You may need to dink around with the BIOS to get it to boot, but usually that's unnecessary. If it boots and installs Windows then you should first run MEMTEST which is also a free download from Microsoft, and every diagnostics program available from the laptop maker and figure out why it went south. Once you're absolutely positive that your hardware situation is stable, then you should be able to also boot from the recovery CD and restore a backup. You don't need to worry about the dissimilar hardware stuff since this is going back on the original source system.
  15. mbennett

    Unknown Windows error 343 after SSD upgrade

    I agree strongly with Lennart_T. You have an O/S or hardware problem. Until it's fixed and VSS is working without error you're chasing the wrong problem by trying to get Retrospect to work.
×