<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic CyberArk PAM Self-Hosted – Production Vault Replication Errors (PAREP022W/PAREP011E) – Request for Guidance in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/cyberark-pam-self-hosted-production-vault-replication-errors/m-p/1410037#M84999</link>
    <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The DR padr.log repeatedly shows:&lt;/P&gt;&lt;P&gt;PAREP022W: Duplicate file table name for file …, file ignored.&lt;/P&gt;&lt;P&gt;PAREP011E: Could not move replicated file …&lt;/P&gt;&lt;P&gt;PAREP015W: Not all Safes replicated successfully.&lt;/P&gt;&lt;P&gt;PADR0011E: Replicate failed.&lt;/P&gt;&lt;P&gt;The log also reports “Metadata Replication is running successfully,” but the file replication errors continue.&lt;/P&gt;&lt;P&gt;The affected paths are under:&lt;/P&gt;&lt;P&gt;E:\PrivateArk\Safes\Data\PSMRecordings\Root&lt;/P&gt;&lt;P&gt;The full error lines reference files with names like these, with identifiers simplified here:&lt;/P&gt;&lt;P&gt;&amp;lt;session-GUID&amp;gt;.win.#&amp;lt;number&amp;gt;# - shortcut.lnk&lt;/P&gt;&lt;P&gt;&amp;lt;session-GUID&amp;gt;.vid.#&amp;lt;number&amp;gt;# - shortcut.lnk&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Sep 2026 07:05:56 GMT</pubDate>
    <dc:creator>OHweidi</dc:creator>
    <dc:date>2026-09-23T07:05:56Z</dc:date>
    <item>
      <title>CyberArk PAM Self-Hosted – Production Vault Replication Errors (PAREP022W/PAREP011E) – Request for Guidance</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/cyberark-pam-self-hosted-production-vault-replication-errors/m-p/1410037#M84999</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;The DR padr.log repeatedly shows:&lt;/P&gt;&lt;P&gt;PAREP022W: Duplicate file table name for file …, file ignored.&lt;/P&gt;&lt;P&gt;PAREP011E: Could not move replicated file …&lt;/P&gt;&lt;P&gt;PAREP015W: Not all Safes replicated successfully.&lt;/P&gt;&lt;P&gt;PADR0011E: Replicate failed.&lt;/P&gt;&lt;P&gt;The log also reports “Metadata Replication is running successfully,” but the file replication errors continue.&lt;/P&gt;&lt;P&gt;The affected paths are under:&lt;/P&gt;&lt;P&gt;E:\PrivateArk\Safes\Data\PSMRecordings\Root&lt;/P&gt;&lt;P&gt;The full error lines reference files with names like these, with identifiers simplified here:&lt;/P&gt;&lt;P&gt;&amp;lt;session-GUID&amp;gt;.win.#&amp;lt;number&amp;gt;# - shortcut.lnk&lt;/P&gt;&lt;P&gt;&amp;lt;session-GUID&amp;gt;.vid.#&amp;lt;number&amp;gt;# - shortcut.lnk&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;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?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Sep 2026 07:05:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/cyberark-pam-self-hosted-production-vault-replication-errors/m-p/1410037#M84999</guid>
      <dc:creator>OHweidi</dc:creator>
      <dc:date>2026-09-23T07:05:56Z</dc:date>
    </item>
    <item>
      <title>Re: CyberArk PAM Self-Hosted – Production Vault Replication Errors (PAREP022W/PAREP011E) – Request for Guidance</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/cyberark-pam-self-hosted-production-vault-replication-errors/m-p/1410038#M85000</link>
      <description>&lt;P&gt;Sorry, not sure what you have tried already but most replication issues can be resolved by doing a full replication.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are a few KB's on this but this one looks good, pretty much what you suggested&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/PAREP022W-Duplicate-file-table-name-for-file-PAREP011E-Could-not-move-replicate" href="https://community.cyberark.com/s/article/PAREP022W-Duplicate-file-table-name-for-file-PAREP011E-Could-not-move-replicate" target="_blank"&gt;PAREP022W Duplicate file table name for file - PAREP011E Could not move replicate&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Thu, 24 Sep 2026 15:30:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/cyberark-pam-self-hosted-production-vault-replication-errors/m-p/1410038#M85000</guid>
      <dc:creator>N.Southgate046715</dc:creator>
      <dc:date>2026-09-24T15:30:21Z</dc:date>
    </item>
  </channel>
</rss>

