Thorough, thanks! I see you and some others are using “asynchronous” backups where the databases backup on a schedule and the backup program does its thing on its own time. That might actually be the best way!
Thorough, thanks! I see you and some others are using “asynchronous” backups where the databases backup on a schedule and the backup program does its thing on its own time. That might actually be the best way!
I’m coming from rsync too, hoping for the same good stuff
It’s gon b long ass backup script I think!
Good to know if I need to just throw the running database into borg/restic there’s a chance it’ll come out ok! Def not a dummy, I only found out databases may not like being backed up while running through someone mentioning it offhandedly
Not a bad idea for a hybrid thing, especially people seem to say that a running database backup at least some of the time most of the time with no special shutdown/export effort is readable. And the dedupe stats are really impressive
That is nicely expandable with my docker_compose files, thanks for the find!
Thanks for the incantation! Its looking like something like this is gonna be the way to do it
So you’re saying you dump on a sched to a <place> and then just let your restic backup pick it up asynchronously?
Holy shot thanks for droppin this spell, that’s awesome
That’s wild and cool - don’t have that architecture now but… next time
Love the detail, thanks!!
As far as I know (unless smarter people know), you need a “long ass backup script” to make your own fun on a set schedule. Autorestic and borgmatic are smooth but don’t seem to have the granularity to deal with it. (Unless smarter people know how to make them do, which I may be fishing for lol)
That’s ok for a database that’s running?
Do you use a ZFS backup manager?
Ah gotchya, well docker compose plus the image is pretty necessary for me to easily manage big ass/complicated database-based storage services like paperless or Immich - so I’m locked in!
And I’d still have to specially handle the database for backup even if it wasn’t in a container…
;.; I don’t know what this means
Yes, it’s recommended to replace the SP4 screen with an SP5 screen - so you can rest easy
Glad yours is usable still! Mine went from fine to unusably flickering within the span of a week, so it set in fast. I babybabied it too hoping to avoid the issue - I guess I just prolonged it till it microsoft wouldn’t fix it anymore. rip fuck this corpo created e waste shit (I use it as a comp strapped to my TV now)
Ditch it, the Surface Pro 4’s are cursed via shit manufacturing.
Its screen will fail sooner or later https://flickergate.com/ . I had one, it started flickering after the “extended” warranty. The display is useless now. Nothing fixes it. At first the flicker stopped if something on the screen moved, so I used this https://github.com/Acie1998/Surface-Pro-Screen-Flicker-Solver to mitigate it. But within a day or two it was worse. I tried a reduced refresh rate, but that did not help by then. It quickly got worse when in use, within minutes after a week of the flickering starting. A used one is just pre-accelerated to its demise.
Replacing the screen - even opening the device - is egregiously dangerous because the screen often cracks when taking it apart. Microsoft abs sucks for making a device that can’t last when it clearly should. (Not to say anything about your specific problems! It sounds like the battery needs to be replaced, but it can run without a battery as far as I know so not sure why it can’t power up with it heavily depleted)
Edit: if you’re going to remove the sceeen, replace the battery and replace the screen with a surface pro 5 screen. They sell them. The batteries get fucked quick cause the heat sink cooks them, so it’s prob the battery causing your problems (mine had shit battery life at its end too)
Here is a blurb from Reddit describing what to get (ifixit apparently sells a surface pro 5 screen as well if you want one degree better than direct China): My advice, if you have a Surface Pro 4 with an Samsung Panel is to replace for an LG Screen from Surface Pro 5/6. You need to buy this LCD cable too for that conversion: M1010537-003
You can check in the device manager which LCD panel you have on your Surface
I did a wireshark packet capture and found the wake-up packet is on UDP 987. I can only capture broadcasts, not specific stuff it looks like. Source: 10.0.69.69(iOS device IP) Destination: 10.0.69.255 Protocol: UDP Length: 105 Info 57477(or 62764, 62335, 60311 as source ports) -> 987 Len=63
Note the IP of the PS4 is 10.0.69.150
I’m not sure what to do with this, though. Nothing I tried worked (e.g., jamming 987 into the IP tables iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A PREROUTING -p udp --dport 987 -j DNAT --to-destination 10.0.69.150:987; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE; iptables -t nat -A POSTROUTING -p udp -d 10.0.69.150 --dport 987 -j SNAT --to-source 10.0.66.10:987
based on https://serverfault.com/questions/586486/how-to-do-the-port-forwarding-from-one-ip-to-another-ip-in-same-network).
Additionally setting the Wireguard mask to 10.0.66.1/16 makes the WG connection not route successfully, and setting the mask in OpnsenseRouter->Interfaces->[LAN]->(under Static IPv4 configuration section) to 16 did nothing. Oh well, this seems beyond me
Would you mind pastebin-ing your docker image creator file? I have no experience cooking up my own docker image.