Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups

  • Home
  • Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups

Solution Draft : After doing many hours of research, I found out that only Synology is offering a very straightforward yet stable backup solution for Microsoft 365. There were couple of other options such as VEEAM which is cloud based and costly. But there was another hiccup. Synology devices are also quite pricy and you can not use the hardware provided by Synology for any other extensive server related workload. But Synology is offering their DSM which stands for Disk Station Management software as a (kind of) open source platform called Xpenolgy. Xpenology can be installed on any hardware which would meet the basic hardware requirements needed by the DSM software. Due to this reason I decided to go for a refurbished HP Microserver Gen10+ as it is cost effective and much more powerful than a stand alone Synology.

Hardware Used : HP Microserver Gen10+ (iLO Card installed and enabled, 32 GB DDR4 RAM, 12TB HDD, 2 x 3 TB HDD(all the hard disk in SATA mode, not using a SAS card) – check “How to setup your HP Microserver Gen10+”

Software Used :

  • Proxmox VE PVE 7.0-11
  • DSM 6.2.3
  • 365 Active Backups (app inside DSM)

Working Environment : Mac OS Big Sur

1. Installing Proxmox,

please refer to the article “How to install Proxmox on HP Microserver Gen10+” and “Top 10 things to do after installing Proxmox”

2. Installing DSM on Proxmox.

This is a very tricky process as you should know which version of DSM you should install depending on the need you have. In my case the need was to run 365 Active Backups. For this app it required a + version of Synology, and since we are installing DSM as a virtual machine you should download a VM image which is generated from a + Synology.

You could easily download it from this link –>

https://mega.nz/folder/pmIxgYpB#SJrffUPeivisM89a69VMDw/folder/1rpk1aBD

I have marked the exact version I downloaded from the link above.

2.1 Transferring the VZDump Image to Proxmox

In order to restore the downloaded image, you need to upload the image to your proxmox’s backup destination. In my case I used rsync in the Mac terminal and the code is as follows

 rsync -avz vzdump-qemu-xpenology-918-6.2.3_25426.vma.lzo root@192.168.1.10:/var/lib/vz/dump

You have to go to the folder where the download is located(via the terminal i.e. cd ~/Downloads) in order to initiate the command. You will be prompted for the root password and it should synchronise in a minute. Make sure to change the IP address in the above example to your Proxmox server’s IP.

2.2 Restoring the Image file

Restoring is a quite straight forward process, once the image is uploaded it should appear in your proxmox server like this

Once you click on the Restore button make sure to select your local storage as the storage option. It selects the backup configured storage option as default but this could throw errors.

If the recovery is succesfull you should be seeing the output window like below, with the message, “TASK OK”. You can close the console at this point.

Now you should see a VM created in the sidebar with the name “XPenology-TMP-ds918” and you can start up the VM to see weather its running

2.3 HDD Passthrough

Now since we have managed to restore the DSM image and after ensuring its accessible via the web, we need to make sure that we pass through the HDD to DSM in order to create a a storage volume in DSM.

Check this article on “How to do an HDD Passthrough on Proxmox

Problem : My client’s organisation running on Microsoft 365 but they need to have a cost effective local backup system in place just to avoid any data loss on server outages.

Solution Draft : After doing many hours of research, I found out that only Synology is offering a very straightforward yet stable backup solution for Microsoft 365. There were couple of other options such as VEEAM which is cloud based and costly. But there was another hiccup. Synology devices are also quite pricy and you can not use the hardware provided by Synology for any other extensive server related workload. But Synology is offering their DSM which stands for Disk Station Management software as a (kind of) open source platform called Xpenolgy. Xpenology can be installed on any hardware which would meet the basic hardware requirements needed by the DSM software. Due to this reason I decided to go for a refurbished HP Microserver Gen10+ as it is cost effective and much more powerful than a stand alone Synology.

Hardware Used : HP Microserver Gen10+ (iLO Card installed and enabled, 32 GB DDR4 RAM, 12TB HDD, 2 x 3 TB HDD(all the hard disk in SATA mode, not using a SAS card) – check “How to setup your HP Microserver Gen10+”

Software Used :

  • Proxmox VE PVE 7.0-11
  • DSM 6.2.3
  • 365 Active Backups (app inside DSM)

Working Environment : Mac OS Big Sur

1. Installing Proxmox,

please refer to the article “How to install Proxmox on HP Microserver Gen10+” and “Top 10 things to do after installing Proxmox”

2. Installing DSM on Proxmox.

This is a very tricky process as you should know which version of DSM you should install depending on the need you have. In my case the need was to run 365 Active Backups. For this app it required a + version of Synology, and since we are installing DSM as a virtual machine you should download a VM image which is generated from a + Synology.

You could easily download it from this link –>

https://mega.nz/folder/pmIxgYpB#SJrffUPeivisM89a69VMDw/folder/1rpk1aBD

I have marked the exact version I downloaded from the link above.

2.1 Transferring the VZDump Image to Proxmox

In order to restore the downloaded image, you need to upload the image to your proxmox’s backup destination. In my case I used rsync in the Mac terminal and the code is as follows

 rsync -avz vzdump-qemu-xpenology-918-6.2.3_25426.vma.lzo root@192.168.1.10:/var/lib/vz/dump

You have to go to the folder where the download is located(via the terminal i.e. cd ~/Downloads) in order to initiate the command. You will be prompted for the root password and it should synchronise in a minute. Make sure to change the IP address in the above example to your Proxmox server’s IP.

2.2 Restoring the Image file

Restoring is a quite straight forward process, once the image is uploaded it should appear in your proxmox server like this

Once you click on the Restore button make sure to select your local storage as the storage option. It selects the backup configured storage option as default but this could throw errors.

If the recovery is succesfull you should be seeing the output window like below, with the message, “TASK OK”. You can close the console at this point.

Now you should see a VM created in the sidebar with the name “XPenology-TMP-ds918” and you can start up the VM to see weather its running

2.3 HDD Passthrough

Now since we have managed to restore the DSM image and after ensuring its accessible via the web, we need to make sure that we pass through the HDD to DSM in order to create a a storage volume in DSM.

Check this article on “How to do an HDD Passthrough on Proxmox

Problem : My client’s organisation running on Microsoft 365 but they need to have a cost effective local backup system in place just to avoid any data loss on server outages.

Solution Draft : After doing many hours of research, I found out that only Synology is offering a very straightforward yet stable backup solution for Microsoft 365. There were couple of other options such as VEEAM which is cloud based and costly. But there was another hiccup. Synology devices are also quite pricy and you can not use the hardware provided by Synology for any other extensive server related workload. But Synology is offering their DSM which stands for Disk Station Management software as a (kind of) open source platform called Xpenolgy. Xpenology can be installed on any hardware which would meet the basic hardware requirements needed by the DSM software. Due to this reason I decided to go for a refurbished HP Microserver Gen10+ as it is cost effective and much more powerful than a stand alone Synology.

Hardware Used : HP Microserver Gen10+ (iLO Card installed and enabled, 32 GB DDR4 RAM, 12TB HDD, 2 x 3 TB HDD(all the hard disk in SATA mode, not using a SAS card) – check “How to setup your HP Microserver Gen10+”

Software Used :

  • Proxmox VE PVE 7.0-11
  • DSM 6.2.3
  • 365 Active Backups (app inside DSM)

Working Environment : Mac OS Big Sur

1. Installing Proxmox,

please refer to the article “How to install Proxmox on HP Microserver Gen10+” and “Top 10 things to do after installing Proxmox”

2. Installing DSM on Proxmox.

This is a very tricky process as you should know which version of DSM you should install depending on the need you have. In my case the need was to run 365 Active Backups. For this app it required a + version of Synology, and since we are installing DSM as a virtual machine you should download a VM image which is generated from a + Synology.

You could easily download it from this link –>

https://mega.nz/folder/pmIxgYpB#SJrffUPeivisM89a69VMDw/folder/1rpk1aBD

I have marked the exact version I downloaded from the link above.

2.1 Transferring the VZDump Image to Proxmox

In order to restore the downloaded image, you need to upload the image to your proxmox’s backup destination. In my case I used rsync in the Mac terminal and the code is as follows

 rsync -avz vzdump-qemu-xpenology-918-6.2.3_25426.vma.lzo root@192.168.1.10:/var/lib/vz/dump

You have to go to the folder where the download is located(via the terminal i.e. cd ~/Downloads) in order to initiate the command. You will be prompted for the root password and it should synchronise in a minute. Make sure to change the IP address in the above example to your Proxmox server’s IP.

2.2 Restoring the Image file

Restoring is a quite straight forward process, once the image is uploaded it should appear in your proxmox server like this

Once you click on the Restore button make sure to select your local storage as the storage option. It selects the backup configured storage option as default but this could throw errors.

If the recovery is succesfull you should be seeing the output window like below, with the message, “TASK OK”. You can close the console at this point.

Now you should see a VM created in the sidebar with the name “XPenology-TMP-ds918” and you can start up the VM to see weather its running

2.3 HDD Passthrough

Now since we have managed to restore the DSM image and after ensuring its accessible via the web, we need to make sure that we pass through the HDD to DSM in order to create a a storage volume in DSM.

Check this article on “How to do an HDD Passthrough on Proxmox

1 Comments:

  1. Lorem Ipsum has been the industry’s standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen.

Leave a Reply

Your email address will not be published.

Let’s Talk About How Can Help You Securely Advance

Get A Free Quote
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups
Installing DSM(Xpenology) on Proxmox VE(PVE) for MS 365 Active Backups

Our Valuable Clients