Current backup script restart btcpay.
I understand it is nice for consistency, but there is unnecessary downtime, especially when backing up often to keep LN channels state fresh.
What could happen when there will be inconsistency in files (other than postgres, it uses transactions for dumps)?
I expected all services can (should) recover inconsistencies at least in case of power outages, so why not in case of restore from backup?
Can we add option to not do restart?
Current backup script restart btcpay.
I understand it is nice for consistency, but there is unnecessary downtime, especially when backing up often to keep LN channels state fresh.
What could happen when there will be inconsistency in files (other than postgres, it uses transactions for dumps)?
I expected all services can (should) recover inconsistencies at least in case of power outages, so why not in case of restore from backup?
Can we add option to not do restart?