Technical Brief Backups and Repository Maintenance Overview Persystent Suite is comprised of various server based components. The purpose of this document is to define what site specific data that should be backed up and the procedures for properly backing up Persystent Suite servers. This document also covers the procedures used to clean up unused files in the shared repository. Backing up the Persystent SQL Database Backing up Shared Repository Backing up Images to a RAD file Shared Repository Maintenance Procedures Backing Up the Persystent SQL Database Requirements Microsoft SQL Server 2005 or later with Management Studio Additional information Persystent Suite utilizes a SQL database called PTC_SITE. This database should be backed up in accordance with your existing SQL backup software procedures. If Persystent Suite is the only SQL Database in your environment, then Persystent recommends to backup the PTC_SITE database using the internal SQL backup function. Backups can be configured with SQL built in backup functions or using a third party SQL backup agent (i.e. Symantec Backup Exec SQL backup agent). This document outlines the basic backup functions provided within the SQL application. Consult your backup vendor s documentation for SQL agent backup procedures. 1
Procedure Overview The example in this document will concentrate on using the SQL 2005 Management Studio when backing up the database. The procedure to configure Microsoft SQL Server 2005 backups is as follows: Use the Maintenance Wizard to define and schedule the backup job. If not using SQL 2005 or you utilize a third party SQL backup agent like Symantec Backup Exec, please contact your backup administrator for further assistance. To Backup Microsoft SQL 2005 Database 1. SQL 2005 provides the administrator with a maintenance plan wizard which steps through the process of creating a backup job and schedule. Run the Maintenance Wizard by right-clicking on Management Management Plans in SQL 2005 Management Studio. 2
2. Click the Next button to start the Wizard. 3. Create a Name for the backup plan 3
4. Then click on the Change button to edit the schedule for the plan. Schedule the backup for the desired time and days of the week. Click OK, then click Next. 4
5. Select the specific tasks to perform. In this step, select Backup Database (Full) task. Click Next. 6. Then select the order of tasks to run. Click Next 5
7. Select the Specific Database PTC_SITE in the dropdown menu. 8. Select the directory in which to store the backup database. Click Next. 6
9. Select the report options desired. Click Next. 10. Complete the Wizard. Click Finish. 11. Ensure that the file location that the SQL database backups reside in are being backed up by your backup administrator. 7
Backing Up Shared Repository, Images, and Host Information Requirements Due to the high volume of read/write transactions in the Persystent shared repository, it is recommended that all Persystent server services should be stopped when backing up the repository and host information. Additional Information The following is a list of directories used in the Persystent Suite installation and what information is stored in each of these directories. Program Files\Persystent\Repository\shared location of all shared files. This will be the largest directory in your repository. Program Files\Persystent\Repository\global\hdimages location of all base image pointer files. Program Files\Persystent\Repository\global\packages location of all software packages and pointer files. Program Files\Persystent\Repository\global\hosts location of all unique host image pointer files, boot logs, and heal logs. Procedure Overview The procedure to backup the shared repository including base images, client repair points, and backed up profiles is as follows: Stop all Persystent services on the server. Copy the following folders to an alternate location on a network or another drive. Restart all Persystent services. Backup the copied files using desired backup application. To Backup the Persystent Shared Repository 1. The stopping and starting of services and file copy process can be accomplished using a simple batch file. This example assumes that the D: drive is the location of the Persystent Server and Repository, and the Q: drive is the destination of the backup. Persystent Backup Script rem *************************************************** 8
rem Persystent Backup Routine rem Stopping Persystent Server Services echo Stopping Persystent services... net stop PersystentServer net stop RepositoryService net stop RemboServer net stop RemboODBC rem Creating Backup Directories if needed Q: CD\ md hosts md hdimages md packages md shared md server rem Copying Persystent files to Backup Location echo Copying Persystent Files to backup location... xcopy D:\Progra~1\Persystent\repository\shared Q:\shared /E /Y xcopy D:\Progra~1\Persystent\repository\global\hosts Q:\hosts /E /Y xcopy D:\Progra~1\Persystent\repository\global\hdimages Q:\hdimages /E /Y xcopy D:\Progra~1\Persystent\repository\global\packages Q:\packages /E /Y xcopy D:\progra~1\Persystent\server\settings.ini Q:\server /E /Y xcopy D:\progra~1\Persystent\server\rembo.conf Q:\server /E /Y xcopy D:\progra~1\Persystent\server\server.db Q:\server /E /Y rem *********************************************************** rem Restarting Persystent Server Services net start PersystentServer net start RepositoryService net start RemboServer net start RemboODBC 2. The files copied to the Q: drive should be backed up utilizing the existing backup solution. Backing Up Images to a RAD file Requirements Adequate disk space for RAD file to be created. Base Images created on Persystent server. 9
Procedure Overview Backing up images to a RAD file will allow all Base images to be placed in a single instance storage flat file. This can be useful for backup purposes as well as allowing these images to be imported into other Persystent Suite repository servers. The procedure to create a RAD file backup is as follows: On the Persystent repository server, open the Persystent Server Utility. Select the images to export. Select the location to create the RAD file. Export the image to the desired location. To Perform Repository Maintenance 1. Log into the Persystent server. Go to Start All Programs Persystent Persystent Server Utility. 2. Click the Export tab and then select the images that should be included in the RAD file. 3. Enter a name and location for the RAD file. 4. Click Export. The progress bar will display; the OK button will activate when completed. Shared Repository Maintenance Procedures Requirements All Persystent Server services should be stopped when performing repository maintenance. There should be enough disk space to allow the repository services to re-index the files. A good rule of thumb is at least 30% free space on the repository drive. Procedure Overview Example: 100GB repository should have at least 30GB free for the procedure. The maintenance routines can take between 15 minutes and 4 hours to complete based on the size of the shared file repository server, disk speed, and server specifications. Persystent recommends scheduling this routine during non-peak business hours. The imaging capability and client/server communications will be down during the maintenance window. Client computers however will continue to function normally during the maintenance period. Persystent recommends monthly repository maintenance to ensure optimal performance of the shared repository. The statshared command will mark all files that are currently in use in the repository. The sweepshared command will purge inactive files from the shared repository, freeing up disk space. 10
The procedure to perform repository maintenance is as follows: Stop all Persystent services. Execute the statshared and sweepshared repository utilities. (Optional) Run Disk defragmentation utility if the repository resides on a local disk. If the repository is on SAN storage, the SAN administrator should be responsible for disk maintenance procedures. Restart all Persystent services. To Perform Repository Maintenance 1. The stopping and starting of services and repository cleanup process can be accomplished using a simple batch file. This example assumes that the D: drive is the location of the Persystent Server and Repository. Persystent Shared Repository Maintenance Batch File rem Persystent Repository Maintenance rem Stopping Services @echo Stopping Persystent Repository Services... net stop RemboServer net stop RemboODBC rem Execute Repository Maintenance Commands @echo Running Repository Maintenance Commands... D: cd\progra~1\persystent\server rembo -d -v 3 -statshared rembo -d -v 3 -sweepshared rem Defragment Hard Drive (local disks only) @echo Running Disk Defragmentation... defrag D: -f -v rem Restart Persystent Repository Services @echo Starting Persystent Repository Services... net start RemboServer net start RemboODBC 11
Utopic Software 1215 East 6 th Ave. Tampa, FL 33605 Phone: (813) 444-2231 Fax: (813) 421-6523 Email: Sales@UtopicSoftware.com Web Site: www.utopicsoftware.com Copyright 2011 Utopic Software, LLC. All rights reserved. Printed in the United States of America. Information in this document is subject to change without notice. Utopic Software makes no warranties, express, implied, or statutory, as to the information in this document. This document contains proprietary information protected by copyright. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, without written permission of Utopic Software, LLC 1215 East 6 th Ave., Tampa, FL 33605, except as specified in the Product Warranty and License Terms. Utopic Software, LLC logos are registered trademarks; Persystent Suite is a trademark of Utopic Software, LLC. Microsoft, Windows Server 2008, Windows Server 2003, Windows XP, Windows Vista, Windows 7, Active Directory, SQL Server, SQL Express, and.net are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. All other registered trademarks and service marks mentioned are the property of their respective owner. 12