Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by johnnymacgo

  1. I really hope they can address this issue also. I am currently having issue running this on Windows Server 2008 R2. Scheduled backups are not running and cannot stay logged on via RDP so leaving it "open" is not an option.


    You really don't need to stay logged on via RDP to keep Retrospect running. I connect via RDP to check the status of backups and then just disconnect (not logout) and everything keeps running.

  2. Retrospect V7.7.325 Multi-Server crashed last night with the following error:


    OS: Windows Vista version 6.1 (build 7601), Service Pack 1, (64 bit)

    Application: C:\Program Files\Retrospect\Retrospect 7.7\Retrospect.exe, version 7.7.325

    Driver Update and Hot Fix version (64-bit)

    Exception occurred on 1/11/2012 at 5:23:45 PM

    Error info: Assertion failure at "elem.cpp-1098"

    Exception code: E0000000 ASSERTION

    Fault address: FD9ACACD 0001:0000BACD KERNELBASE.dll


    This is just a FYI. I found the cause to be due to backing up one of my Windows Clients, The client is running Windows 2008 R2 and I reformatted it's data disk and gave it the same exact label as before. This caused Retroect to think that it had two of the same volumes when it went to back it up:


    1/11/2012 5:12:18 PM: Connected to BOAZ

    * Resolved container BOAZ to 3 volumes:





    I reconfigured the client to only use selected volumes and deselected the last volume and it worked fine.


    Johnny Mac

  3. -->

    My license manager says I have Advanced Tape Support, but I cannot get retrospect to use my librarie's multiple LTO drives in parallel on a single backup job, a feature detailed on the website as the capability provided by Advanced Tape Support. (I will note that I can do multiple single jobs simultaneously, a feature the website details is included without Advanced Tape Support.)



    I've never had multiple LTO drives to do a parallel backups in a single script but I belive you might have to BIND the tape drives together. If you open up the properties on the tape backupset there is a "Binding" tab. I can't get to this tab as I don't have the Advanced Tape Support license but you might want to look there.

  4. The compression issue is a bug in V7.7. There was very good topic on it in the old forum writen by wuchem and if it comes up it was located here:




    The work around was to recycle the tape backup sets and before you add new member tapes to the backupset, put them in the drive first so they can be read and the add them to the backup set. This should set the "DC" flag on the tape when you look at the properties on the tape drive.


    Hope this helps,


    Johnny Mac

  5. What kind of backup set do you have? Tape? Disk? Disk

    Do you backup both servers to the same backup set? No

    How many files and how much data is there in the backup set? One backup set has 894,909 files with 1.59GB used and the other has 1,324,800 files with 2.82GB used


    For me this issue has nothing to do with the size of the target backup set or the number of files on it. It's how much DATA is being transfered from the client. If it goes above 508GB it fails, less than that and it works.

  6. I have the same exact problem on 64bit clients with big amounts of data to backup. The clients are Windows 2008 R2 systems and the data is more the 1TB. I called Retrospect support for this issue. They said to try disabling Antivirus, defrag the disk ect... and nothing helped.


    How I worked around the problem is in the Retrospect client I temporarily excluded some of the larger folders to keep the total backup under 508GB. Once it backed up less then 508GB I un-excluded those large folders to still keep it from backing up less then 508GB at one time and backed up the disk again. Once it's finally done I remove all excluded folders and then backups run fine after that. It's a pain to do it that way but it works.

  7. We have about 40 remote clients including some Mac's and servers.


    I also quit Retrospect after configuration changes and make backup copies of the config file and do sometimes go back to those backup configuration files. The issue with that is even that backed up configuration file starts to go bad after running on it and it gets to a point where I can't make any more configuration changes unless I wipe it out and start over again.


    I'm just hoping that engineering is working on a fix to this. There is more stored in the config77.dat file besides configuration information. I believe script history is also stored in it. Thats why the file gets bigger over time even when no configuration changes have been made to it. Maybe if they took all the non configuration information out of the file it wouldn't get corrupt so often? Thats just an idea...

  8. We do not have any optional Retrospect modules installed. I don't think this is really an issue with d2d2t but more likley how many remote clients we are backing up and the fact the those clients change fairly often so we keep on having to delete old clients and add new ones. Thats what seems to cause the corruption.


    I am aware of the backup copy of the config file and like I said I do use backup copies of the config file already but even the backup copies seem to get corrupt over time.


    I just rebuilt the Retrospect config today and it ended up taking up a good part of the day :-( If this was a once in a blue moon type of thing it wouldn't be too bad but the file seems to get corrupt after about 3 months or so.

  9. Hi,


    I'm running Retrospect Multi Server V7.7.325 64-bit in a fairly complex enviroment doing disk to disk to tape backups. My config77.dat gets corrupt every few months or so. The symptom is that backing up a remote client (usally a random one) hangs while scanning it. I worked with Retrospect support a while ago on this and they found that the configuation file was hosed. If I create a new one and reconfigure everything from scratch (takes about 3-4 hours) then the remote client backs up fine.


    I have ended up shutting down Retrospect every week or so to make a backup of the config77.dat but what I find is when I use that backed up config77.dat and then put back all the the changes made since the last backup the file ends up getting corrupt again in a matter of weeks.


    I have traced down the problem to adding new remote clients. If I add a new client and then add that client to a backup script, one random client in that script will hang during scanning later on, sometimes the same day, sometimes days later. This problem is not specific to hardware since it happened on two totally different servers and clients. I don't really want to update to V7.7.5XX since I've read about alot of new different bugs with that version.


    My question is, Is Retrospect Engineering working on a fix for this issue? Is it even on their bug lists? I know lots of other people have reported problems with configuration file corruption as well.




    Johnny Mac

  10. I agree, I have run into the same exact issues you have:



    Since years Retrospect has some major bugs:

    1) Damaging configuration. The Retrospect configuration is easily damaged, and there is no way to repair of export the settings.

    2) Starting as a ‘Service’ so the UI is always available, now the UI is unreachable, if the main program Retrospect was not running.

    3) Grooming failure



    I don't think it's a setup/configuration or hardware issue at. Since I have had these same problems on two different servers with totally different hardware.


    Numbers 1 and 3 are really bad for me since they require a hugh amount of my time to recover from them. They really do need to be fixed.

  11. Hi Tom,


    I'm not sure I'm getting the same exact error as you since I can't read German but I do get the following event logged to the application log on all my Windows 2008/Windows 2008 R2 systems when retrospect backs them up, this happens at multiple sites:


    Log Name: Application

    Source: VSS

    Date: 9/17/2010 11:41:13 PM

    Event ID: 8194

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: GAD


    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x80070005, Access is denied.

    . This is often caused by incorrect security settings in either the writer or requestor process.



    Gathering Writer Data



    Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}

    Writer Name: System Writer




    Johnny Mac

  12. It seems like V7.7.341 was released in 9/7/10 and is available here:




    That sites states:

    "2.Click on the product name to view the readme file."


    But those links seem to be broken. I downloaded the full update but the readme for it doesn't list the changes in .341. What has changed and what has been fixed in this new release?




    Johnny Mac

  13. Hey Greg,


    Yes, I finally did get compression on my tapes so there is defiantly a bug within Retrospect V7.7 that you found! This is the first time I have seen my tapes go over 800GB of capacity. I got 1100GB on some of them. We were looking into buying new tapes because we were running out of capacity on the ones we have and you saved us from doing that!


    Were you going to log a call with them so they fix this issue?


    Thanks for posting this,


    Johnny Mac

  14. Hey Greg,


    It seems like you found a bug to me. I'm using Retrospect V7.7.325 (64-bit) with driver update and hotifix V7.7.3.203 connected to a Dell PowerVault TL4000 library that also has a LT04 SAS tape drive. I was not getting any compression at all on all of my tape backup sets (created with compression enabled) and the DC was not displayed under "Format: U-416". I recycled 4 of my tape backup sets and added the tapes as members just like you said, put them into the drive first and then add them. Now they all show us as "Format: U-416, DC". I will be running backups this weekend that normally take 8 tapes, lets see how many tapes it takes now.


    Good find,


    Johnny Mac

  • Create New...