Tuesday, July 24, 2012

Backing up Microsoft SQL

As advertised the 3X Appliance is capable of backing up Microsoft SQL databases. In fact, as of version 3.1.26 the product is even able to handle Microsoft SQL clusters. Due to the demand for backing up this platform we get a lot of questions about how to configure the backups for SQL, and how to configure SQL to play well with our product.

First things first, we need to list out what is needed to have a successful backed up SQL environment:
1. SQL Server Instance
2. SQL Management Studio
3. 3X Appliance

Next lets talk about how your SQL instance should be configured. The first requirement is that the SQL Server Browser service is enabled, started, and set to automatic. The service is question is shown in the following screen shot:



After you've made sure that requirement is met you will then want to make sure you have SQL authentication enabled on your instance, as well as an account set up. The easiest way to do this is through the use of SQL Server Management Studio. In SQL Server Management Studio you'll want to go into the properties of your SQL instance and to 'Security'. There you'll want to select 'SQL Server and Windows Authentication mode'. Screen shot below:


You also need to make sure you have a SQL account that you can use. In the example here it's the sa account due to it being in a test environment. In production it is suggested that you create a new account and assign it access to the databases you are backing up.

Lastly you'll want to make sure that TCP/IP is enabled as the communication protocol. This you'll find under the SQL Server Configuration Manager. If you are running a cluster you'll find the network settings under 'features' and the cluster configuration manager.

Once you have made sure that the above is complete you are then ready to run SQL backups with the 3X Appliance. In your 3X Manager you just need to set up a SQL backup set and proceed through the wizard. Remember when prompted for authentication you will be making use of the SQL account and not a Windows authentication account.

For information on SQL Restores check out this article: http://itrkoch.blogspot.com/2012/05/quick-microsoft-sql-restore-how-to.html