Skip navigation

Allow BDA to reboot agent nodes if necessary

score 20
You have not voted. Not Planned

BDA currently has the ability to reboot a Windows node as part of a job, but this functionality is not used in any of the places it would be really useful.

  1. Provide a new checkbox in the job options page "Reboot target node after job if necessary" that will check to see if a reboot is necessary at the end of the job, and, if so, will reboot the node.  If the node is part of a Windows Server Failover Cluster (WSFC), the state of cluster resources should be noted before the reboot occurs and those states should be restored when the node is back up (i.e., if this node is the active node in a Clustered SQL Server instance before reboot, it should be the active node after the reboot), and BDA should not reboot more than one node in a WSFC at the same time.
  2. Provide a new checkbox in the job options page "Reboot target node before job if necessary" that will check to see if a reboot is necessary at the beginning of the job, and, if so, will reboot the node. All the same WSFC checks/actions for "Reboot target node after job if necessary" will be performed.
  3. A new capability (say, "Reboot Node as part of job") will be added to allow restricting this new feature to certain users without needing to provide those users the "Reboot Node" capability.  Users that have the "Reboot Node" capability would implicitly have the "Reboot Node as part of job" capability.

Comments

Vote history