- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
09-23-2026 12:05 AM
Hi everyone,
I’m troubleshooting a recurring replication issue in a production CyberArk PAM Self-Hosted environment with a Main Vault and a DR Vault. Before making any filesystem changes, I would appreciate advice from anyone who has encountered this.
The DR padr.log repeatedly shows:
PAREP022W: Duplicate file table name for file …, file ignored.
PAREP011E: Could not move replicated file …
PAREP015W: Not all Safes replicated successfully.
PADR0011E: Replicate failed.
The log also reports “Metadata Replication is running successfully,” but the file replication errors continue.
The affected paths are under:
E:\PrivateArk\Safes\Data\PSMRecordings\Root
The full error lines reference files with names like these, with identifiers simplified here:
<session-GUID>.win.#<number># - shortcut.lnk
<session-GUID>.vid.#<number># - shortcut.lnk
I found matching Windows shortcuts on both Main and DR. I’m considering moving only these .lnk files to a separate quarantine folder outside the Safes directory, leaving the original recordings untouched.
Would this actually resolve the replication errors? Is it safer to move them manually or through a PowerShell script? Could moving them on Main and DR affect Vault integrity or recording access?
This is a production environment, and I need an approach that does not require stopping any services. Can this safely be done while the services are running, or is there a different supported solution?
Thanks.
09-24-2026 08:30 AM
Sorry, not sure what you have tried already but most replication issues can be resolved by doing a full replication.
In terms of restarting services, you'll need to update the padr.ini and restart the padr service. Depending on the size of your DB and network speeds it can take a while but would be different for each environment.
There are a few KB's on this but this one looks good, pretty much what you suggested
PAREP022W Duplicate file table name for file - PAREP011E Could not move replicate
Restartinf the padr services should not affect production service, however full replication's can put a strain on the vault if done at peak times. A full replication is only doing a full replication of the DB and not the PSMRecordings/files stored in safes.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

