Servers filling up since replication appliance gone

Hi Claudio,

You have 2 ways to attack this problem: 

1. You can remove from protection the volume or volumes that are having problems, this will get rid of those log files automatically for you after around 5 minutes. Once they are no longer in the system you can reprotect them. The downside with this approach is that it is going to trigger a new base image.
2. You can upgrade the core and agent to a newer version as the newer versions changed how they track the logs and no longer keep growing like that. Something 6.3 or newer should do the trick however if you prefer this approach I would recommend going to the latest version supported by your core OS.

Lastly, since you mention you are new to Rapid Recovery and they didn't give you any knowledge transfer I recommend you to watch these free training videos Rapid Recovery Administration: Module 1 - Product Overview - Free (quest.com). You can check the rest of them here Rapid Recovery - Educational Services (quest.com)

Thanks a lot Victor, I don't believe we are licensed to upgrade any further than what we are, when I check the licensing it spits this error: "

Forgot to mention in my previous message, you have 2 different problems. 

1. Replication
2. And AALogs

Both of them are not related one to another.

For the replication problem, you need to make sure the source core is able to reach the target core by testing ping to the hostname or IP address from the source core, and also making sure is able to telnet from the source to the target using the port 8006. If the server is not able to ping then the replicatin wont work, you can also remove the replication on both servers and try to add the replication server from the source core again.

To remove the volume from protection what you need to do is select the affected volumes and uncheck the protection check marks similar to this www.screencast.com/.../99LnBo07z

Thanks again Victor.  Yeah the "destination core" is gone, it appears the Dell server was formatted and made into a simple Dell R730XD (no quest software at all).  So I think I will delete.  Does the attached image seem like a good course of action to fix things?  https://i.imgur.com/R9EZTWq.png

Yes, just like that, after you do that wait around 5 minutes and check the affected server to verify if the AALogs are gone, if yes, then protect the volumes again.

Thank you, I went ahead with the plan, and un-paused the job.  The AALogs are still there though.  I am going to a meeting and will check back if things changed.

Still at the same spot, not sure what else I need to do to free up the space, I will attach one final image showing that 2 new "AALog" files are created, and none deleted.

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

Try the solution #2 from this KB article How to delete AALogs change logs (118402) (quest.com) 

Thank you, I will try.   I hate that I may have to do this 30x for 30 servers!

Thank you, I will try.   I hate that I may have to do this 30x for 30 servers!