Forum Discussion
Open Mirroring - Replication not restarting for large tables
Hello,
I am running a test of open mirroring and replicating around 100 tables of SAP data. There were a few old tables showing in the replication monitor that were no longer valid, so I tried to stop and restart replication to see if that removed them (it did).
After restarting, only smaller tables with 00000000000000000001.parquet still in the landing zone started replicating again. All larger tables, that had parquet files > ...0001 would not resume replication. Once I moved the original parquets from the _FilesReadyToDelete folder, they started replicating again.
I assume this is a bug? I cant imagine you would be expected to reload all parquet files after stopping and resuming replication. Luckily all of the preceding parquet files still existed in the _FilesReadyToDelete folder, but I assume there is a retention period?
Thank you for reaching out to Microsoft Fabric Community Forum.
Report this to Microsoft via a Fabric support ticket. Include logs and table names/sizes if possible.
Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay Pabbu
3 Replies
I have the same issue.
Thank you for reaching out to Microsoft Fabric Community Forum.
Report this to Microsoft via a Fabric support ticket. Include logs and table names/sizes if possible.
Microsoft will analyze backend logs and provide a resolution
Below is the link to create Microsoft support ticket:
https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
If this post helps, then please consider Accepting as solution to help the other members find it more quickly, don't forget to give a "Kudos" – I’d truly appreciate it!
Regards,
Vinay PabbuThank you Vinay. I will create a support ticket.
