SQL Server Linux Log Shipping Copy Job Path Issue

Question

SQL Server Linux Log Shipping Copy Job Path Issue

ABDUL HAQ ABDUL LATHEEF 25

A SQL Server log shipping copy job was configured with a Linux path, but an error occurs stating that it cannot find part of the path c:/. How can this issue be resolved?

ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-09-30T08:30:25.8966667+00:00

Answer accepted by question author

Lakshmi Narayana Garikapati 1,330 Microsoft External Staff Moderator

Hi ABDUL HAQ ABDUL LATHEEF,

Thank you for reaching out to SQL forum

Based on the screenshot you shared, here are some troubleshooting steps and workarounds.

Log shipping jobs in SQL Server are OS-dependent, meaning the file system paths used by SQL Server Agent jobs must match the format of the operating system. If SQL Server is running on Linux, it cannot interpret Windows-style paths like C:. and instead expects Linux-style paths such as /var/opt/mssql/logs/.... When a job tries to access a Windows path on a Linux system, it fails because that path doesn’t exist. To resolve this, update the backup folder path in your log shipping configuration to a valid Linux-compatible path like /var/opt/mssql/logshipping/backups. Make sure the SQL Server Agent has the necessary read/write permissions on that path using chmod and chown. Then, modify the copy job settings in SQL Server Management Studio (SSMS) or via T-SQL to reflect the correct Linux path, and check the msdb.dbo.log_shipping_secondary and related tables for any outdated path references. After making these changes, restart the SQL Server Agent to apply the new configuration, and manually run the copy job to confirm the issue is resolved.

https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-use-log-shipping?view=sql-server-ver16

If you have any questions or need further clarification, please don’t hesitate to reach out.

We appreciate your collaboration and support!

Best regards,

Lakshmi.

ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-10-01T06:18:08.56+00:00

Thanks Lakshmi, actually i had followed the document in the link mentioned by you and it was told to specify the backup and source directory to be the same path as the mounted directory in the secondary as depicted in the below

screenshot:

So i felt a bit suspicious about this ,as the error message was not relevant to the situation and since it was a doc from Microsoft i had to rely on this.I tried changing the destination directory to another local directory in the secodnary and all went well ,the issue was solved .

I kindly request microsoft to add a line in this document ,reagrding creating another local directory in the secondary in addition to the samba mount or put up a commnet beside the @backup_destination_directory ,telling that it must be another local directory .So that no one is confused

As far as i understood, the copy job gets confused ,when the source and destination are same and throws this irrelevant error

So to conclude, the follwing solution worked for me

@backup_source_directory ='/var/opt/mssql/tlogs/' -- the shared mount with SAMBA

@backup_destination_directory = any local directory in the secondary with mssql as the owner with read and write privileges

Again ,thanks for your response in this regard
Lakshmi Narayana Garikapati 1,330 Reputation points Microsoft External Staff Moderator

2025-10-01T10:30:07.7266667+00:00

Hi, ABDUL HAQ ABDUL LATHEEF

Glad to hear that your issue is resolved, and thanks for the confirmation.

Thank you for your suggestion. We will notify the respective team to update the Documentation as per your suggestions.

If this post helped resolve your issue, please consider marking it as the Accepted Solution. It also helps other community members find relevant answers more easily

We appreciate your collaboration and support!

Best Regards,

Lakshmi.
ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-10-06T10:40:28.3433333+00:00

@Lakshmi Narayana Garikapati I am not able to mark my own answer as acceptable Kindly do the need ful

1 additional answer

Your answer

ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-09-30T08:30:25.8966667+00:00
ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-10-01T06:18:08.56+00:00

Thanks Lakshmi, actually i had followed the document in the link mentioned by you and it was told to specify the backup and source directory to be the same path as the mounted directory in the secondary as depicted in the below

screenshot:

So i felt a bit suspicious about this ,as the error message was not relevant to the situation and since it was a doc from Microsoft i had to rely on this.I tried changing the destination directory to another local directory in the secodnary and all went well ,the issue was solved .

I kindly request microsoft to add a line in this document ,reagrding creating another local directory in the secondary in addition to the samba mount or put up a commnet beside the @backup_destination_directory ,telling that it must be another local directory .So that no one is confused

As far as i understood, the copy job gets confused ,when the source and destination are same and throws this irrelevant error

So to conclude, the follwing solution worked for me

@backup_source_directory ='/var/opt/mssql/tlogs/' -- the shared mount with SAMBA

@backup_destination_directory = any local directory in the secondary with mssql as the owner with read and write privileges

Again ,thanks for your response in this regard
Lakshmi Narayana Garikapati 1,330 Reputation points Microsoft External Staff Moderator

2025-10-01T10:30:07.7266667+00:00

Hi, ABDUL HAQ ABDUL LATHEEF

Glad to hear that your issue is resolved, and thanks for the confirmation.

Thank you for your suggestion. We will notify the respective team to update the Documentation as per your suggestions.

If this post helped resolve your issue, please consider marking it as the Accepted Solution. It also helps other community members find relevant answers more easily

We appreciate your collaboration and support!

Best Regards,

Lakshmi.
ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-10-06T10:40:28.3433333+00:00

@Lakshmi Narayana Garikapati I am not able to mark my own answer as acceptable Kindly do the need ful

Answer 1

ABDUL HAQ ABDUL LATHEEF 25

@backup_source_directory ='/var/opt/mssql/tlogs/' -- the shared mount with SAMBA

@backup_destination_directory = any local directory in the secondary with mssql as the owner with read and write privileges

Lakshmi Narayana Garikapati 1,330 Reputation points Microsoft External Staff Moderator

2025-10-06T10:21:59.98+00:00

Hi @ABDUL HAQ ABDUL LATHEEF,

We’d like to confirm whether your issue has been successfully resolved. If you still have any questions or need further assistance, please don’t hesitate to reach out. We’re more than happy to continue supporting you.

We appreciate your engagement and thank you for being an active part of the community.

Best Regards,

Lakshmi.
ABDUL HAQ ABDUL LATHEEF 25 Reputation points

2025-10-06T10:27:50.5966667+00:00

Hi @Lakshmi Narayana Garikapati

First of all thanks a lot for reaching out ,yes my issue has been resolved after making the above mentioned changes for the Destination directory
Lakshmi Narayana Garikapati 1,330 Reputation points Microsoft External Staff Moderator

2025-10-06T10:34:07.05+00:00

ABDUL HAQ ABDUL LATHEEF ,

Thanks for the conformation, consider marking it as the Accepted answer. It also helps other community members find relevant answers more easily

Best Regards,

Lakshmi.

Share via

SQL Server Linux Log Shipping Copy Job Path Issue

1 additional answer

Your answer