• State Suggested Answer
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 28 subscribers
  • Views 4880 views
  • Users 0 members are here
Options
Related

Servers filling up since replication appliance gone

claudio howeg
over 1 year ago

Good afternoon,

I just started my role at this organization with no knowledge transfer.  I have never used Quest Rapid Recovery, so during my investigation I found out that apparently we had 2 appliances, but one disappeared (for whatever reason), so all the servers that are protected show yellow, and I believe that since replication is not taking place, the servers are getting full with AALog_xxxxxxx Files

I see the device is running version 6.2.1.100 (if that helps)

https://i.imgur.com/qrFxhcM.png

I am not sure how to fix this, while not completely destroy the existing data on the surviving appliance.

Thank you in advance for any advice you can provide!

  • 0 over 1 year ago in reply to phuff

    Thanks a lot Paul, I tried following the KB, the link on "how to get aces to the system volume information folder" is broken.

    I cloned the VM to test this, and it worked. Can someone please let me know if this is OK or if this is super bad to do:

    Stop Agent Service and set to Disabled
    Launch elevated command prompt
    execute the following commands:
    cacls "driveletter:\System Volume Information" /E /G MYUSERNAME:F
    assuremc disable C:
    del aalog*.*
    cacls "driveletter:\System Volume Information" /E /R MYUSERNAME
    assuremc enable C:
    Set Agent Service to Automatic (Delayed Start) and start Agent Service.

    Thank you!

  • 0 over 1 year ago in reply to claudio howeg

    I'm glad it worked. Good move on cloning first. It isn't the 'preferred' method, however it does work. With the older versions it is sometimes necessary (needed) to get the job done, that or a full removal of the agent should do it too. Just be prepared, it might abruptly reboot the OS without warning if you do it. Though not 'preferred' it does work.