@Moonlight
Firstly I recommend reading through Planning for an Azure File Sync deployment and Deploy Azure File Sync which should cover the majority of these questions and many others you might have.
- If you don't have extra storage for initial onboarding and would like to attach to the existing shares, you can pre-seed the data in the Azure files shares over SMB or with AzCopy. This approach is suggested, if and only if you can accept downtime and absolutely guarantee no data changes on the server shares during the initial onboarding process. Another option is using Azure DataBox to migrate the files offline.
- This is not required. The Azure File Sync agent communicates with your Storage Sync Service and Azure file share using the Azure File Sync REST protocol and the FileREST protocol, both of which always use HTTPS over port 443. For more info refer to Azure File Sync networking considerations.
- To protect the data in your Azure file shares against data loss or corruption, all Azure file shares store multiple copies of each file as they are written. Depending on the requirements of your workload, you can select additional degrees of redundancy. If you wish to backup Azure files you can use Azure file share backup.
- I would recommend starting with a hot tier and if necessary you can switch to transaction optimized or cool tier if necessary. See Storage tiers section for more information.
Hopefully this response and the linked articles answer all your questions. If you have further questions or issues please let us know.
Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.