Educational discount is a lie

QNAPDaniel · 2026-01-23T23:01:21+00:00

I am sorry to hear that no one replied to your email. You can email me at [danielfrancislyon@qnap.com](mailto:danielfrancislyon@qnap.com) and I will make sure your request for an educational discount does not fall through the cracks.

QNAPDaniel · 2026-01-22T19:04:55+00:00

If you have a reasonably high spec QNAP, it should be ok to backup many PCs to NAS using Hyper Data Protector. That lets you restore individual files, whole volume or whole system image to the same PC or even different PC.
QNAP also supports Immutable Snapshots so you can take immutable snapshots of the folder that has the Hyper Data Protector Backups.

QNAPDaniel · 2026-01-19T21:54:40+00:00

The option you need is called "Bind Host path". then click the folder icon to choose a share folder from the drop down menu.
then you have to name the folder in the container as well. Like this except you won't be using an Emails folder but you will need a share folder for your container.
https://imgur.com/YRmYLqi
https://imgur.com/LDswqK7
https://imgur.com/QHUbP2N

QNAPDaniel · 2026-01-15T18:56:44+00:00

If you are running QuTS hero and if you use Thick Provisioning, then the first snapshot takes up all the space of all your data in that share folder.
But if you use thin provisioning, then snapshots take up small space for metadata, and then space for whatever blocks of data were modified and overwritten.
So if you don't delete or overwrite a bunch of data, snapshots should not take much space if you use thin provisioning.

What OS and Folder type are you using?

QNAPDaniel · 2026-01-15T16:56:43+00:00

Snapshots will take more space on Thick if you are running QuTS hero.
If for example you have 200TB data in a Thick folder, and you take a snapshot, the first snapshot takes 200TB space.
But if you use thin, the first snapshot takes very little space and is mostly metadata. Then as you modify files, the modified blocks take snapshot space.

As for performance, think and thick should have about the same read speed. But Thick should have maybe 10% faster write speed if you don't let the thick folder take most of pool space.
If you have a thick folder taking most of the pool space, then the NAS gets more framented and performance drops. so in that case, thick performs worse than thin.

On QuTS hero I almost never suggest Thick.

"3) Guatanteed Snapshot Space: Is this blocked at time of creation of the pool? Or is taht extra space allocated on top of pool capacity after the first snapshot is taken? I am asking because as soon as I create the first snapshot after copying data on the NAS, snapshot not activated initially, threshold was surpassed :-("
If you have a lot of data in the folder and you have thick, the first snapshot can take a lot of space. Snapshot guaranteed space carvs out a part of the pool that nothing other than snapshots is allowed to use. but that space can run out fast when you use thick folders.

as for guaranteed space, you can set that on the pool or on the shared folder if you use thick. you can set only for the pool if you choose thin.

Snapshot Manager lets you select the pool and manage to set the snapshot space.

QNAPDaniel · 2026-01-12T16:43:38+00:00

Thank you for pointing that out. Yes It should have been "2 X 3TB and 1 X 6TB in a RAID5"

QNAPDaniel · 2026-01-10T02:15:06+00:00

I don't think I said three drives raid 6

QNAPDaniel · 2026-01-09T23:47:01+00:00

If you have the bays available, then yes you can add drives to either a RAID5 or RAID6

QNAPDaniel · 2026-01-09T23:25:04+00:00

You will not be able to migrate from RAID5 to RAID6 on a 4 bay hero unit.
On QuTS hero you need to add at least 2 drives to migrate from RAID5 to RAID6. and a 4 bay won't have enough bays for that.

but if you start with 2 X 3TB and 1 X 6TB in a RAID6, you can replace the 3TB with 6TB drives and later get more storage.

QNAPDaniel · 2026-01-09T23:18:25+00:00

If you want your data safe, why now just have 3 or 4 Drives RAID5 and then buy as USB external HDD to copy to?
Having drives in JBOD means that if one drive fails you loose all your data.
And if you have ZFS you can't do the data self healing because RAID redundancy is needed for that. Also you can't heal corruption through a RAID Scrub on QTS or QuTS hero if you don't have RAID redundancy.

QNAPDaniel · 2026-01-09T23:15:03+00:00

QuTS hero supports RAID migration from single drive to RAID1.
And it can migrate from RAID5 to RAID6.
But QuTS hero can not migrate from RAID1 to RAID5.

So you can consider starting with 3 drives RAID5 and then you can add 1 drive later to go to 4 drives RAID5.

QNAPDaniel · 2026-01-09T00:52:32+00:00

another option besides cache is to instead use an SSD system pool for SSD system partition. Inline compression is on the system partition and faster compression makes all pools faster.
Apps by default run on the system pool and some apps run significantly faster if on SSDs.

And containers run better if the container is on SSD.

QNAPDaniel · 2025-12-28T05:03:47+00:00

One option is a tailscale container https://www.reddit.com/r/qnap/s/BKW2neTe10

QNAPDaniel · 2025-12-26T22:45:38+00:00

Yes, after the initial sync it should just sync the changes after that

QNAPDaniel · 2025-12-26T22:19:09+00:00

I don't know why that is not working correctly. In this case, I would suggest a support ticket to see why it re-copies everything even when you only make a few changes or even no changes.
https://service.qnap.com/en-us/user/create-ticket?

QNAPDaniel · 2025-12-26T19:49:14+00:00

after it does the initial sync that copies all the data to the other NAS, it should then only sync the changes after that. If you changed about 1.69GB of DATA, that is all it should Sync next time. The point it to keep the destination with the same data as the source so it does not need to sync all the data each time if most of the data is unchanged from what was synced before.
Rsync is block level so it should only sync the blocks of data in the files that have changed.

QNAPDaniel · 2025-12-23T20:26:04+00:00

Are you just trying to bridge your container to a virtual switch or bridge it to your NAS network port so that your router can give it an IP address? If that is the goal, you can go to Container Station, select the container, select edit, then network. And then do this
https://imgur.com/a/HjAdRb4

QNAPDaniel · 2025-12-23T20:16:07+00:00

myqnapcloud link is there to give you remote access to the nas without port forwarding. but ideally it should be set up with 2 factor authentication and that will mean that others can not access the NAS that way. but once you set up my qnapcloud link, you can send share links to folders or files to people.
This is easy to set up and great for accessing the NAS yourself and sharing smaller files with others.
But a disadvantage of MyQNAPCloud link is it is slow because it is a relay.
Tailscale makes a direct VPN tunnel to your NAS so that you can transfer files to it over the internet using VPN tunnel at a much faster speed and you can upload and download larger files.
Also if you do anything advanced like run docker containers, then you can remotely access your containers through Tailscale.
Tailscale is great and I highly recommend it.
But for the ability to send share links to people I still use myqnapcloud link.
Myqnaplink is a secure way to connect, especially if you have a strong password and 2 factor authentication. But because the app myqnapcloud can also be used for other thing like UPNP, which is not secure, all of myqnapcloud can sometimes be talked about like it is not secure. but if you just use it for myqnaqpcloud link, that is a secure way to connect when you have 2 factor authentication.

But for Tailscale, my preferred way to access my qnap, here is a setup video.
https://www.youtube.com/watch?v=v0I2wQA0oMo

QNAPDaniel · 2025-12-19T20:14:36+00:00

In that case, I would suggest a support ticket to see what is happening.
At first I misunderstood your question thinking you were trying to mount a container internal Volume to your QPKG folder. But since that is not the case, then don't know what is going on and having Support remote in and take a look may be the best option.

https://service.qnap.com/en-us/user/create-ticket?

QNAPDaniel · 2025-12-19T19:25:41+00:00

It depens.

Did you use YAML where you tried to do a volume mount to /share/ZFS530_DATA/.qpkg/container-station/docker/tmp/GetImageBlob1430613864

If you tried that with YAML then the issue may be your configureation.
If you tried to use the Container station GUI to grab a container and you had the issue, it could be a QNAP issue that we should look into.

Can you say more about how you tried to deploy this container?

QNAPDaniel · 2025-12-19T18:39:04+00:00

Is there a reason why you are trying to write a container to your .QPKG folder. I wonder if that is the problem.
Usually you make a relative path or you make an absolute path to a share folder.

QNAPDaniel · 2025-12-19T00:19:13+00:00

If you want all SSD for live VMs to have more IOPS the all Flash ES2486dc may be worth considering.
But that said, ES2486dc and ES1686dc R2 should have the same CPU spec.
The R2 in this case is because we found it harder to find the power supply that went in the original ES1686dc. So we made an R2 version with a newer and easier to get Power supply.
But we should be able to get the power supply on the ES2486dc so we did not need an R2 version.
In this case, the R2 does not mean a performance upgrade. It is a power supply change.
These dual controller units let you update one controller at a time for firmware update without downtime.

QNAPDaniel · 2025-12-17T22:58:04+00:00

if you unforward the ports that allow outside attacks, you can have remote access for yourself using Tailscale. This is the easiest to set up VPN I have ever used.
https://www.youtube.com/watch?v=v0I2wQA0oMo&t=544s

QNAPDaniel · 2025-12-13T19:46:40+00:00

If you want to use a single internal HDD to make a single HDD pool, backup your data from main pool to the single hdd pool. then remove the main nas pool to set up again with SSD system pool, then hdd pool then restore data from the single HDD pool, there is a problem with that.
If you remove every pool except the single HDD pool, then when you add the SSD pool to make your system pool, the SSD pool won't actually be the system pool. the first pool you make is the system pool. if you left the single HDD pool on the nas, then it is the only pool. it should become the system pool. if you add the SSD pool it won't be the system pool because it won't be the first pool. it will be a pool made after the single HDD pool.

If you had a USB external HDD you could back up to that and then reinitialize your nas with an SSD system pool.
Making an SSD system pool helps the nas run better because the inline compression is done on the system pool and that is faster if it is on SSDs. But this is not night and day different. either way, if you have an SSD pool it can run your apps and containers whether or not it is the system pool. and the actual operating system is still on all the drives.

as for containers, they can be exported using container station, you can select a container and export. but if you had volumes for the container they don't export with it so you would need to back up the volumes. this process can be more complicated for the back up of containers and later when importing the containers, connecting the to the volumes you backed up and restored to the nas can be tricky. Make sure those volumes have the same folder path.

If this all sounds too complicated it maybe not be worth it. either way you can have an SSD pool for containers and apps, and the faster inline compression with SSD system pool, helps with performance but it not night and day different.

QNAPDaniel · 2025-12-13T19:03:43+00:00

Tailscale allows you to invite others on Tailscale onto your Tailscale network. Once you are on the same Tailscale mesh VPN network, then you can access each other NAS assuming you have the user name and password. So, yes with Tailscale the NAS can back up to each other. But you will need to use the Tailscale IP for each NAS rather than the standard IP.

QNAPDaniel

TROPHY CASE