Multiple OC$ files

Question

I have a spec that when sync'ed, files don't seem to be sending to the target. After watching the sync'ed stats, the bytes get queued, files get queued, the kernel cache stays around 82%, nut no files get transferred. But in the mean time, I see multiple OC$ files are getting generated to the point the data directory automatically purges and the process starts over. Connection to the target seems fine, this has been working ok, but for some reason it seems as if the server can't send data to the target. Files sent stays at 0, completion percentage bar does not move.

Any direction on this issue?

Thanks

indyemcuser · Answer

- Allow the Spec's to perform real-time replicationfor a business day. How is a real-time sync kicked off?Do you mean to just kick off a non-scheduled sync?Message was edited by: indyemcuser

dramjass · Answer

If there are entries in the Kernel Cache/Logs, these are a build-up of I/O that have not been sent to the Target. This can occur if:
- the link between the Source and Target is not sufficient.
- A Sync is being performed. If a Sync is underway, RepliStor will cache all changes that are occurring during the Sync until it has completed.

Please ensure you are running RepliStor 6.3 SP2 (available via PowerLink) as it contains critical fixes for deadlock issues.

To see if the pipe is sufficient for the replication you are doing use these steps:
- Perform a DeleteDataDir (purge the Kernel Cache/Logs).
- Allow the Spec's to perform real-time replication for a business day.
- Monitor the Kernel Cache/Logs for abnormal growth. If you go day to day and are not catching up, it could mean that your pipe is insufficient. You can also try to change the performance settings in RepliStor (Maintenance -> Options -> Performance) to see if this helps.
- If there is no build-up, perform and schedule an Inc Sync of the data during off-hours, so that production I/O is kept to a minimum.

indyemcuser · Answer

Begining to realize that relistor is not a setup and forget application. I just had to delate all data directories, restart all services. for some reason even though i was not synchronizing, i had serveral servers that had 90% + kernal cache and climbing, creating the OC$ files. THis product is just hard to manage, but it is all i have for DR. in theory it works well, but actually running is something different. anyway, I am back to green on all servers, cache is at 0% across the board. just something more to monitor.

indyemcuser · Answer

so let me ask, if I have mirroring and forwarding turned on, do I ever need to sync (other thatn the first time)?

indyemcuser · Answer

Ok. Since all servers are mirrored, that explains why there is traffic all the time.

dramjass · Answer

There are 2 different replication functions used in RepliStor:
1. Mirroring - Real-time replciation occurs on a Spec when it is enabled all of the time. The I/O is first put in to the Kernel Cache (and logs if the Cache becomes full) then that same I/O is sent to the Target.

2. Sync (Inc or Full) - this is a point in time comparison of the data that is defined by a Spec. It is used when the data becomes out of Sync.

indyemcuser · Answer

Thanks! Love the response time on this forum. Very helpful!

dramjass · Answer

No, once you have Sync'd the data the 1 time, and the Spec is in its normal yellow'ish folder color (not red), then no other Sync's are required.

Mirroring will capture all I/O and send it to the Target.

To validate that Mirroring is enabled on a Spec, right-click the Spec and Modify it. Then go to the Options tab. Look for the option called "Sync Only (No Mirror). This option should NOT be enabled. This is a default.

A Sync is only required if Mirroring is stopped for a point in time such as:
- A Spec is Disabled
- A DeleteDataDir

Replication Manager

Multiple OC$ files

Was this post helpful?