Timing to start the service after obtaining a consistency backup

[Tos]

Hi
Our customer have question about consistent backup of Veeam Backup for AWS.
They want to backup Linux EC2, so they use pre/post scripts that stop/start service.
https://helpcenter.veeam.com/docs/vbaws ... tml?ver=40

However, the first EC2 snapshot creation takes time, so the service will be stopped for a long time at the time of the first job running because post-script is executed after the EC2 snapshot is completely created.
Customers believe that backup data is consistent if the service is down even at the start of the EC2 snapshot creation task.
So, immediately after starting the Veeam Backup for AWS job and the pre-script stops the service and the EC2 snapshot creation task starts on AWS, they think it's okay to manually start this service.

Is there any problem with this operation ?

Let me know.

[nielsengelen]

Hi Toshihiro,

The flow sounds correct and Logic. On the timing, it is hard to tell if there is something causing a delay that may be faster. For this, we would need insight via logs to see the actions in order. Could you (or your customer) contact our support and let us know the case ID here so we can follow it for reference?

Thanks!