Synology Hyper Backup can backup to WebDAV servers. Stack has support for WebDAV but They don’t seem to like each other. If you follow a few Dutch forum threads  (1 2 ). Users mention that the use of Sparse files is the problem. Hyper Backup creates a Sparse file in WebDAV backups in nas_1.hbk/Pool/bucketID.counter.1

The filename tells us that it’s used as a counter. After creation of the backup task it seems to be empty (I tested this with another WebDAV server 😉 ). If we manually try to upload this file to Stack we receive an error. “Method not allowed”

So, let’s see what is actually in this file. Well it’s empty…


gijs@Carbonite:~$ hexdump -C bucketID.counter.1
 00000000 00 00 00 00 00 00 00 00 |........|

After creating the backup task, this file is empty but as soon as the backup runs the file will be replaced with another one. When I check the contents of this new file it was not empty.


gijs@Carbonite:~$ hexdump -C bucketID.counter.3
 00000000 00 00 00 00 00 00 01 5e |.......^|

Uploading this new file is accepted by Stack. Below I will guide you through the steps to get Hyper Backup use Stack as a backup destination.

Step 1: Have another WebDAV server

Before we can create a backup to Stack we need a separate WebDAV server that supports the use of Sparse files.
This can be remote or local with the WebDAV server package.
I choose to use the local package.

Step 2: create a WebDAV backup task to this server.

Create a new backup task and select the server from step 1 as the destination.

  • The server address should be the address of your WebDAV server (in my case the Synology itself)
  • The folder needs to be the folder you like to use on Stack (you may need to create a temporary folder on your WebDAV server.)


After clicking Next you can choose the folders you want to backup and all the options you like to use. It’s not important for now so I don’t cover it here.

Hyper Backup will ask if you like to create a backup now. Click NO.


Step 3: Copy files to Stack

Upload the complete nas_1.hbk directory to Stack in the folder with the same name as in step 2. Stack will not accept the file nas_1hbk/Pool/bucketID.counter.1 but you can skip it.

In my situation my folder in Stack was:  stack_backup > nas_1.hbk

Step 4: Edit the backup task

Go to your Stack settings page and copy the WebDAV url:

In Hyper Backup: Edit the backup task by clicking on the menu and then Edit.


Open the Target tab and replace the current values with those from your Stack account.


Click OK and Hyper Backup will recognize the backup task at your Stack storage 🙂

I have tested the following and they all work fine:

  • Initial backup (17GB)
  • Adding a file and doing an incremental backup
  • Recovering 1 file
  • Recovering the complete folder (17GB)


Note: Having a decent backup plan is important. Test your backups and have multiple destinations. Also Off-line.

21 thoughts on “Make Synology <3 TransIP Stack

    1. I had the same problem. It went wrong during copying the BACKUP.hbk to Stack. What I did is downloaded the hbk folder to from my NAS, deleted the bucketID.counter.1 file from the pool folder and uploaded the hbk folder to stack. After that, my backup came online again.
      Maybe it helps….

      Liked by 1 person

  1. It seems the local NAS username and the remote TransIP username password combination needs to be the same. Otherwise you cannot modify the Hyper backuptask I found.


  2. I cannot seem to get the connection to work. I can create a folder, but when I want to apply the task, I get the error: Insufficient privileges to access this destination shared folder


  3. Does not work for me, even not after having same user and password and deleting the mentioned counter file and even not after deleting all 0 byte files.


  4. I had trouble getting this to work. The file I downloaded from the temp webdav server was a zip file. It was not clear to me that I needed to extract it and place the extracted folder onto stack.
    After doing that it worked immediately.
    Thank you for the information.


  5. De afgelopen twee jaar kijk ik eens in de paar maanden of er een oplossing is. Teleurstellend dat TransIP niet hier actie op heeft ondernomen, maar geweldig dat jij het probleem hebt gehackt en deelt! Veel dank Gijs, ik ben hier erg blij mee


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s