- From the Management Console, navigate to the Availability Group on which you want to remove the database.
Make sure that the primary replica for the Availability Group is on the SQL Server instance that you want to contain the database after it is removed from the Availability Group. If it is not, follow the instructions in Failing over a SQL Server Availability Group to fail the primary replica over to the appropriate instance.
Select Provision > Remove Database from SQL Server Availability Group In the General page, populate the following fields, and click Next.
Field
Description
Domain
Displays the BMC Database Automation (BDA) domain for the Windows cluster hosting this Availability Group.
Cluster
Displays the Windows cluster hosting this Availability Group.
Primary Instance Displays the current primary instance for this Availability Group. Template
(Optional) Select from the list of defined Remove Database from Mssql Availability Group templates to automate input during the wizard data collection. If you select a template, you may click Skip Ahead to advance directly to the next step that requires input. Any steps that have been configured by the information in the template will not appear.
In the Databases Selection page, populate the following fields, and click Next.
Field
Description
Databases
Select the database that will be removed from the Availability Group.
Note
There must be at least one database in an Availability Group at all times.
Remove Secondary Databases
If this option is left unchecked, the selected databases will be removed from the Availability Group and identical copies of the database will exist on each instance hosting a replica of the Availability Group. If this option is checked, BDA will, after removing the selected databases from the Availability Group, delete the identical copies of the databases from the instances hosting secondary replicas, leaving the only copies of the database on the instance hosting the primary replica. Checking this option makes “Remove Database from SQL Server Availability Group” leave both the Availability Group and the target database in the same state they were in before a corresponding “Add Database to SQL Server Availability Group”: the database isn’t part of the Availability Group and only exists on one instance.
In the Custom Scripts Configuration page, select any pre-provisioning or post-provisioning scripts that you want to run as follows, and click Next.
Section
Description
Pre-Provisioning Scripts
(Optional) Select the scripts that you want to run before this event and click the right arrow to move them to the Selected list box. The scripts in Selected are run in the order listed. Use Move Up and Move Down to re-order the scripts when necessary. See also Managing pre-provisioning and post-provisioning script files.
Post-Provisioning Scripts
(Optional) Select the scripts that you want to run after this event and click the right arrow to move them to the Selected list box. See also Managing pre-provisioning and post-provisioning script files.
In the Job Options page, specify any of the following Job options, and click Next.
Type
Option
Description
Notification Emails
Email List
(Optional) Click Add Email to add email addresses to the notification list.
Job Administration
Cleanup Agent Logs
(Optional) Select to automatically remove logs that are generated by BMC Database Automation on the Agent after the Job is complete.
If the Change Control page displays, populate the following fields, and click Next.
Section
Field
Description
Bypass Change Control
(Optional) Select to bypass using BMC Remedy ITSM to control the change process. Selecting this option removes the rest of the fields from this page.
Change Control Options
Select to determine whether to open a new BMC Remedy ITSM change ticket, or to use an existing BMC Remedy ITSM change ticket to control the change process.
- Selecting Use Existing Change Ticket displays the fields in the Use Existing Change Ticket section on this page.
- Selecting Create New Change Ticket displays the fields in the Create New Change Ticket section on this page.
Use Existing Change Ticket
ITSM Change ID
Specify the BMC Remedy ITSM change ticket number to associate with this change process.
ITSM Task ID
Specify the BMC Remedy ITSM task ID number to associate with this change process.
Create New Change Ticket
Change Type
Assign the type of change for the new BMC Remedy ITSM change ticket.
Change Impact
Assign the impact level of this change process for the new BMC Remedy ITSM change ticket.
Change Urgency
Assign the urgency level for the new BMC Remedy ITSM change ticket.
Change Risk-Level
Assign the risk level of this change process for the new BMC Remedy ITSM change ticket.
Change Class
Assign the change class for the new BMC Remedy ITSM change ticket.
Change Summary
Type a summary of the change process.
Note
The Change Control page appears only when change control is configured for your environment. See Configuring change control.
- In the Summary page, review the provisioning information.
To make changes, do the following:- Click Go to to return to the provisioning step that you want to edit.
- Make your changes.
- Click Save and Review to return to the Summary page.
- Specify your verification preferences.
For additional information, see Understanding pre-verification tests.- To continue with removing the database from the availability group after the pre-verification tests have been successfully run without manual intervention, select Automatically Continue If All Tests Succeed.
To remove the database from the availability group without having first run the pre-verification steps, select Skip Pre-Verification Tests.
Note
The Skip Pre-Verification Tests option should only be used when you are certain all tests can succeed. The option skips verification and advances directly to the actual provisioning activity.
Click Remove Database from SQL Server Availability Group.
A progress page appears followed by a success message upon completion. The databases no longer appear in the Contents page for this SQL Server Availability Group.Note
Detailed current and historical information about this action can be viewed in the Jobs section of the Management Console. See Monitoring jobs and viewing job history.
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks