Antsle Forum
Welcome to our Antsle community! This forum is to connect all Antsle users to post experiences, make user-generated content available for the entire community and more.
Please note: This forum is about discussing one specific issue at a time. No generalizations. No judgments. Please check the Forum Rules before posting. If you have specific questions about your Antsle and expect a response from our team directly, please continue to use the appropriate channels (email: [email protected]) so every inquiry is tracked.
Backups not showing status after completion
Steps taken:
- I did a "Backup now" operation on an LXC antlet and chose "self-managed".
- I had previously installed a public key from my Antsle on my backup server which happens to be a Netgear ReadyNAS 312.
- I specified the destination path (/data/Backups/Antsle) and the user for the ReadyNAS ([email protected])
- Started the backup. The process went through the "Backing Up" status, then the "Uploading" status and appeared to complete successfully.
- I looked on the ReadyNAS and the backup file was present (backup_local_6.zfs.gz).
- However, when I view the Antman backup screen for Antlet, there is no status and no actions available. See the attached screen shot of the backup screen.
Question 1: Why is no information displayed for ID#6.
Question 2: How could I restore this backup, if I needed to?
Question 3: The three other backups (#2,#3 and #4) all failed and but they persist in the backup table. I've searched the directories on the Antsle, but I can't find a backup catalog anywhere. I would like to delete these non-existent entries. Where is this information stored on the Antsle?
Uploaded files:
OK, I didn't realize I didn't have the latest Antman. I upgraded to 3.2.1 and that fixed everything... sort of. I could now delete the empty backups (#s 2,3,and 4) as well as having the successful backup(#6) show up with a "delete" and "restore" option.
I say "sort of" because according to the backup video from a week or so ago, it appeared that you could restore over the top of an existing stopped antlet. I don't see that restore option with version 3.2.1. It forces you to create a new antlet. I suppose one could delete the original antlet then heal to the same name, but that somehow seems risky to me. I would much rather have the "Restore" function download the backup to a local copy and then, if successful delete and restore the target antlet.