You make it sound so simple, in reality, its not. I tried to add a network location on my Windows 10 server, this is the result "Could not unmount Server2021_Backups due to: Transaction for mnt-data-supervisor-mounts-Server2021_Backups.mount/stop is destructive (mnt-data-supervisor-mounts-Server2021_Backups.mount has 'start' job queued, but 'stop' is included in transaction)." Total gibberish. Edit 1: Well, I just changed the name, basically removed the 2021 reference and it connected, how weird. Edit 2: Now I get "The operating system does not support network storage Network storage is not supported on this host", and if I try to access backups just a white screen, but it did eventually open. Oh such joy.
Nice message! Yeah, one thing I have learned in tech generally is that it's always more complex than you think it's going to be. I tend to include the challenges I come across in my videos. But as you can see with your issue. Everyone seems to come across different things.
I made a clone of HA's SSD under Windows 11 with the balenaetcher program to another SSD which allows me to change the SSD if my SSD has a data error or other. I obviously take snapshots on Google Drive.
That's certainly a good idea. When I used to run my HA on a Pi, I used to backup my SD card like that. Surprisingly I never actually had an SD card failure.
Marc, the HA backup method to NAS *used* to work, but sadly it stopped. Checking HA's Github page showed other people having the same issue: HA failing to use the NAS share because "Cannot mount HABackups at /data/mounts/HABackups because it is not empty." This is to a QNAP NAS with an appropriate SMB share that had backup data on it, but now I can't use it for backups? Crazy. After blowing out the backups and trying again with a fresh version of the share, the same message happens.... on a share that is completely empty (QNAP's own share management says there are 0 files in it).
Wow, thanks for letting me know about the GitHub issue, I didn't realise there was an issue so many people were having. Thankfully I haven't come across the issue. Reading the thread it looks like rather than deleting anything on your NAS itself you need to run some shell commands to clear up the mount point on the HA OS. Also, thankfully, it looks like a fix has recently been merged to address the issue. The fix won't resolve an existing mount issue by the look of it. So for you when you recreated the share, did you give the entry name (mount point) in HA the same name by any chance? I think you will need to create a new HA entry with a different name. (Regardless of the share folder name) Let me know how you get on!
I still use this add-on, but I only use it for local backups now because it backs up to 2 TrueNAS instances, so don't feel I need a Google backup as well. However, there are not any recent GitHub issues raised which would suggest it should have stopped working. Perhaps try and reauthenticate it with Google? It might be that some tokens have expired and not renewing correctly. It also has a "logs" tab which is worth checking out if you haven't already! It will hopefully point you to the problem.
That's a really good point. I should have mentioned that another thing people/businesses often don't do is actually test their restore process. I have the same backup mechanism for my dev environment. I do full Restores each month for that to aid with creating the HA monthly release videos. My setup is not ideal. I currently run ESXi. I plan to move to Proxmox later in the year and possibly have a clustered setup.
You make it sound so simple, in reality, its not. I tried to add a network location on my Windows 10 server, this is the result "Could not unmount Server2021_Backups due to: Transaction for mnt-data-supervisor-mounts-Server2021_Backups.mount/stop is destructive (mnt-data-supervisor-mounts-Server2021_Backups.mount has 'start' job queued, but 'stop' is included in transaction)." Total gibberish. Edit 1: Well, I just changed the name, basically removed the 2021 reference and it connected, how weird. Edit 2: Now I get "The operating system does not support network storage
Network storage is not supported on this host", and if I try to access backups just a white screen, but it did eventually open. Oh such joy.
Nice message!
Yeah, one thing I have learned in tech generally is that it's always more complex than you think it's going to be.
I tend to include the challenges I come across in my videos. But as you can see with your issue. Everyone seems to come across different things.
I made a clone of HA's SSD under Windows 11 with the balenaetcher program to another SSD which allows me to change the SSD if my SSD has a data error or other. I obviously take snapshots on Google Drive.
That's certainly a good idea. When I used to run my HA on a Pi, I used to backup my SD card like that. Surprisingly I never actually had an SD card failure.
Marc, the HA backup method to NAS *used* to work, but sadly it stopped. Checking HA's Github page showed other people having the same issue: HA failing to use the NAS share because "Cannot mount HABackups at /data/mounts/HABackups because it is not empty." This is to a QNAP NAS with an appropriate SMB share that had backup data on it, but now I can't use it for backups? Crazy. After blowing out the backups and trying again with a fresh version of the share, the same message happens.... on a share that is completely empty (QNAP's own share management says there are 0 files in it).
Wow, thanks for letting me know about the GitHub issue, I didn't realise there was an issue so many people were having.
Thankfully I haven't come across the issue.
Reading the thread it looks like rather than deleting anything on your NAS itself you need to run some shell commands to clear up the mount point on the HA OS.
Also, thankfully, it looks like a fix has recently been merged to address the issue.
The fix won't resolve an existing mount issue by the look of it.
So for you when you recreated the share, did you give the entry name (mount point) in HA the same name by any chance?
I think you will need to create a new HA entry with a different name. (Regardless of the share folder name)
Let me know how you get on!
Has Google drive back up stopped working ? Is there an alternative ?
I still use this add-on, but I only use it for local backups now because it backs up to 2 TrueNAS instances, so don't feel I need a Google backup as well. However, there are not any recent GitHub issues raised which would suggest it should have stopped working. Perhaps try and reauthenticate it with Google? It might be that some tokens have expired and not renewing correctly. It also has a "logs" tab which is worth checking out if you haven't already! It will hopefully point you to the problem.
Have you done a full restore from Google Drive and TrueNAS? A backup system without restore testing is just wishful thinking!
That's a really good point. I should have mentioned that another thing people/businesses often don't do is actually test their restore process.
I have the same backup mechanism for my dev environment. I do full Restores each month for that to aid with creating the HA monthly release videos.
My setup is not ideal. I currently run ESXi. I plan to move to Proxmox later in the year and possibly have a clustered setup.