TRIM Integration with Data Protector

ManualsBrandsHP ManualsSoftwareHP Data Protector V6.11 Software

Table of Contents

Introduction ......................................................................................................................................... 3

Prerequisites ........................................................................................................................................ 3

TRIM Internals

...................................................................................................................................... 3

TRIM’s Data Organization

................................................................................................................. 3

TRIM’s Architecture

........................................................................................................................... 4

Implications for Backup

..................................................................................................................... 4

Sample Configurations

......................................................................................................................... 5

Sample Configuration of a TRIM System

............................................................................................. 5

Sample Backup Configuration

........................................................................................................... 5

Step-by-Step Guide for a TRIM Backup

................................................................................................... 7

Installing Data Protector

.................................................................................................................... 7

Preparing Data Protector for Backup

................................................................................................... 8

Setting up Devices

........................................................................................................................ 8

Finding the Locations of Data Components

...................................................................................... 8

Creating a Backup Specification for the Database

.......................................................................... 12

Creating a Backup Specification for the Document Store, Document Content Index, Audit Logs and Global

Configuration File ....................................................................................................................... 16

Performing a Backup

...................................................................................................................... 18

Performing a Restore

...................................................................................................................... 21

Restoring the Metadata Database

................................................................................................. 22

Restoring the Document Store, Document Content Index, Audit Logs and Global Configuration File

...... 22

Restarting Services

...................................................................................................................... 24

Further Considerations

........................................................................................................................ 24

Backup Frequencies

........................................................................................................................ 24

High Protection Using High Frequency Backups

............................................................................. 24

High Performance/Low Impact Setup Using Low Frequency Backups

................................................ 25

Procedures Following an Inconsistent Data Recovery

.......................................................................... 26

Scenario 1: Database is recovered but documents missing in the Document Store

.............................. 26

Scenario 2: All documents in the store but database recovered to a previous point in time .................. 28

Scenario 3: All documents and metadata recovered but content index out of date.

............................ 29

Summary of content (31 pages)

PAGE 1
TRIM Integration with Data Protector Table of Contents Introduction ......................................................................................................................................... 3 Prerequisites ........................................................................................................................................ 3 TRIM Internals......................................................................................................................................
PAGE 2
Legal Considerations ...................................................................................................................... 30 For more information ..........................................................................................................................
PAGE 3
Introduction This paper explains how HP Data Protector can be used to back up an HP TRIM system. It is intended for TRIM system administrators who have no knowledge of Data Protector but have a reasonable knowledge of TRIM’s architecture and data organization. Prerequisites For the practical parts in the second half of this paper, you need access to a running TRIM system or the knowledge of how to set one up.
PAGE 4
• One or more Document Stores Document Stores contain the actual files linked to individual records. The physical locations of the stores are defined in the corresponding Metadata Database. For each Dataset, you can also instruct TRIM to maintain the following: • A Document Content Index. The index facilitates fast indexed searches. It can always be rebuilt from the Document Stores, but this can take a considerable amount of time. The location of the index is held in the global configuration file.
PAGE 5
Sample Configurations Sample Configuration of a TRIM System As an example to explain how to design the backup strategy, Figure 3 shows the part of a sample TRIM system that is relevant for backups. Dataset A is distributed over several hosts. Dataset B is completely set up on one host. Different Datasets could also share hosts. Figure 3: Example Configuration of a TRIM System Sample Backup Configuration A possible backup approach is illustrated in Figure 4.
PAGE 6
Figure 4: Example Backup Configuration 6
PAGE 7
Step-by-Step Guide for a TRIM Backup The following sections use the concepts explained in the previous sections to explain how to accomplish a backup using Data Protector step-by-step, including installation of Data Protector itself. Make sure that you have familiarized yourself with these concepts, otherwise the steps in the following sections will not be clear.
PAGE 8
Figure 6: installing MS SQL Server Integration Preparing Data Protector for Backup The backup preparation process is divided into three tasks: • Setting up the target devices • Finding the locations of TRIM data components • Creating backup specifications for the different data components The following is a detailed description of each of the tasks. Setting up Devices To prepare Data Protector for backup, first set up logical devices on the Media Agents to serve as targets for backups.
PAGE 9
Figure 7: TRIM Enterprise Studio 9
PAGE 10
Figure 8: Database type and location 10
PAGE 11
3. To find the locations of the Document Stores, open the TRIM client with an administrator login and access the store management through Tools  Context Administration  Document Store…. The Full Directory field will tell you the exact location of each store. Here it is \\demo\TRIM_DATA\Corp\STORE\CO\1 (see Figure 9).
PAGE 12
4. To find the location of the Document Content Index for each Dataset, open properties of your event server as shown in Figure 10, and select the Configure Processes tab. If an index is configured, the complete path is displayed in the Document Content Indexing field. In this case it is \\demo\TRIM_DATA\Corp\DCI\CO, which is the path we will use in our example. Figure 10: Properties of Event Server 5.
PAGE 13
• Integration Guide for VMware, Sybase, NNM and NDMP To create a backup specification: 1. In Data Protector, in the Context List, click Backup. 2. In the Scoping Pane, expand Backup Specifications. 3. Right-click the type of item you want to back up (MS SQL Server in our example), and click Add Backup. See Figure 11.
PAGE 14
4. In the Create New Backup dialog box, leave the defaults and click OK. See Figure 12.
PAGE 15
5. Select the appropriate client and the application database and click Next. See Figure 13. Figure 13: Choosing the database 6. In the Source property page, expand the system that contains the objects that you want to back up and the select the sources you want backed up. See Figure 14. Figure 14: Adding backup specification: select sources 7. In addition to the Metadata Database itself (here “Corp”) it is highly advisable to back up the system databases up as well.
PAGE 16
Figure 15: Adding backup specification: choose device 10. The remaining steps are the same as usual. Refer to the Data Protector Concept Guide, Chapter 2, “Planning your backup strategy” for more information. 11. Finally save the backup specification, specifying an appropriate name. See Figure 16.
PAGE 17
In this paper, for simplicity, the Document Store, Document Content Index, Audit Logs and global configuration file will be backed up using one backup specification. In most cases it is better to put these into separate specifications, for example, if the different components have different schedules. See also “Further Considerations” later in this paper on this subject. To create a backup specification for file systems: 1. Right-click on Filesystem in the Backup Context, and click Add Backup.
PAGE 18
Figure 18: Selecting sources for the backup Figure 19: Selecting sources for the backup 4. The remaining steps are as usual. Again the final step is to save the backup specification with an appropriate name. Performing a Backup Backups are either triggered automatically if specified in the backup specification or you can start them manually by right-clicking each backup specification and selecting Start Backup as shown in Figure 20.
PAGE 19
Figure 20: Starting a backup For more information on the options in the Start Backup dialog (Figure 21), see the Data Protector online Help index “starting backup sessions”. In this paper a full backup will be performed. For each backup that is performed, Data Protector should show a backup session output similar to the one in Figure 22. When backups have been successfully performed for both the database and the file systems the backup is complete.
PAGE 20
Figure 21: Starting a Backup dialog 20
PAGE 21
Figure 22: Backup session output Performing a Restore Restoring from data loss is done in four steps: 1. Reinstall the necessary applications (TRIM Context and/or the database application, such as MS SQL Server) on the affected hosts. 2. Restore the lost data. 3. If necessary, perform actions to get consistent Datasets. 4. Restart the TRIM services. It is assumed that you know how to reinstall the necessary applications, so the following assumes that pristine installations of the applications exist.
PAGE 22
Restoring the Metadata Database 1. In the Context List, click Restore. 2. In the Scoping Pane, under Restore Objects, expand the appropriate data type (for example, MS SQL Server). 3. Expand the client system with the data you want to restore and then click the object that has the data. 4. In the Source property page, expand the object and then select all the databases to be restored, as shown in Figure 23. 5. Click Restore.
PAGE 23
Figure 24: Selecting restore sources 3. Open the Destination tab, and select Overwrite in the File Conflict Handling options. This will ensure that the global configuration file, automatically installed while reinstalling TRIM, will be overwritten by the backed-up version. Otherwise Data Protector will keep the new one.
PAGE 24
If everything performs correctly, Data Protector should show a restore session output similar to that in Figure 26. Figure 26: Restore Session Output Restarting Services Now that all data and the global configuration file are restored, you must tell TRIM to use the restored data and configuration by restarting TRIM’s services. To do this, select Start  Administrative Tools  Services and then restart all TRIM services. TRIM should now be fully recovered.
PAGE 25
Figure 27 illustrates such a strategy and what happens when a disaster occurs. When the disaster occurs, half-an-hour’s data is lost. To reduce the impact on the system, you could configure the backup to do a full backup nightly and an incremental backup every hour.
PAGE 26
Figure 28: Low frequency backup strategy Tue Wed Thu Fri Sat Sun Document Content Index Document Store Meta Data Database Mon Tue Wed Recreate Fri Thu Lost Lost Sat DISASTER Mon Lost Sun Procedures Following an Inconsistent Data Recovery In the event of a recovery, you may need to decide whether a more complete but inconsistent recovery is more advantageous than an older but consistent recovery.
PAGE 27
TRIM provides a Document Store Integrity Check which checks for any missing documents, although it takes time to execute in a large system. To invoke the check: 1. In the TRIM Context’s main menu, open the Document Stores window by selecting Tools  Context Administration  Document Stores… See Figure 30.
PAGE 28
2. In the Run Integrity Check dialog (see Figure 31) click OK to start the check. Figure 31: Run Integrity Check dialog Note that you can source documents from any document caches in the system (if available) and simply copy them to the document store. Scenario 2: All documents in the store but database recovered to a previous point in time There is no reverse document store integrity check in TRIM but the documents with no metadata need to be removed before normal operation can be resumed.
PAGE 29
• the file extension (here, “.doc”), which indicates the type of document and is the same as the original document that is registered. • the part of the file name between the leading c and the file extension is a unique base 36 number, used by the database in the reSID column of the TSRECELEC table to associate the document with its record. Figure 32 shows how the base 36 number and the decimal number relate to each other.
PAGE 30
Figure 33: Reindex dialog Legal Considerations When backing up a TRIM system, be aware that legal regulations can state the records must be deleted after a certain time. For example, the law might insist that you delete backups older than 2 years. How you do this depends heavily on the particular circumstances. One solution would be to set the backup frequency and backup retention time at a very small fraction of the legally required retention time.
PAGE 31
For more information www.hp.com/go/dataprotector © 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.