Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started using Hot Snapshots i.e. Backups with Snapshots while the VM was running and identified potential corruption to some of my backed-up VM services, hence the need to have those services stopped prior to the backup snapshot.
The first approach that I contemplated was to have the VM stop the sensitive services prior to the backup and then call the backup ghettoVCB script. The drawback to this solution was that the restore process where the services where stopped required to be restarted manually. The second approach was to use the POWER_VM_DOWN_BEFORE_BACKUP option of ghettoVCB. The draw-back of such approach was obviously the VM required to be stopped prior to the backup, but also the restart only occurs once the backup was completed. Not much I could do about powering-down the VM but I notice that I could speed-up the restart process by having a snapshot created immediately after the power down, this allowed the restart of the VM while it is being backed-up making the access to the VM faster.
I added the option COLD_START_SNAPSHOT to ghettoVCB code to provide faster access to the VM. I must confess that I am not the first to have had this idea. You will find similar approach here: #166 . You can thank @ctsde-markus owner of the thread: Reduce downtime with POWER_VM_DOWN_BEFORE_BACKUP=1 who gracefully encouraged me to release my branch of the code with a small design approach difference to my code described in the above thread #166
Implementation note: to enable the option COLD_START_SNAPSHOT you will be required to also enable the option POWER_VM_DOWN_BEFORE_BACKUP. I made this design code decision to make it clear to all users that when you choose the COLD_START_SNAPSHOT option it will require a power-down of the VM.
One last item, I believe I found a bug to the backup script while working on this option, which was difficult for me to ignore. You will find a thread of the issue here: #163 . I decided to add the fix to this branch. If you believe that I have made a ‘faux pas’ in doing so, I can be convinced of retracting the fix.
Enjoy