"Reset after snapshot revert": what exactly gives on a Rocky Linux-based VA?

[carmik 0]

Hello,

all previous CentOS-based VA installations had an option from the text console to "Reset after snapshot revert". The Rocky-based VA does not have such an option, instead online documentation at https://help.eset.com/protect_deploy_va/11.0/en-US/va_upgrade_migrate.html prompts the admin to "Use Backup database instead."

This is not clear to me, I'd be grateful if:

1) someone could rephrase exactly what should be done in case one has to rollback a Rocky-based VA to a previous snapshot/version.

2) could explain what would happen if the admin fails to do so in such a case. Would clients misbehave and, if so, how?

[tomasS 5]

Dear Carmik,

thank you for your post.

#1) someone could rephrase exactly what should be done in case one has to rollback a Rocky-based VA to a previous #snapshot/version.

- well, this option is an execution of the stored procedure in the ERA DB, for instance:

Quote

declare @new_uuid char(36);
SET @new_uuid = LOWER(NEWID());
exec dbo.usp_replication_realm_uuid_set @new_uuid;

# 2) could explain what would happen if the admin fails to do so in such a case. Would clients misbehave and, if so, how?

- in case the step mentioned above will not be performed(an "usp" will not be executed), it might take some time till all information about particular computers will be synchronized(usually, full sync is done every 7 days)

Edited Friday at 11:46 AM by tomasS

[carmik 0]

Thanks @tomasS, from (2) above it seems that I won't have to do anything, things will be back to normal automagically after a couple of weeks.