Jump to content

johnnymacgo

Members
  • Posts

    65
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by johnnymacgo

  1. Me too. Over the weekend I had the same type of freeze\hang with the console stuck at "Finding next-computer-to-backup". I'm running Retrospect for Windows Multi-Server V15.5.0.179 which I upgraded to last week. Before that I was running V15.1.2.100 for a while for no issues. It's on a Windows 2012 R2 server and the only thing that changed was the upgrade of Retrospect.  The backup computer is running Windows 10 Pro 1803 64bit agent version V15.5.0.179.

  2. Over the weekend I had the same type of freeze\hang with the console stuck at "Finding next-computer-to-backup". I'm running Retrospect for Windows Multi-Server V15.5.0.179 which I upgraded to last week. Before that I was running V15.1.2.100 for a while for no issues. It's on a Windows 2012 R2 server and the only thing that changed was the upgrade of Retrospect so I suspect its and issue with V15.5.0.179. The backup computer is running Windows 10 Pro 1803 64bit agent version V15.5.0.179.

     

     

  3. Hi,

     

    Since I upgraded our Windows Retrospect Multi-Server from V10.5.0.110 to V11.0.1.106 I'm seeing the following error intermittently:

     

    stfiDoBackupOne: error -1101 (File/directory not found) on C:\Windows\wlansvc\Polices\.

    and 43,392 others

    stfiWaitForBackupDone: Operation terminated, (file/directory not found)

    Trouble reading files, Error -1101 (File/directory not found)

    8/16/2016 8:11:52 PM: Trouble copying folders, error -1101 (file/directory not found) ddex=48,675

     

    (I'd paste more info from the operation log but for some reason this forum won't let me paste)

     

    This problem is new to V11.0.1.106. It happens to different Windows backup clients at different times. It even started happening at another customers site!

     

    I logged a call with support and they said I was seeing those because I don't have the Open File Backup license. I find that hard to accept since we never had Open File backup before and never had that error before the upgrade. They also said I was the only one to report it but like I said, It's happening at two totally different customers.

     

    The Windows clients were also upgraded to V11.0.0(252).

     

    So the reason for this post... Is anybody else seeing this error?

     

    Thanks!

     

    John

    • Like 1
  4. Hi,

     

    I'm running Retrospect for Windows Multi Server V10.5 to two USB disks. Retrospect started crashing recently with an Assertion failure at "elem.cpp-1145" while backing up a Windows Laptop that was recently upgraded to Windows 10. I logged a call with Retrospect support. They had me rebuild the catalog file on the USB disk and that fixed it.

     

    I hope this saves you some time if you run into this,

     

    Johnny Mac

     

  5. You don't say what version of Retrospect you are using. I use Retrospect for Windows V10.5 Multi-Server and I have already used that method. I had a client/laptop that the hard drive died on. I hooked my usb disk with the latest Retrospect backup on it directly to the laptop (that same disk also has the catalog on it). I then booted the laptop off of the DR CD and prepared the new disk on the laptop. Did a full disk restore. When the restore was done I removed the usb disk and the DR CD and the laptop booted off the newly restored boot disk just fine.

  6. Since upgrading from Windows Multi-Server V8.5 to V10.0.2.119 I have had multiple clients that were also upgraded to V10.0.2.119 bind to the wrong IP address (usually on our iSCSI SAN). Working with Retrospect support we finally found that you shouldn't use -ipsave but use /ipsave instead. So the full commands would look something like this:

     

    C:\Program Files (x86)\Retrospect\Retrospect Client>retroclient /ipsave 10.10.0.??

     

    I didn't need to restart the Retrospect service. This created the following registry key:

    HKEY_LOCAL_MACHINE\\Software\\Wow6432Node\\Dantz\\Retrospect Client\\6.5\\BindListener

     

    This didn't happen to all clients with multiple IP, just some of them. I suspect that one's that worked wouldn't after a reboot until that registry key is created.

  7. I ended up logging a support ticket with Retrospect to get some answers. Here is their response:

     

    Details on the new .xml file can be found at:

     

    http://www.retrospect.com/en/support/kb/migrating-from-bak-to-xml-configs

     

    Please make sure you are using the 10.0.2 version of Retrospect, since it contains bug fixes related to the .xml file.

     

    Yes, both of those files are being used by Retrospect 10.

     

    I am not sure when the user's guide will be updated.  I will remind our documentation team that this is missing from the docs.

     

     

  8. Hi,

     

    Looks like config77.dat finally got replaced with configs.xml as per the release notes for V10.0.1.103:

    Engine: configs.xml, which replaced Config77.bak for speed and robustness, does not import all settings including client volumes and network subnets (#5316)

     

    Looking at the Retrospect V10 Users guide and it references config77.dat instead of the new XML configuration file on page 462:

     

    Moving Retrospect

    If you ever decide to switch backup computers, you must do more than just install

    Retrospect and your backup device on the new machine. You must move some other files

    to the new backup computer in order to keep Retrospect’s preferences, clients, catalogs,

    scripts, and schedules intact.

    To move Retrospect to a new backup computer:

    1. Install Retrospect on the new computer.

    2. Copy the Catalog Files (with name extensions .rbc and .rbf ) from the old backup

    computer to the new computer.

    3. The default location that Catalog Files are saved is ..\My Documents\ Retrospect

    Catalog Files.

    4. Copy the configuration file (Config77.dat) from the old backup computer to the

    new computer.

     

    On page 463:

     

    Configuration Backups

    Retrospect’s configuration file contains your client database, scripts, schedules,

    preferences, custom selectors, and other important information. Retrospect uses the

    configuration file, named Config77.dat, located in the folder in which the Retrospect

    application resides or at the path:

    ..\Documents and Settings\All Users\

    Application Data\Retrospect\

    Each time you exit Retrospect, it automatically saves a backup copy of Config77.dat in a

    file named Config77.bak. You should back up this file regularly. If your active configuration

    file (Config77.dat) is ever lost or becomes corrupt, delete it then open Retrospect, which

    creates a new Config77.dat from the Config77.bak.

     

    And a few other places. Can someone from Retrospect give us some more information on the new XML configuration file, how it's used and if the old Config77.dat file is even used anymore with V10? Is there going to be an updated Users Guide with this information?

     

    Thanks,

     

    John MacGown

     

    • Like 1
  9. RE: Richy_Boy:

     

    -->

    It's about time they created a config export tool, which would allow us to export the config (which would also do a corruption/fix process), then we could wipe and reapply all our settings quickly.

    <--

     

    I couldn't agree more. My config file gets corrupted on a weekly basis now. How I get around it is I delete all the execution history and it works for another week or so. If I do end up creating a new config file it takes me about 4-5 hours to get it right.

     

    Johnny Mac

  10. There is a fix to some grooming issues in Retrospect for Windows V8.0. From the release notes located here:

     

    http://kb.retrospect.com/articles/en_US/Retrospect_Article/Retrospect-8-for-Windows-Release-Notes/?q=8.0+windows+release+notes&l=en_US&fs=Search&pn=1

     

    "2413: Fixed a bug that caused repeat occurrences of Grooming error -2241 even after catalog rebuilds"

     

    I groom my disk backup sets once a week and run into grooming issues every other month or so. I end up recycling the disk backup set and then do a Transfer Backup Set from my most recent tape backup set to the newly recycled disk backup set. It's a pain to do but I'm not ready to move to V8 yet.

×
×
  • Create New...