Using shared VHDx for guest clustering on a storage with no support for Microsoft Cluster & virtualization

Hi everybody,

last weekend my friend Udo Walberer and I had some struggles when setting up a guest cluster with shared VHDx as cluster volumes. We weren’t able to get it work.

We were able to connect the VHDx and to configure it as cluster volume but after a reboot the VMs weren’t starting and we get following failure:



So after some research wie figured out that the storage which he was using had no support for Microsoft Clustering and Virtualisation as well as Persistent Reservation. After we tested on a supported storage all was fine.

So please before you try to use shared VHDx, check if you storage is supported for some options.

The two screenshots below show you two synology storages, first one without those support and second with support.





How to setup Azure Backup with Synology Storage

Hello everybody,

today I want to show you how to setup a disk to cloud backup with the new cloud backup feature from synology storage. In my environment I use Azure as backup target.

Why do I use Azure?

I backup some of my important VMs to Azure as desaster recovery. So if my local systems fail I fire up the VMs in Azure.


1. You need to create a new Azure Storage were you store your data. From a security standpoint I would not suggest to use a storage shared with other Azure services you have.




2. After you created one you need to create a new management access key. We will need it later.


3. Now the needed preparations on Azure are done. Next Logon to your Synology and select the Backup & Replication Plugin.


4. Now you click create and select the backup typ you want.

File Backup – You can select Files and Folder you want to backup.

LUN Backup – Backups a complette LUN on Synology LUN on Azure



5. Now you select “Public Cloud Backup Destination”


6.  Now you select Backup to Azure


7. Now you enter your Azure Storage account data and create a new storage container


8. Now enter your container name you want to use



9. When everything went well it should look like on the picture below




10. In the next step you need to select the volume and share or LUN you want to backup




11. Here you can also select applications to backup. I won’t do that in my szenario.




12. In the last step you need to do transfer, backup and shedule settings.









Synology configuration for max. IOPS with Hyper-V

Hello everybody,

as most of you know I’m using a Synology DS1813+ as storage for my testlab. Last week I took some time to change my configuration to improve the IOPS for my Hyper-V Systems.

My old configuration with RAID 10 and Block based iSCSI LUNs only brought about 6000 IOPS, so I needed to improve to get more VMs up.


Let us start with the Hardwareconfiguration. I’m using a DS1813+ with 8 Disk splitted as followed.

Disktyp Count Capacity HD Vendor & Typ Disk Role
SSD 2 120 GB Kingston SV300S37A120G Cache
HDD SATA 7.200 RPM 6 1000 TB 2x Seagate ST1000DM003-1ER162
3x Seagate ST1000DM003-1CH162
1x Seagate ST31000524AS

I connected three 1 Gbit/s ports with MPIO to my SAN network. So there should be enough bandwidth.


My disk are configured as followed:

The SSDs are configured as Cache Volume for our later Hyper-V VM Volume. When you configure the SSC Chache choose “Read-Write”.



Now back to the harddrives. You should configure RAID 10 for the disks. You can use RAID 5 too if you need the capacity but you will lose at least 1/3 of the final performance.




Now you need to create the volume for you VMs. Here comes the point were I lose some performance because I need to create milti volumes on one RAID. For more performance you should choose single volume on RAID but you cannot use the disk any longer for more volumes.



The volume must be configured with LUN allocation unit size 4KB for Windows ODX.



Now you create the iSCSI Volume and Target. Here you choose regular files and advanced LUN features. If do not use thin provisioning, you will get some more IOPS too but that does not matter.




So that’s all you need to do on the storage. Next you need fomat the drive. Here I would suggest to format the driver with NTFS and 4KB unit size.




As a resulte I got a max. from nearly 12.000 IOPS out of my Synology DS1813+ 🙂  Not bad for are SOHO Diskarray 😉





[huge_it_slider id=”6″][huge_it_slider id=”7″]


How to sync Synology Storage with Microsoft OneDrive


last week I investigated some new features from Synology DSM 5.1. One of the features is synchronisation to Microsoft OneDrive, Box etc.

Today I want to show you how you can configure the sync. I’m using a Synology DS115j for my test and have a DS1813+ for production.

1. You need to create a new user. I would suggest to create a separet user for the synchronisation.


2. Now you need to create a shared folder for the OneDrive files. I would suggest to create an additional volume too.



3. The user you created to manage the synchronisation musst have Read/Write on the share and on the NTFS / Advanced Share Permissions.



4. Now you need to install the Plugin. It is named Cloud Sync and you will find it in you Package Center.



5. After the Plugin is installed you can open it via “Start Menu”.


6. Now you should follow the Wizzard. First select your cloud service you want to connect too. In my case OneDrive.



7. Enter your credentials to connect to your account. For OneDrive you need your Microsoft Account.


8. You need to agreed the access to your accountsetting.



9. Now you need to select the local sync folders you want to sync to.




10. After you selected the folder it should look like the picture below.



11. In the next step you need to select your folders that should be available on your Synology.


12. After you selected the folders, the following message should pop up.


13. After you setup the sync, the initial sync starts.


Depending on your use, that may take a while. Attention!!! During the syncronisation you will notice a high CPU load of you synology. 


[huge_it_slider id=”6″]

Synology now supports Offsite Backup with Azure

As Microsoft Azure becomes more liked within industry and private field, Synology now supports off-site backup to Azure.

If you want to use these feature, you need to update to DSM 5.1 version.


Data backup

Protect your data, just the way you like

When it comes to off-site backup, cloud storage is playing an essential role in home and business backup strategies. With DSM 5.1, you can now back up data directly to Microsoft Azure, SFR, and hicloud. Plus, the new Explore feature for Glacier Backup makes it easier and cheaper than ever to retrieve single files from Amazon Glacier.

In addition, DSM 5.1 brings more flexible options for managing backup permissions, schedulable iSCSI LUN snapshots, broader support for package backup, as well as a performance boost up to 169% for LUN backup.

[huge_it_slider id=”6″][huge_it_slider id=”7″]