Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azcopy doesn't recognize CNAME or the privatelink URI of the FILE uri #2893

Open
IfthikharAhamed opened this issue Dec 16, 2024 · 3 comments

Comments

@IfthikharAhamed
Copy link

I am trying to figure out a work around for the cross regional copy of AFS resource with multiple PE (one on the source VNET and another on DEST VNET). Due to the DNS issue having multiple PE, I am trying out to use a CNAME app.company.net instead of the file.core.windows.net,

The azcopy doesn't recognize the CNAME or the privatelink.core.file.windows.net DNS and failing as below.

Cannot perform sync due to error: trying to sync between different resource types (either file <-> directory or directory <-> file) which is not allowed.sync must happen between source and destination of the same type, e.g. either file <-> file or directory <-> directory.To make sure target is handled as a directory, add a trailing '/' to the target.

@IfthikharAhamed IfthikharAhamed changed the title Azcopy doesn't recognize CNAME or the privatelink URI of the BLOB uri Azcopy doesn't recognize CNAME or the privatelink URI of the FILE uri Dec 16, 2024
@vibhansa-msft
Copy link
Member

AzCopy detects the storage type and couple of other things based on the URL so if the URL does not contain ".blob.core.windows.net" or ".file.core.windows.net" the copy/sync jobs will not work.

@gapra-msft
Copy link
Member

@IfthikharAhamed Does setting the --from-to CLI parameter not work?

@IfthikharAhamed
Copy link
Author

even with the --from-to cli i am getting the same error:

Tried with the privatelink.file.core.net & custom DNS name .myapp.local.am.net

ERROR:
Get "https://testingaccount.myapp.local.am.net/fileshare002?restype=share&se=2024-12-19": x509: certificate is valid for *.file.core.windows.net, *.file.storage.azure.net, *.z1.file.storage.azure.net, *.z2.file.storage.azure.net, *.z3.file.storage.azure.net, *.z4.file.storage.azure.net, *.z5.file.storage.azure.net, *.z6.file.storage.azure.net, *.z7.file.storage.azure.net, *.z8.file.storage.azure.net, *.z9.file.storage.azure.net, *.z10.file.storage.azure.net, *.z11.file.storage.azure.net, *.z12.file.storage.azure.net, *.z13.file.storage.azure.net, *.z14.file.storage.azure.net, *.z15.file.storage.azure.net, *.z16.file.storage.azure.net, *.z17.file.storage.azure.net, *.z18.file.storage.azure.net, *.z19.file.storage.azure.net, *.z20.file.storage.azure.net, *.z21.file.storage.azure.net, *.z22.file.storage.azure.net, *.z23.file.storage.azure.net, *.z24.file.storage.azure.net, *.z25.file.storage.azure.net, *.z26.file.storage.azure.net, *.z27.file.storage.azure.net, *.z28.file.storage.azure.net, *.z29.file.storage.azure.net, *.z30.file.storage.azure.net, *.z31.file.storage.azure.net, *.z32.file.storage.azure.net, *.z33.file.storage.azure.net, *.z34.file.storage.azure.net, *.z35.file.storage.azure.net, *.z36.file.storage.azure.net, *.z37.file.storage.azure.net, *.z38.file.storage.azure.net, *.z39.file.storage.azure.net, *.z40.file.storage.azure.net, *.z41.file.storage.azure.net, *.z42.file.storage.azure.net, *.z43.file.storage.azure.net, *.z44.file.storage.azure.net, *.z45.file.storage.azure.net, *.z46.file.storage.azure.net, *.z47.file.storage.azure.net, *.z48.file.storage.azure.net, *.z49.file.storage.azure.net, *.z50.file.storage.azure.net, not testingaccount.myapp.local.ama.net
goroutine 1 [running]:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants