Overview
This article will cover the prerequisites and client configuration details for MS SQL Server data protection.
The information in this article applies to:
- Standalone, failover, and AlwaysOn Availability Group (AAG) instances of MS SQL.
- For clustered MS SQL instances, please install the agent on ALL NODES in the cluster.
Client configuration with the prerequisite values
- Allow Cohesity network access to your client.
- Fill out a ticket here for NTS to allow traffic through the network firewall.
- Source IP: 10.128.180.64/26
- Destination: IP address(es) of MS SQL Server(s)
- Ports: 445, 1433, 50051
- Configure Client
- Download agent.
- Login to Cohesity using your Duck ID.
- Select ad.uoregon.edu as the Domain.
- Go to Data Protection > Sources.
- Click download agent.
- Select Windows.
- If you get a permissions error, submit a ticket here.
- Install the agent.
- Run the EXE file.
- Accept the defaults.
- Reboot the server when possible.
- Add inbound Firewall rule for Cohesity connection.
- Open Windows Firewall with Advanced Security on your SQL server
- Right-click Inbound Rules > New Rule
- New Rule Parameters:
- Rule Type:
- Custom
- Program:
- All Programs
- Protocol and Ports
- Protocol Type: TCP
- Local Ports: 445, 1433, 50051
- Remote Port: All Ports
- Scope:
- Which local IP addresses: Any IP address
- Which remote IP addresses: 10.128.180.64/26
- Action:
- Allow the connection.
- Profile:
- All three options checked.
- Name:
- Give it a descriptive name and description.
- Give the agent access to the MS SQL instance.
- Launch SQL Server Management Studio
- Create new login with sysadmin role
- Expand Security
- Right-click on Logins
- Select New Login
- New Login Parameters:
- General
- Login name: NT AUTHORITY\SYSTEM
- Server Roles:
- sysadmin
- public
Process Completion
Submit a ticket on the Data Protection Support service page for backup configuration and completion of the process.