Jump to content

Michael Hacker

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Michael Hacker

  • Rank
    Newbie
  1. Thanks! I eventually will run a Blue Iris VM, but I'm guessing that just backing up my Blue Iris settings from the VM would be sufficient instead of that massive file. Appreciate it!
  2. Does anyone have a clear understanding of libvert.img and why it would need to be backed up. Of course, including it in the backup is no big deal, but I also offsite my backups of appdata and flash to AWS S3. I'm wondering if I need to do the same for libvert.img and how important it is. Currently i'm doing a checksum to see the backed up libvert.img file has changed, and even though I have no VMs it seems the checksum is changing every 2-3 days, which then triggers a 1GB upload to aws, which seems not necessary. Am I missing something? I tried to search around but it doesn't seem there is a clear answer of what libvert.img (beyond used to run VM) and why/how it would change, especially when not running VMs. Thank you!
  3. New unraid and s3backup user here. First, this container is great, and thanks for providing it! One question though, I'm not sure if I'm doing something wrong, but everytime i start the container, I get another cron entry. Now /etc/cron.d/s3backup has 8 entries (the first one and 7 duplicates). I can't figure out how to edit the cron file or how to make it stop duplicating. I know this file has to be stored somewhere but there isn't any disk maps beyond my share that i'm backing up. Any help is appreciated.
  4. Can anyone point me in the direction of where to put the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. I understand that these need to be daemon environment variables and not client environmental variables and those daemon variables are what I can't figure out. Specifically looking here: https://docs.docker.com/config/containers/logging/awslogs/#credentials.