No different than a hot-hot replication so just follow that pattern I feel like this is better accomplished with a device snapshot-image that is regularly load

No different than a hot-hot replication so just follow that pattern I feel like this is better accomplished with a device snapshot-image that is regularly loaded onto a new device (daily? Hourly?) Updating a device makes automation non trivial as you have to do something physical most likely and can’t just do it via API You could even just skip acquiring the device until you need it given the idea that it may be years before you have this volcano situation. However that doesn’t meet your spec precicely I would better define the idempotency interval you’re ok with losing data between and then using the method that updates the simplest at that frequency