RepliStor drive is no space - how to fix this ?

Hi,

Does OC$nnnn file exist?

If it exists, it suggest communication problems between the source and target.

You must check event log of RepliStor.

Hi,

Thank you for your reply.

Yes, there are a lot of OC$nnnnn files.

And because of these files, no space in the drive at all.

I'll check the network but how these log files can be cleared ?

Is it not necessary to reboot the source and target servers ?

Hi,

It is not necessary  to reboot the OS.

There are two workarounds.

You choose it

1) You need to investigate the event log, to solve the cause.

2) You execute delete data directory.

    And you will need to re-synchronize.

Hi,

Thanks.

I'll try.

Hi,

Did this solution work for you?

Irfan

Yoshinobu Ito has already provided the Delete Data Directory resolution of this issue on the Source node. Be prepared to wait a long time for RepliStor to remove all the old OC$nnnn.rdf files. I recommend you Disable all Specifications on the Source and Target nodes before executing the Delete Data Directory command. If they are enabled they will continue to try to send data from the Source to the Target which will not help clear out the OC$ files. Then before you enable and re-sync the Specifications make sure you can contact the Target node from the Source node. RepliStor requires ports 7144 1nd 7145 for TCP and UDP Bi-Directional communications. Once you have confirmed there are no communications issues then Enable and Sync the specifications and keep an eye on how fast the OC$ files come back, if at all. I also recommend you schedule a reboot of both nodes before restarting the Syncing.

EMC no longer supports RepliStor so if you plan on continuing to use it then this Forum is your best source of information. However, EMC cannot recommend any alternate host based replication solutions.