[Glass] Backup procedure

[Johan Brichau via Glass]

> You mean you do not even ever stop/start seaside gems??? mmmmmm

Nope. Only when they crash ;)

> I have not figured out why the servicevm is behaving different in our case because the flag is set for all gems.
> 
> Did you check if one of the gems is fired linked while the others don't? if so, then you may be getting the flags of the gem.exe rather than the one of the seaside gems (I had this issue in the past)

I checked. Does not seem to be the case.
It’s a mystery (for now :)

> I never experienced a voting issue though, except if I accidentally launched another MFC concurrently. I don’t know but maybe a backup also blocks the voting process for an MFC? I think the manual mentions the conditions of the voting though.
> 
> 
> mmmm in my case I THINK that the one gem that was opened and rejecting the MFC because of voting was actually gemtools...not seaside gems. So...I guess I am stopping the gems while MFC just to be super sure it will be fine and the MFC takes little time so far. …

Ha yes. I think gemtools also causes that.
But mind that leaving a gemtools open without interaction for a long time while seaside is serving requests will also grow your transaction backlog. So I never leave gemtools connected for a long time.

cheers,
Johan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150608/23ee5988/attachment.html>