Hello Luca! It sounds like you're encountering a challenge with azcopy sync when trying to backup files with the .vhd extension, which are being excluded due to their association with Virtual Hard Disks, even though in your case, they represent VHDL coding language files. To include .vhd files in your azcopy sync operation, you can use the --include-pattern parameter to specifically include these files. While azcopy sync doesn't have a direct parameter to override the exclusion of .vhd files based on their extension alone, using include patterns can help ensure they're considered for synchronization.
Here's a general approach to include .vhd files in your azcopy operations: Using --include-pattern You can specify patterns for the files you want to include in your synchronization or copy operation. To include .vhd files, you can use the --include-pattern parameter followed by the pattern matching your VHDL files. For example: bash Copy code azcopy sync '<source-path>' '<destination-path>' --include-pattern "*.vhd" This command tells azcopy to sync all files that match the pattern .vhd from the source to the destination. It's important to ensure that your pattern accurately reflects the files you intend to include to avoid inadvertently excluding other necessary files. Note on --blob-type
For the azcopy copy command, when dealing with files that Azure might interpret differently based on their extension (like .vhd files for blobs), specifying the --blob-type parameter can be crucial. For non-disk-related files, you might use: bash Copy code azcopy copy '<source-path>' '<destination-path>' --blob-type BlockBlob --include-pattern ".vhd" This explicitly sets the blob type as BlockBlob and includes files matching the .vhd pattern, helping to ensure that your VHDL files are treated as regular blob files rather than virtual hard disks.
Additional Considerations Wildcards: The --include-pattern accepts wildcards, allowing for flexible file selection. Use this to your advantage for specifying multiple file types or naming conventions. Exclusion Rules: If there are other file types or specific files you wish to exclude, you can also use the --exclude-pattern parameter in conjunction with --include-pattern for finer control over what gets synchronized. Testing: Before running your final azcopy sync command on your entire dataset, consider testing with a smaller set of files or using the --dry-run option (if available) to review what actions azcopy would take without actually transferring any files. This can help ensure your command is correctly set up. Just be carefully crafting your azcopy command with the right parameters, you should be able to include your VHDL .vhd files in your backup or synchronization processes without them being mistakenly excluded.
I hope this helps? If you have any questions please let me know.