when backup it shows "storage is not online"

[micahel jiang]

Hi

I have proxmox connected to a QNAP -1273au-rp via NFS (or SMB) for a storage.
Use it to backup .

I've seen this question raised repeatedly on the forum, but there's no definitive answer. The daily backups are half successful and half unsuccessful, which is very frustrating! Proxmox doesn't seem to have paid much attention to this issue for years, but it's crucial for businesses.

I thought PVE9 would solve this problem, but it didn't! I used the guest OS with NFS and didn't have this problem, so I think the hosts file on the cluster storage isn't well-tuned.

Lately I have a frequant issue when I access the storage in proxmox with it telling me that the "storage is not online", when it is all the time. When I quit the message and try again it's instantly available sometimes.

I also discovered that whenever NFS Samba is mounted, queries to local and LVM-ZFS are affected, and df-h also experiences delays, presumably due to the constant scanning.

Is there a way to tell what the problem is?

Thx in advance

 

[MagicFab]

After experiencing all sort of problems with backups over NFS and Samba, I stopped using such storage and only use iSCSI for my setups whenever possible.

QNAP’s NFS server isn’t always tuned for heavy concurrent I/O from hypervisors. SMB/CIFS is even more problematic for VM backups : it introduces latency and locking issues.

When dealing with this in a cluster, I modify local hosts files to resolve the backup server, this eliminates having to deal with "it's DNS!" problems.

If you absolutely have to keep NFS or Samba, I'd choose NFS and tune it.

In /etc/pve/storage.cfg, check NFS options:

options vers=3,proto=tcp,timeo=14,retrans=3

• vers=3 -> QNAP’s NFSv4 support is often buggy.
• proto=tcp -> avoids UDP packet loss.
• Lower timeo and retrans -> fail faster instead of hanging

Test, rinse and repeat.
Or just use iSCSI.

I welcome other opinions and suggestions ! This is only based on my personal experience and installs I've supported.

---

Fabián Rodríguez | Le Goût du Libre Inc. | Montreal, Canada | Mastodon
Proxmox Silver Partner, server and desktop enterprise support in French, English and Spanish

 

[micahel jiang]

After experiencing all sort of problems with backups over NFS and Samba, I stopped using such storage and only use iSCSI for my setups whenever possible.

QNAP’s NFS server isn’t always tuned for heavy concurrent I/O from hypervisors. SMB/CIFS is even more problematic for VM backups : it introduces latency and locking issues.

When dealing with this in a cluster, I modify local hosts files to resolve the backup server, this eliminates having to deal with "it's DNS!" problems.

If you absolutely have to keep NFS or Samba, I'd choose NFS and tune it.

In /etc/pve/storage.cfg, check NFS options:

options vers=3,proto=tcp,timeo=14,retrans=3

• vers=3 -> QNAP’s NFSv4 support is often buggy.
• proto=tcp -> avoids UDP packet loss.
• Lower timeo and retrans -> fail faster instead of hanging

Test, rinse and repeat.
Or just use iSCSI.

I welcome other opinions and suggestions ! This is only based on my personal experience and installs I've supported.

---

Fabián Rodríguez | Le Goût du Libre Inc. | Montreal, Canada | Mastodon
Proxmox Silver Partner, server and desktop enterprise support in French, English and Spanish

Thank you for your reply. Unfortunately, I'm using it as a backup, which is why iSCSI doesn't support it.
Updated: I mount the iscsi volume and add directory on this vol and it works fine.
I think it's not supposed to be like this way ; Hopefully, the next version will be even more perfect, and a time schedule will also appear in Snapshot.