internal error - tried creating snapshot that's already in use

Rico29 said:
thanks.
I checked, vm is locked by a verify task on the same datastore.
thanks for your help !
Click to expand...
Hey @Rico29,
How did you fix this ?
I have the same issue with a verify job taking sometimes longer than expected and causing this error on a Sync.
I could stop the sync for 2h at night and do the verify only once a day at that time, but it feels and sounds wrong.
 
festraviz said:
Hey @Rico29,
How did you fix this ?
I have the same issue with a verify job taking sometimes longer than expected and causing this error on a Sync.
I could stop the sync for 2h at night and do the verify only once a day at that time, but it feels and sounds wrong.
Click to expand...
Hi,
as said in the previous post, vm was locked by a verify task on the same datastore.

check that rou backup is not locked or beeing synced at the same time
 
  • Like
Reactions: festraviz
Rico29 said:
Hi,
as said in the previous post, vm was locked by a verify task on the same datastore.

check that rou backup is not locked or beeing synced at the same time
Click to expand...
@Rico29, thanks for the lightning fast response on this "old" thread !!!
So, I did get that and got to this thread by looking for options and ideas on how to solive it and I'm curious on what exactly you changed in your Verify and Sync schedules to avoid having the verify running at the same time as the Sync.
I have Sync and Verify running every 30 minutes : Sync is running on *:15/30 and Verify was on *:12/30.
I'm moving Verify to *:20/30 and will report back, but I highly doubt as Verify does run for more than 2 hours long on occasions, re-verifying old backups (>30 days).
 
Last edited:
You must log in or register to reply here.
Top Bottom