• by Published on 04-13-2011 09:21 AM

    Hi All,

    After lengthy support sessions with Asigra yesterday, we found that an issue we were having was down to a bug in the latest Asigra patch for Windows DS-Clients. This patch has now been removed from the Asigra Web Portal but if you have it, remove it and take it out of your Auto-Upgrade repositories if it is there...

    The issue is that, when retention runs, it reduces the online number of generations to 2... regadless of the number of generations you have per set... As you will understand, this is a very serious issue and Asigra are currently working to fix the issue.

    I havent seen any notifications about this issue anywhere yet but the update was downloadable from 9th April, so someone other than myself must be suffering with this issue.

    Anyway, thats the heads up... if you have already rolled out this hotfix, the only real option is to suspend Retention activities and wait for a patch.


  • Recent Forum Posts


    (Error) Failed to allocate database connection.

    I have the same issue. In my case, I am setting up the 64bit DS-Client on a new machine and restoring the db and then I get the error even with a new

    backmeup 08-29-2014, 04:07 PM Go to last post

    N-Central/N-able DS-Client API


    I am looking into the possibility of integrating our Asigra monitoring with our N-central installation.

    The instructions

    Jamesc 08-28-2014, 12:49 PM Go to last post

    Storage Hardware Considerations

    Asigra Vs. ShadowProtect is an apples Vs oranges comparison. ShadowProtect is short term storage of disk images for DR and Asigra is long term file storage

    GaryP 08-26-2014, 09:09 AM Go to last post

    Storage Hardware Considerations

    Thanks Rackman for the response. Do you use 7200 RPM drives on your standalone DS-System and 3Par storage? I would love to be able to on our next rig.

    abeland 08-26-2014, 08:00 AM Go to last post
  • Recent Activity

--> qwerty <--