SQL Clone service behaviors
Sean_Lively
Posts: 27 Bronze 2
in SQL Clone
Last night after our windows update installs completed and the VMs rebooted, 30 of our SQL Clone Agents failed to register with SQL Clone, likely due to the hosting server for SQL Clone rebooting at the same time.
1. It would make life a LOT easier if the services (both SQL Clone Agent and SQL Clone) would stop running when they give up, as we can monitor for stopped services instead of trying to scrape the Agent screen.
2. Please remove the version number from the SQL Clone Agent service name. Having the version name in the service complicates recovery scripts.
1. It would make life a LOT easier if the services (both SQL Clone Agent and SQL Clone) would stop running when they give up, as we can monitor for stopped services instead of trying to scrape the Agent screen.
2. Please remove the version number from the SQL Clone Agent service name. Having the version name in the service complicates recovery scripts.
