Azure File Service on linux

You can now using azure file services to make large drives and mount them to linux server. When i was testing, it was available for many windows versions and very few version of linux.

Linux VMs deployed on Azure can make use of this service using the Linux Kernel CIFS client. The kernel client must be configured to support and use the SMB 2.1 protocol dialect:

CONFIG_CIFS_SMB2 must be enabled in the kernel configuration at build time
# zcat /proc/config.gz | grep CONFIG_CIFS_SMB2
to check this on a running system.
The vers=2.1 mount.cifs parameter must be provided at mount time.
Furthermore, the Azure storage account and access key must be provided as username and password.

# mount.cifs -o vers=2.1,user=smb // /share/
Password for smb@// ******…
# df -h /share/
Filesystem Size Used Avail Use% Mounted on
// 5.0T 0 5.0T 0% /share


using @ as CNAME

you can’t make the @ record a CNAME without deleting all other resource records for @, and you can’t do that since some (like the NS records) are required for proper DNS functionality.
You will need a host to perform the HTTP redirection from to for you, to which you will point A (and AAAA) record for @.

If your DNS is hosted with GoDaddy, then they have a free service that will do this for you. In your GoDaddy domain manager, look on the left hand side for “Forwarding” and click “Manage”. Then set it to forward to and update your DNS to support the change. You should leave the Advanced Options at their defaults.

External Connection to a Windows Azure VM SQL Server

1. Within Windows Azure, navigate to ‘ENDPOINTS’ and Select ‘ADD’ at the bottom of the page.

2. You will need to open up a port in order to allow access to the instance of SQL Server. I’m going to stick with the default port of 1433 and create a new endpoint here. Make sure Both Check boxes (circled below) are NOT ticked

3. Next up we need to configure the firewall on the server itself. Open an RDP session and log into the Azure VM. Open Control Panel > Windows Firewall and configure a new inbound rule in the Windows firewall for port 1433:

4. Select a rule type of ‘Port’. The default port for SQL Server is 1433 but this can be different depending on how the SQL Server properties have been set up. Simply type ‘tcp setting for SQL Server’ in a search engine and this will tell you where to find or change the port number.

After clicking next, the options are as follows:

· Select TCP and specify port 1433

· Next, select ‘Allows This Connection’

· Then, select when you want the rule applied – typically ‘Public.’ This will enable external connection to the port.

· Lastly, assign this rule a name (e.g SQL Port)

5. The next step is to verify that SQL Server is enabled to use the TCP protocol. Ensure that ‘Named Pipes’ is set to DISABLED. You can do all these settings by using SQL configuration manager.

6. Check that SQL Server is configured to use mixed mode authentication. Right Click on the server (within SSMS) and toggle to the ‘Security’ page and verify that the radio button ‘SQL Server and Windows Authentication Mode’ is selected.

7. Create a test login

8. Restart the SQL Server. It is important the service is restarted, otherwise, any changes to the tcp or pipelines will n bot have been committed.

9. The final step is to login in from your local SSMS. Specify the full server name (taken from Azure) and the new user credentials created.

Backup Blob to another Blob

Select-AzureSubscription “SubscriptionName”

# I am making a VHD backup – VHD blob to copy #
$blobName = “1436836594602.vhd”

# Source Storage Account Information #
$sourceStorageAccountName = “SomeName”
$sourceKey = “SourcePrimaryKey”
$sourceContext = New-AzureStorageContext –StorageAccountName $sourceStorageAccountName -StorageAccountKey $sourceKey
$sourceContainer = “vhds”

# Destination Storage Account Information #
$destinationStorageAccountName = “Backupprodvmdiskfiles”
$destinationKey = “DestinationPrimaryKey”
$destinationContext = New-AzureStorageContext –StorageAccountName $destinationStorageAccountName -StorageAccountKey $destinationKey

# Create the destination container #
$destinationContainerName = “vhds”
New-AzureStorageContainer -Name $destinationContainerName -Context $destinationContext

# Copy the blob #
$blobCopy = Start-AzureStorageBlobCopy -DestContainer $destinationContainerName `
-DestContext $destinationContext `
-SrcBlob $blobName `
-Context $sourceContext `
-SrcContainer $sourceContainer

while(($blobCopy | Get-AzureStorageBlobCopyState).Status -eq “Pending”)
Start-Sleep -s 30
$blobCopy | Get-AzureStorageBlobCopyState