I have a remote VM that I am using to keep my encrypted ZFS backups. Also, in my current set-up I have some databases that I need to lock/flush before snapshoting them, and also unlock them when done. Then I have writen a script to lock/unlock the DBs, and another to start/stop the VM, so that my znapzendzetup create looks like (ZFSfiler is the SSH host configuration name in .ssh/config):
Do you want to save this backup set [y/N]? y
ssh: connect to host zfsfiler.westeurope.cloudapp.azure.com port 22: Network is unreachable
NOTE: if you have modified your configuration, send a HUP signal
(pkill -HUP znapzend) to your znapzend daemon for it to notice the change.
So, the machine is obviously not up as (I think) the manageVM.py script has not been run. Have I hit a bug, or am I doing something wrong (and I do not see what)?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I have a remote VM that I am using to keep my encrypted ZFS backups. Also, in my current set-up I have some databases that I need to lock/flush before snapshoting them, and also unlock them when done. Then I have writen a script to lock/unlock the DBs, and another to start/stop the VM, so that my znapzendzetup create looks like (ZFSfiler is the SSH host configuration name in .ssh/config):
When running the previous command, I get:
So, the machine is obviously not up as (I think) the manageVM.py script has not been run. Have I hit a bug, or am I doing something wrong (and I do not see what)?