walle

Members
  • Content Count

    31
  • Joined

  • Last visited

Community Reputation

2 Neutral

About walle

  • Rank
    Newbie

Recent Profile Visitors

437 profile views
  1. Unfortunately no what I'm aware of, all information is contained in the /mnt/user/system/docker/docker.img file and the easiest way to get any meta information from this file is running docker CLI commands. If you read the content of my script, it's basically the same docker commands that you would normally write in a terminal. I don't think there is any similar way than this unless someone either creates a plugin or be part of some backup plugin/tool. Anyhow, just install User script plugin, if you not already have it, and copy paste the script, change path and you are done.
  2. I would like to have the option to install autossh with Nredpack if possible.
  3. Yeah, but in my case I also need to know what driver I did use and that's why I needed the network config. But thanks anyway. Anyhow after another server crash (🤮), fix the most likely cause of the error, recover the data again and lastly fixed mayor issues with some containers I finally had time to reconfigure the networking. It was a bit of a pain, but if this happens again I have now at least metadata backup of the config thanks to this simple scheduled user script I run every night: #!/bin/bash BACKUP_PATH=/mnt/user/backup/system/metadata docker network ls > "${BACKUP_PATH}
  4. That’s the basically the issue, I don’t remember what networks I did setup and what guides I followed. I will probably able to figure that out soon as I get some sleep (currently 4 am). I still have the corrupted docker.img, so if it’s possible to recover the information from it I will give it a try. Also, if there is a way to back up Docker metadata other than backup docker.img file, let me know. Or if it’s ok to back it up anyway even if it’s mostly unnecessary and space inefficient to do so.
  5. For some reason my cache pool got corrupted today (thx 2020) and I ended up with using btrfs restore, format and restore the pool. When I tried to start the Docker service again got the following message: So I deleted the docker.img-file, started the service and I'm currently adding the containers from my templates. However it seems that my Docker network settings are gone and therefor a few containers can't run properly because of missing my custom network types. Is there a way to restore these network settings, or at least a way to recreate it? Also it would be nice
  6. The balance operation is done, and I think this looks like that everything is in working order (correct me if I'm wrong): Label: none uuid: fd9abfd5-7e13-487f-ba5d-419b90608d6b Total devices 2 FS bytes used 262.61GiB devid 1 size 465.76GiB used 293.03GiB path /dev/mapper/sdg1 devid 2 size 465.75GiB used 293.03GiB path /dev/mapper/sdf1 Label: none uuid: bf870768-3cdb-4f9e-836b-4b1ed2c4c253 Total devices 1 FS bytes used 384.00KiB devid 1 size 238.47GiB used 1.02GiB path /dev/sdk1 Label: none uuid: e15f3b51-09b3-4cab-bbee-13670824960d
  7. I think I found the problem. I use a script from this topic in order to have the encryption key stored on another server: I think the issue is that the unlock encryption key was removed too early in the process and therefor couldn't start the balance operation. After I disabled the key deletion script and re-added the drive to the pool, then the balance operation with the start of the array. Now I just have to wait and see if the balance operation can be completed successfully or not.
  8. Ah ok, yes I did that also. I didn't help.
  9. I don't think that helped. Seams to be the same issue. See attachment for fresh diagnostics. I was not sure exactly how you wanted me to wipe the device, so what I did in that case was to remove the partition and formatted to unencrypted BTRFS (if that matters at all?). Also it has been consistent and called it sdf. walleserver-diagnostics-20200318-1317.zip
  10. I did that, it seams that it's still the same issue. I have attached fresh diagnostics zip. But something I noted was that when I stopped and unassigned the drive and started the array again, the docker service failed to start. I connected to the server via SSH and saw that the /mnt/user didn't exist. This was fixed by starting and stopping the array without any changes. When I later re-assigned cache2 it happen again, and was solved in the same way. Do you think this odd behavior have something to do with including cache2 into the cache pool? walleserver-diagnostics-20200318-11
  11. Ok, here you go. walleserver-diagnostics-20200318-0901.zip
  12. I have recently bought a new 500 GB SSD in order to create a cache pool with my existing encrypted btrfs 500 GB SSD cache device I installed a while back. What I have basically done is to shut down the server, installed the drive, start the server and lastly followed this guide: The thing is that I don't think it started to balance the drives when I started the server. I had to trigger a full balance manually and after balancing I'm not sure if the pool is working or not. See attachment for screenshot. As you can see, it still have "new drive" status and have basically no wri
  13. I have a Docker image that needs the hostname paramter. For example: docker run --name backup-container --hostname backup-instance How do I set this parameter in a container template?
  14. Sorry about the late reply. I didn't have time to get back to you. You can read about the cache folder here: https://forum.duplicacy.com/t/cache-usage-details/1079 It uploads during backup, it only uploads chunks of the files. https://forum.duplicacy.com/t/chunk-size-details/1082 What I do is I backup locally on the server, then using the copy command to offsite storage. It's much more efficient than run same backup for each offsite backup storage and upload it each time. I think don't need to do that. Sense my last post, Duplicacy have announced beta testing o