QNAP NAS: Create Backup of TimeMachine Directory

I was recently setting up remote backups for my QNAP NAS and came across a problem.

QNAP NAS by default doesn’t seem to be able to create backups of the TMBackup directory it uses to store TimeMachine backups. You are unable to sync this directory with remote server or cloud storage/backup service.

I was googling around and noticed that few people had this problem, for example here and I have found a solution.

My Setup

I have NAS with 2 volumes, first volume is used for multimedia (this one backups fine), second volume is used for TimeMachine backups (this one doesn’t work).


When creating remote (cloud) backups of files on my NAS TimeMachine volume doesn’t appear on the list:


This problem can be solved by creating a new “Shared Folder” and pointing it to /.timemachine (the location of TM backups).

After that, go back to “Hybrid Backup Sync” to setup “Sync Job”.

Your newly created folder will be visible with TM backups as content.

How to use Trezor Wallet with Bitcoin Testnet

The following post is a quick tutorial how to use Trezor hardware wallet with Bitcoin Testnet.

Connect your Trezor like you normally would

Click on “Wallet settings”

Delete contents of this field and enter “https://testnet-bitcore1.trezor.io/” instead

Click “Save & Reload”

This is how the wallet page should look

Notice that in the right left corner it says “Custom backend”, this is expected. I already have 0.20 testnet BTC there.

This is how “Receive” tab looks like, there is information that you are running on testnet

This is how “Send” tab looks like, there is information that you are running on testnet

Unfortunately there’s no way for the Trezor wallet to remember this setting and you are required to repeat those steps every time you plug in your wallet into computer.

Using Swagger UI For Local Development

When working on the swagger documentation, several different tools can be used.

The ‘official’ editor developed by the Swagger community is Swagger Editor, live preview: https://editor.swagger.io/, I have found it quite quick and easy to use, but for larger project it gets cumbersome. Additionally it doesn’t support ability to have multiple files that will reference each other.

This post is a quick demonstration of the workflow I’m using when working on the large, multi-file swagger documentations. It’s certainly not ideal but it helps me to get the job done.

Here it is:

Edit swagger.yaml

This file can be edited in any editor of choice, the yaml format is widely supported. The documentation can be split up into multiple files that reference each other. I use this functionality to extract examples and other JSON documents. Referencing other files is explained quite well in this post How to split a Swagger spec into smaller files

Publish swagger.yaml locally

In order to view swagger.yaml inside Swagger UI the file can be either referenced by a regular file system reference, or it can be fetched via HTTP.

I use local HTTP server to expose swagger.yaml (with all other, referenced files)

Here I’m using http-server from npm but you can use any HTTP server, make sure to disable caching and CORS

Run Swagger UI

The last component, Swagger UI can be started like this:

After viewing http://localhost:1111 Swagger UI will display the generated documentation

Now, every time you make a change swagger.yaml or any file it’s enough to refresh web page to see the changes (or validation errors if there are some)


This method is more involved that alternatives like Swagger Editor or simply running Swagger UI with file referenced by regular file system reference (possibly outside Docker), but overcomes 2 major limitations of those tools, with it you’ll be able to:

  • Not pollute your environment with different tools when Docker container will work
  • Ability to edit swagger documentation that consist of multiple files (either JSON or YAML)
  • Quick feedback loop, simply refresh web page to see the changes in swagger docs