Table of Contents. 1 Introduction Recommendations MSSQL Example MSSQL 2012 Backup... 4

Transcription

1 tquest Backup

2 Table of Contents 1 Introduction Recommendations MSSQL Example MSSQL 2012 Backup To Create a Maintenance Plan Standard Volume Structure... 5 Page 2 of 6

3 1 Introduction The following backup instructions are recommendations only, and are for use by IT support teams or other IT professionals. During backup schedules, the performance of your systems may be reduced, schedule large backups processes outside of high usage periods. 2 Recommendations Indigo 4 recommends that a weekly full system backup (including registry) followed by a daily incremental or differential backup is implemented. A regular (hourly) transaction log backup with shrink is also highly recommended. Backups should not be stored locally. If a full system backup cannot be implemented, then as a minimum Indigo 4 recommends the tquest Database, Transaction Log and the following directory is backed up: D:\tQuest Note: Ensure any backup software used will not attempt to force processes to relinquish locks on files they may be using, as there is a high probability of causing data corruption. 3 MSSQL If the tquest MSSQL database and Transaction Log cannot be backed up using your backup software, or you do not wish to use your backup software, Indigo 4 recommends that you create Maintenance Plans in MSSQL. The following plans are recommended: Maintenance Plan to perform a full database backup once a week Maintenance Plan to perform a differential database backup daily Maintenance Plan to perform a Transaction Log backup and shrink hourly Note: Configuring all three Maintenance Plans is the most desirable option; the regularity of the Transaction Log backup and shrink is at each site s discretion. The most recent Transaction Log available minimises the amount of lost results/data. The best restoration following a system failure is achieved with the most recent backup. Maintenance of any SQL server database, along with its transaction log, is very important. Indigo 4 advises that the database is run in full recovery mode, thus allowing for point-in-time recovery of the data. If the database is run in full recovery mode and the transaction logs are not backed up and shrank regularly, they will continue to increase in size and may cause the system to fail due to lack of disk space. Page 3 of 6

4 3.1 Example MSSQL 2012 Backup The example given is for MSSQL 2012, but there is little difference between this and earlier versions of MSSQL. In this example the objective is to back up the database and transaction log; there are many other considerations that should be made to ensure that the database is kept in an optimum state, re-indexing, updating statistics etc. Please consult your SQL administrators or contact the Indigo 4 support team for more detail. 1. Open the Microsoft SQL Server Management Studio program; connect to the server where the relevant database(s) is situated. 2. Check Recovery Mode is set to Full. Database Properties > Options > Recovery Model: 3. Check the Microsoft SQL Server Agent is running, in SQL 2012 it s disabled by default. 4. Open the Microsoft SQL Server Configuration Manager program, select SQL Server Services. 5. In the results pane, right click on the SQL Server Agent instance and Select Properties. In the Service tab change the Start Mode to Automatic. In the Log On tab click Start, a green arrow on the SQL Server Agent icon, indicates that the SQL Server Agent is running successfully To Create a Maintenance Plan 1. Open Microsoft SQL Server Management Studio, in Object Explorer, expand the required server instance, and then expand Management. 2. Right-click Maintenance Plans and select Maintenance Plan Wizard. 3. Follow the steps of the wizard to create these Maintenance Plans: a. Maintenance Plan to perform a full database backup once a week b. Maintenance Plan to perform a differential database backup daily c. Maintenance Plan to perform a Transaction Log backup and shrink hourly 4. Give an appropriate name to the plan. 5. Schedule the plan as appropriate. 6. Select Back Up Database (Full), Back Up Database (Differential) or Back Up Database (Transaction Log) as required. 7. Select the tquest database. Select Backup set will expire, if required. 8. Configure the backup location (Back up to:). An external location should be used where possible. 9. Specify whether to generate a report for the Microsoft SQL Server Maintenance Plan and store it at a specific location. The report contains details of the steps executed by the Maintenance Plan, including any error information. 10. To ensure that the transaction log does not become too large the DBCC Shrinkfile command can be run after the transaction log backup. Page 4 of 6

5 11. Once the wizard has completed, right click the Back Up Database (Transaction Log) Maintenance Plan and select Modify, open the Toolbox (top left hand corner) and double click Execute T-SQL Statement Task. 12. Right click the Execute T-SQL Statement Task and select Edit, enter the following text (ensure that the database and transaction log name are correct); USE tquest; DBCC SHRINKFILE (tquest_log); GO 13. Ensure that the Execute T-SQL Statement Task is connected to Back Up Database (Transaction Log), Back Up Database (Transaction Log) should be run first. 4 Standard Volume Structure The following is an overview of a standard tquest installation layout. Occasionally this may vary according to sites requirements. C: (Operating System (OS)) Contains the OS and supporting applications, it would be unusual for Indigo 4 to install any software here, however, important information is stored in the OS registry. D: (Application) Contains the tquest application files and MSSQL tquest Transaction Log. E: (Database) contains MSSQL tquest Database. Ideally, Indigo 4 would prefer to keep the database volume exclusively for the database; however it may be used as temporary backup storage. In this situation, Indigo 4 strongly advises that once a backup file is created, it should be moved from the tquest server as soon as possible. Page 5 of 6

6 Version Control Date Author(s) Summary of changes Doc Version 11/05//2011 Chris Webster /10/2012 Mark Brook Additional details regarding transaction log maintenance /04/2014 Dave Beard Backup advice simplified to just cover database backup 1.2 Name Telephone Address EMIS Health Support Desk Terms relating to the release of this document This document contains confidential information belonging to EMIS Health and is for the intended recipient only. Where it contains information of a confidential nature, including without limitation, information relating to trade secrets, special terms or prices, these shall be deemed for the purpose of the Freedom of Information Act 2000, as information provided in confidence by EMIS Health and the disclosure of which would be prejudicial to EMIS Health commercial interests. The provision of this document is not intended to infer any commitment on the part of EMIS Health, to enter into a contract to supply any software or services described. EMIS Health Standard Terms of Business apply and are available on request. This material contains the valuable properties and trade secrets of EMIS Health, embodying substantial creative efforts and confidential information, ideas, and expressions, no part of which may be reproduced or transmitted in any form or by any means, or retained in any storage or retrieval system, without the express written permission of EMIS Health. Copyright EMIS Health 2015 Page 6 of 6