How to migrate Shadowcopy files.

GOAL
After completing this guide, you will have moved existing Shadowcopy files from one EDP server to another.

1.  Prepare New Server
   • Install EgoSecure
   • In AdminTool: Set server type to Management + ShadowCopy and activate "Accept shadowcopy data" (if not already activated)
   • Connect to the existing SQL database
   • In the Console under Product settings → Audit → Shadowcopy → Shadowcopy server settings, enter the new storage path (the copied files will be stored there later). Recommendation: Use the identical path as on the old Windows server. The path must be local on the server. Note: The storage path is stored in the SQL database. Changing it in the Console affects all servers connected to that database. Using the identical path on both servers avoids any conflicts.
   • After configuration is complete, stop the EgoSecure Server service on the new server. Do not restart it until step 3.
2. Pre-synchronization
   • Copy the Shadowcopy data from the old to the new server, for example, with Robocopy.
   • Repeat the copy process several times until there are almost no differences left. Note: Do not copy the "Uploads" subdirectory. It contains incomplete in-progress transfers that will be retried by agents automatically.
3. Stop Old Server
   • Stop the EgoSecure Server service on the old server.
   • Perform one final Robocopy pass to capture any files uploaded since the last sync. Note: This step is required. Both servers run a cleanup cycle every 24 hours that claims ownership of local files in the database. If both servers are running with copies of the same files, they will repeatedly overwrite each other's ownership records in the SHADOWCOPY table. Stopping the old server prevents this.
   • While the old server is stopped, agents will buffer shadow copy files locally. The default client-side storage limit would be sufficient for a short outage, but increase it if a longer outage is to be expected or schedule this step during low-activity hours.
4. Switch over to one Test Agent
   • Start the EgoSecure Server service on the new server. On first start, the cleanup cycle runs automatically and adopts the copied files by updating their ownership in the database.
   • After starting the service, verify in the EgoSecure Server log that the shadow copy files were adopted. Look for a log entry containing "records updated in the SHADOWCOPY table (SERVER field changed)" — the number should match the count of copied files. This confirms the new server has taken ownership of the migrated files.
   • In the Console: Installation → EgoSecure agents → Install/Update. Right-click on the Agent chosen as Test:  Agent → Favorite ShadowCopy Server → select new server.
5. Smoke Test
   • Check old shadowcopies: In the Console under Audit → File access, open a known old file or test "Save as"
   • Check new shadowcopies: On the Test Agent, copy files to USB or network drive and verify that they appear on the new server and can be opened in the Console
   • The following access should be obtainable:
     • Access to the old Shadowcopy files is possible (those created before the migration)
     • Logged new Shadowcopy files can be opened
6. Optional: Switch over a few more Agents, and repeat the Smoke Test.
7. After a successful smoke test, switch all remaining agents to the new server using the same method as the last step in 4.