windream Data Backup windream GmbH, Bochum

Transcription

1 windream Data Backup windream GmbH, Bochum

2 Copyright 2005 by windream GmbH Wasserstr. 219 D Bochum Issue: 04/ All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form (print, photocopy, or any other form) or by any means without the express written permission of windream GmbH. Important Note All information and technical specifications in this book have been collected by the authors with great care. They cannot, however, either guarantee, take legal responsibility for or make any other warranty resulting from the use of this information. We would also like to point out that all software and hardware logos and names are the exclusive property of the Trademark, Brandname or Patent right holders. These are naturally protected by the appropriate laws and trade agreements.

3 Table of Contents i Table of Contents windream Data Backup 3 Reasons for a Backup Strategy 3 windream Data Backup 3 Current Status 4 Users and Groups 4 windream Database 4 Backup via SQL Server Enterprise Manager 5 Backup via Oracle Enterprise Manager 6 windream Database Backup via Seagate Backup Exec 7 File Storage 8 ObjectStore / Long-Term Archive 8 Data and Register Files 9 Configuration Files and Logfiles 10 CD-R-Archiving 12 Automized Generation of Media under Windows 13 Automized Generation of Media under UNIX 13 Creation of Backup Copies for MO/WORM Media under UNIX 13 Registry 13 Backup at runtime 14 Backup at a specific date 15 Data that might not have been saved 15 Recovery of windream Data 16 Basic Requirements 16 Users and Groups 16 windream database 17 Recovery of File Storage 18 ObjectStore / Long-Term Archive 19 Recovery of the Archive or Jukebox Media 19 Registry 19 Appendix 21 Registry 21

4

5 windream Data Backup 3 windream Data Backup Reasons for a Backup Strategy The objective of this document is to present strategies for an administrator to backup system data, and particularly windream data, so that they can be recovered in case of a system crash, hard disk or general failure. A prerequisite is in that case, that the backup itself can be done, while windream is operating, so that windream services have not to be stopped. This is necessary for the uninterrupted operation of windream. Data sources that are directly connected with windream and that are to be backed up are the database, the file storage, the user and group information, the program files, Registry-entries, configuration files, and optionally the ObjectStore. This document describes the physical storage locations of the various systems and what data has to be backed up particularly. The backup of windream data on an operating windream system can lead to the situation, that the backup is not consistent, due to the fact, that among other things not all windream data sources can be backed up simultaneously. In chapter 3 Data Backup at Runtime we will show what kind of inconsistencies can occur and what steps are necessary to avoid them. Beside the backup of the windream data, a backup-concept for saving enterprise data should already exist; or rather the systems and particularly important data should regularly be saved. This document does not serve as a concept for all company data, as it only covers the backup of relevant windream data. Note: Please carefully consider the system requirements published by windream GmbH, which must be fulfilled to operate a windream system correctly. windream Data Backup This approach describes the backup of data generated and administered by windream in operation mode. These data are the windream file storage, windream database (SQL Server or Oracle), ObjectStore or windream long-term archive, the different log-files and scripts created by the administrator etc.

6 4 windream Data Backup Current Status Currently, a lot of windream systems are only saved as a full-backup. This means that dynamic and static windream data will be saved by specific applications. Regarding windream, this means, that e.g. even the windream executable files are saved, although they do not change after the installation. Users and Groups windream obtains user and group information from the Windows userand group-administration. Depending on the system configuration it has to be paid attention that all windream users and groups from all domains used are backed up from time to time. This is necessary to back up user IDs, too, that are used by Windows internally. A respective tool to back up and synchronize users and groups will be available. This tool will export the user and group structure into a file that has to be saved. This file can be imported via the tool, if necessary, for recovery to restore the groups and users. The following configurations for the determination of windream users or groups are possible: windream standalone server (no member of another domain, no trusted domains in use): Users and groups of the standalone system have to be backed up windream server on a server that is member of a domain (installation not on the PDC or BDC), users and groups are exclusively received from the PDC or from trusted domains: Backup of local groups or users not necessary. Groups and users of the PDC or the trusted domain have to be backed up. windream server on a server that is member of a domain (installation not on the PDC or BDC), local users and groups are used: Backup of groups or users of all domains used (PDC, local, trusted domains). windream server on the PDC (NOT recommended): Backup of groups or users of the PDC and trusted domains. windream Database The windream database including the installed Stored Procedures with the Setup can regularly and automatically be saved over the Enterprise Manager of the SQL Server or the Enterprise Manager of Oracle. For the fulltext catalog windreamft of the SQL Server used for the fulltext search of windream, a backup possibility does not exist in the respective administration tools. However, the fulltext catalog is refilled after restoring the windream database in the fulltext table by once executing the function for starting a complete filling.

7 windream Data Backup 5 Fulltext indexing is executed with InterMedia Text over an Oracle Job. It is automatically created and configured with the installation of windream. When the database server cannot be started any more, the database can only be backed up by copying the relevant files with the explorer. SQL Server 7 <installationpath>\mssql7\data\windream.mdf and the logfile windream_log.ldf SQL Server \<installationpath>\mssql2000data\data\windrea 2000 m.mdf and the logfile windream_log.ldf Oracle \<installationpath>\oracle\oradata\<oracledb>\ Backup via SQL Server Enterprise Manager The backup, or rather the adjustments for the time schedule are executed over SQL Server Enterprise Manager. In the hierarchic representation of the database Server, the windream database is presented under the folder databases. If the entry windream is marked, 'All tasks 'Backup database' is called over the pop-up menu, or the listed function Backup database is called over the right window under General and Backup. In the dialog box SQL Server Backup windream different adjustments according to the requirements of the backup can be executed. Corresponding to the planned backup method, settings are made in this dialog box. You can find detailed descriptions of the different areas in the documentations for SQL Server. If a scheduled task for the automatic backup of the windream database or transaction protocols shall be created, the process can be enabled over the check box for the time schedule. The following dialog box is opened over the accompanying Browse-button; here, further adjustments can be executed. If the rules for the repetition of the backups shall be changed, another dialog box has to be opened over the command button for changing. Available jobs for the backup of the database or transaction protocols are listed over $Server\Administration\SQL Server-Agent\Jobs, and the properties are displayed. The storage place of the transaction protocol is set as default. It is located in the SQL Server Installation directory. According to the infrastructure of the database, and because of security reasons, we recommend to save the transaction protocol in another directory or on another Server. During the backup process, you will have to take care that also the swapped transaction protocol is included into the regular backups, too. The file(s) selected for the backup of the windream database must regularly be saved on external media (tapes, CD-R etc.), so that the

8 6 windream Data Backup database, after a total failure or the demolition of the corresponding hard disk, can be restored by the backup files. Backup via Oracle Enterprise Manager When setting up the Backup jobs for backup of the Oracle database or the windream Tablespaces over the Enterprise Manager or over the Oracle DBA Studio, you have to take care that the services of the Oracle Agents and the Oracle ManagementServer are started. Otherwise, the backup functions cannot be executed. This is also valid for the setup of the time schedules for backup/recovery/export/import of the Oracle database. When selecting the backup options, you will have to take care that the first backup is complete. After that, incremental backups should regularly be executed; however, complete backups are additionally required. The database must operate in archive log mode, if the backup of a tablespace shall be valid. Starting the Enterprise Manager Console The console of the Enterprise Managers is started over the Oracle program group. The login to the Console has to be executed as system administrator; as otherwise, there will be no access to the functionalities for the backup of the windream database. Starting Oracle DBA Studio For starting Oracle DBA Studio, the same requirements as for the Enterprise Manager Console are valid. Creating Backup Configuration A backup configuration can be created that is used as basis during the backup strategy selection in the option for predefining a backup strategy. Different recovery catalogs can be created for the backup configuration. Information on the configuration is either filed in a control file or in another Oracle database. Selection of the backup strategy and definition of the time schedule When selecting the backup strategy, an available strategy can be used, or an own strategy can be adjusted. Then, it is selected, which object shall be saved; this means, it is selected whether a whole database or only tablespaces, or data files shall be saved with the backup. Here, the option Complete database, or even better Tablespaces should be selected. Then, in the following selection dialog, the tablespace (windream database) is selected.

9 windream Data Backup 7 When selecting the backup options, you have to take care that the database is regularly and completely saved. Besides, an incremental backup should automatically be executed, for instance once a day. windream Database Backup via Seagate Backup Exec Seagate provides different Agents with its product Backup Exec; they are particularly specified for the backup of Oracle and SQL Server databases, tables, and transaction protocols, and also for the backup of SQL Server and Oracle databases. Agent for Microsoft SQL Server The agent for Microsoft SQL Server is a tool which can be handled intuitively. With this tool, particularly an SQL Server installation can be saved, and a recovery of the SQL Server can be executed. The Agent accesses SQL Server to save and restore the available databases with their tables and transaction protocols over different methods. Here, you should also take care that the consistency of the database and data of the ObjectStore/long-term archive are guaranteed with a backup. This is why a single backup of user-defined tables does not make any sense; rather, a complete backup of the database should be executed once a week, and a backup of the transaction protocols should be executed once a day. Oracle Database Agent The Windows NT Oracle-Agent as add-on of Backup Exec (Seagate Software) allows the backup of the tablespace data, the archived logfiles of Oracle, and the control file backup. The backup of the data can be executed in database-online mode, so that the users can still work with windream or access the database. When a tablespace in online-mode is saved, it is set into backup mode. After backup, the tablespace is again switched to online mode. However, offline backups with database stopped are generally recommended, as with this method the recovery of the database after an emergency case is easier. The Oracle Backup-Agent of Backup Exec requires a user account with certain database rights, in order to access the database for backup of the tablespaces, logfiles, or control files. In the Oracle-Database-Agent description, you can look up which rights are concerned. Additionally, you can find information on the work with the Oracle- Agent, e.g. how to save an online- or an offline-database, and which adjustments are required, in the Oracle-Database-Agent as well.

10 8 windream Data Backup File Storage The windream file storage is the storage place for windream documents that are still in the editing period, which depends on the life-cycle settings. Furthermore, it is also possible to save windream documents of windream version 2.5 or higher, which had been moved to the archive area over Archive immediately, or because of the expired editing period in the windream file storage. If all documents are saved in the file storage, there will be no backup of the windream ObjectStore. For backup of the windream file storage, it is required to shut down the windream DMS Service. The selected directories in the file storage for the different windream storages on the windream Server or on a connected drive are the relevant areas for the data backup. You have to take care that a backup also saves all subdirectories. The windream documents are hierarchically filed corresponding to the determined value for directory levels in the administration. ObjectStore / Long-Term Archive Precondition for the backup of the ObjectStore is: the mm-dam must not have access to the ObjectStore and has to be shut down. On a Windows Server, the service for the ObjectStore has to be stopped. You can find information on how to stop the mm-dam on a UNIX Server in the archive manual. The ObjectStore is in the area on the hard disks of the Server, which had been selected during the installation, or which had been configured later. For the backup of the ObjectStore and the accompanying configuration and logfiles it is necessary that the corresponding directories are saved with the conventional backup methods. The data of the ObjectStore are saved in so-called pools. There are different types of pools that can respectively be created when installing the ObjectStore or later. It is differentiated between: the directory-pool that hierarchically files the data in the folder structure of the Server, the filestream-pool, which serves as BLOB-container for a previously determined data volume. Filestream-pools are required e.g. for CD-R Archiving, and the Jukebox-pool required for the archiving on media in jukeboxes.

11 windream Data Backup 9 Pools are required for filing archived windream documents in the area of the document-type administration of the windream Management Console. If index data shall also be archived during the archiving of documents, a pool of the ObjectStore has to be assigned to the corresponding document-type. In any case, you have to consider the different registers that are administered in connection with the ObjectStore or rather the longterm archive during backup.. Additionally, information is saved into configuration files and log-files. The data and their folders that have to be saved are listed in the following tables. The most important files or directories, which, if possible, should be regularly saved (e.g. each day), are the object register in the directory.\data\mm-dam\, the 'mm-arc.ini', 'user.cfg' and the directory.\pools\ in the directory.\data\mm-dam\. This directory also contains the BLOB-register that includes information on a pool and particularly on the BLOBs saved there. Data and Register Files The data and register files of the ObjectStore are as default saved in the directory <MMUNIXVAR>\mm-dam\ (UNIX) or.\mm-dam\ (Windows). You have to take care on which Servers the different pools had been configured, so that all data are saved on all Servers used. In the following table, different files that must be saved for each pool-type are listed: Object to be saved Pools Path Filename Description In this directory, a further directory that must be saved exists for each pool. Object register Object register Object register that contains all entries for the BLOBs in the different pools. Filestream Pool \mmdam\pools\ \data\mmdam\pools\< Poolname> <WorldID>.< Poolname>.stat us <Worldid>.<P oolname>.volu me Here, the volume-file (BLOBcontainer) and a status-file are saved corresponding to the name of the

12 10 windream Data Backup Server (WorldID) and the filestream-pool (e.g. PERM). BlobRegister Directory Pools.\data\mmdam\Pools\< Poolname>\ \data\mmdam\pools\< Poolname> ObjectRegister $(MMUNIXV AR)\mmdam\ MediaRegister $(MMUNIXV AR)\mmdam\ <WorldID>.< Poolname>.br <Worldid>.<P oolname>.<nr > <Worldid>.<P oolname>.<nr >.req ObjectRegister MediaRegister. <Jukeboxname> The BLOBregister(s) of a filestream-pool (at least one file) contain(s) information on the pool and on the single BLOBs of a pool. In this directory all files are filed as binaries in socalled BLOBs and in the accompanying description-files corresponding to the name of the Server (WordID) and the directorypool (e.g. TEMP). Object register with all entries for the BLOBs in the different pools. Information on status of media in a CD-R Jukebox. The name of the jukebox describes the name of the jukebox defined in the file ObjectRegister. Configuration Files and Logfiles The logfiles of the ObjectStore are saved in the directory.\var\spool\megamedia\mm-dam\logs\ (UNIX) or <MMUNIXVAR>\log\ (Windows). The logfiles and their place of

13 windream Data Backup 11 storage depend on the storage media used. In the following table the different files are listed: Object to be saved Configuration files Configuration file for archive user Path Filename Description.\data\conf mm-arc.ini Configuration files for start of mm-arc and mm-dam, and indications for configuration of jukewrite.pl (Windows only).\data\conf mmpasswd.cfg Contains encrypted archive users (Windows, UNIX) created with mmpasswd. Logfiles.\data\log mm-arc.log mm-dam.log mm-tcp.log Registryentries Configuration file for jukewrite Configuration file for dobackup Configuration file for dobackup Mmunix.cfg $HKLM/Soft ware/a.i.s. GmbH/windr eam Objecstore/ Logfiles for the different Services Saving of registry-entries for the archive/objects tore under Windows in a file c jukewrite.cfg Configuration file for the function jukewrite (jukewrite.pl under Windows) $(MMUNIXV AR\mmdam\dobackup \ $(MMUNIXH OME\etc\ $MMUNIXH OME\etc seite_.cfg dobackup.cfg Mmunix.cfg Configuration file for media backup under HP-UX Configuration file for media backup under HP-UX Configuration file for startup

14 12 windream Data Backup script mm-dam.cfg \opt\megame dia\etc mm-dam.cfg Configuration file for starting the Archive backend Service under UNIX Mm-arc.cfg \opt\megame dia\etc mm-arc.cfg Configuration file for starting the Archive frontend Service under UNIX Logfiles $(MMUNIXV AR)\mmdam\log <Logfilename> Logfiles in the subdirectory of the MediaRegister giving information on the recording process of CD- Rs, e.g. jukewrite.log Trace files (MMUNIXVA R) \log UNIX: \var\spool\m egamedia\log <Logfiles> Different logfiles are saved in the indicated directory. CD-R-Archiving For CD-R archiving, at least two BLOB-Containers (also named Volume-Files ) with 640 MB are created for each pool during the installation of the archive. These BLOB-Containers serve as a collection of the windream documents, as CD-Rs cannot be recorded incrementally. If the Volume file is filled, the whole content is written on a CD-R. Corresponding programs that are described in the Archive manual can execute this either automatically or manually. In this context the second BLOB-Container is necessary, as it is recorded as soon as the first one is filled. This makes an uninterrupted storage of data into the ObjectStore possible. For recording a CD, the service for the windream ObjectStore has to be closed, or rather the mm-dam under UNIX. This is necessary for a problem-free recording of a CD. Many recorders can record a CD only in a state free of vibrations. This cannot be guaranteed when media is changed.

15 windream Data Backup 13 With the command jukewrite (under Windows: jukewritr.pl) complete volume files (also named BLOB-Containers) are recorded on a CD. For the writing process you can configure how many copies shall be created (Option: --copies=<number>). The configuration of jukewrite (jukewrite.pl) is executed over the configuration file jukewrite.cfg. The file jukewrite.log contains all log outputs, which, during a writing process, are created corresponding to the parameters determined in the configuration file. You can find more information on this topic in chapter 5 of the archive manual (Generation of media with CD-R Jukeboxes). Automized Generation of Media under Windows With the help of Scheduled tasks, a process can be started regularly or in a certain time frame under Windows. For this it is necessary to create a timetable that regularly executes the file jukewrite.bat. With this, the regular creation of media can be automized. The file jukewrite.bat is in the directory \bin\. It contains all necessary data for a correct launch of a media backup. Automized Generation of Media under UNIX With the command cron, an automatic recording during night can be controlled under UNIX. A detailed description of the command cron can be found in the respective UNIX documentation. Creation of Backup Copies for MO/WORM Media under UNIX There are different procedures for creating MO/WORM backup copies under UNIX, which depend on the operating systems used: on the one hand the media backup for directly controlled MO/WORM jukeboxes, and on the other hand for indirectly controlled MO/WORM jukeboxes. Concerning directly controlled MO/Jukeboxes, Windows, AIX and Solaris platforms are supported. There, copies can be created with the tool jukecopy, which is described in chapters 4 and 5 of the Archive manual. An incremental backup of the data is executed by adding the difference between the original and the copy to the backup-worm. Periods of time for the execution of backup can be controlled over the Cron -function under UNIX. For indirectly controlled WORM/MO Jukeboxes, the processes under HP-UX for continuing the copy are enabled over the function dobackup. Here, an incremental backup is executed as well so that not all data of the original WORM/MO have to be copied. The regular process of backup can be controlled over the Cron -function as well. Registry The important registry entries for windream are stored under the key:

16 14 windream Data Backup Backup at runtime HKEY_LOCAL_MACHINE\Software\A.I.S. GmbH\windream\<version-number>\ Generally the complete tree under " HKEY_LOCAL_MACHINE \Software\A.I.S. GmbH/windream" should be backed up. The respective command is: regedit -e c:\wmserver30bak.reg "HKEY_LOCAL_MACHINE\software\a.i.s. gmbh\windream" Note: The file is generated under Windows 2000 in unicode-format (regedit-5-format) and under Windows NT in ANSI-format (regedit-4- format). The unicoded file cannot be imported under Windows NT without conversion. After the installation of the windream server only specific entries of the key, e.g. for the reporting, are changed by adjusting the windream configuration. These entries are listed in the appendix of this document under Registry. Backup of windream data has to be carried out by a system administrator, who is logged in as windream main user at the same time. While saving all relevant windream data at runtime, you have to be aware that specific objects in the file-storage are in current access, and might not be backed up. This chapter shows which inconsistencies might occur. When saving windream data, it has to be observed, that certain taskplans used for the backup of database, FileStore, and possibly of the ObjectStore are matching. In case of a data recovery, all backupfiles of a specific date have to be restored. This is absolutely necessary for the correct referencing of windream documents in the FileStore or BLOBs (binary large objects) in the ObjectStore via the database, because the links have to link to real existing documents in the FileStore or to BLOBs in the ObjectStore. BLOB is the abbreviation for binary large object. They are the smallest possible storage unit in the windream ObjectStore. A BLOB is separated in so-called dataparts, which can contain additional information (e.g. database-information) beneath the document itself. All data, that is to be backed up, has to be listed in a backup-schedule with their regularly backup-dates and the way of backup, to generate a complete overview for the administrator.

17 windream Data Backup 15 Backup at a specific date With the use of mirrored servers and raid-arrays it is possible to ensure permanent data security concerning general operating system functions. Normally, not all windream data can be saved at a specific point in time. Thus it is not possible to guarantee complete consistency. Depending on the backup time, differences between the metadata in the database and the links to the files in the FileStore / the BLOBs in the ObjectStore can arise. The sequence of the different steps of the backup is relevant in that case. Firstly the database and secondly the file / ObjectStore have to be backed up. The difference, that was generated due to the different backup times, could then be determined on the base of the transaction log of the database. Other data like the user- and group-information, DCOMconfiguration, net-config, registry, shadow user information and the program files should not change (or at least only very little) during that difference of times. The administrator should not change any user- or group- information during that time. Data that might not have been saved Several services and systems can have access to windream documents during an online backup, so that files might not be backed up, because they are locked. The operating system itself can have access to specific files, so that these files cannot be accessed by the backup procedure. windream users might have opened windream documents, thus these documents cannot be saved. Documents could be accessed via the windream web portal and because of that are locked and cannot be saved. The windream fulltext-service is running and is extracting fulltext from windream documents. Those files cannot be saved, either. The backuptool should here start the process again after some time. For the document archiving process, the windream agent can be started in a scheduled task. The archiving task should be scheduled before or after the backup task. In that case a close analysis of the necessary period of time for both processes should be done in order to avoid collisions. An overlapping of both processes should definitively be avoided.

18 16 windream Data Backup Recovery of windream Data Basic Requirements For a complete recovery, the operating system and the required programs have to be restored. Among others, the required programs are SQL Server or the Oracle Server including the windream database that is installed with the Setup of the windream Server. The ObjectStore/archive has to be installed as well, which allows the restoring of windream data. Furthermore, the user groups and users including their assignments have to be created again. When installing the windream Server, you have to take care that for file storage the same directory path on which the backup of the file storage and the database are based is again created. Users and Groups When restoring windream data, it must be differetiated between the restoration of a complete Windows Server and the recovery of windream data. When a complete server is to be restored, it has to be taken into consideration that the windream user- and group-structure has to be restored. With the help of the respective recovery tool (which will be supplied by windream GmbH) it is possible to restore a former existing structure. When only windream data has to be restored, an adjustment of user IDs with the recovery tool is essential to provide system integrity. When restoring the user- and group-structure it has to be differentiated between different system architectures in use. The following listing presents some possible configurations and the related recovery procedures: 1. The windream server is installed on a standalone system, which is not a member of a domain and there are no trusted domains in use. The user- and group-structure of the standalone-system has to be restored after the complete Setup of the Windows Server. Thus, an import of the relevant data via the recovery-tool is necessary. In the following step the user-ids have to be adjusted to the windream database. 2. The windream Server is installed on a server which is member of a domain (the server is neither a PDC nor a BDC). User and group information are exclusively received from the PDC or from trusted domains. It is not necessary to restore the local users and groups for using windream. Ensure that the user-ids are adjusted. 3. In case the local system has received windream users, too, it will be necessary for a completely new installed server to restore the userand group-structure. A following adjusting process has to be done.

19 windream Data Backup when the windream server is installed on a PDC, the restoration process is equal to 1. windream database SQL Server In case the complete SQL Server is concerned with data loss, it has to be reinstalled. The respective installation medium should be available. Then, the windream database and the windream database fulltextextension have to be selected and installed with the windream Server installation (user-defined). After that, the last backup file created by the database should be restored in the corresponding directory (e.g. \MSSYL7\Backup\<Name of backup file>), or the respective medium should be made available, in order to restore the database with the help of the recovery function in the Enterprise Manager of the SQL Server. Select the entry windream in the list of the databases over the Enterprise Manager of SQL Server. In the right window of the Management Console, among others, the group for backup is displayed. There, select the function for restoring the database. In the dialog box for restoring the database, the database can be restored from a backup file, or from a medium. Select the respective option and confirm with OK. After having restored the windream database, the schedules for the regular backup of the database and transaction protocols should be checked and adjusted. The Enterprise Manager of SQL Server 7.0 does not offer the opportunity of saving the fulltext catalog (look at chapter Backup of the windream Database'). As the fulltext table with all entries has been restored with the recovery of the windream database under the entry fulltext, the fulltext catalog 'windreamft' created for the new installation must be refilled. For this it is necessary that the schedules for the filling (incrementally and completely) are checked or re-created. After that, the fulltext catalog should once be filled manually. This is executed over the respective function and when the fulltext catalog 'windreamft' is highlined. As the fulltext table can be very complex, the creation of the indices can take some time. Oracle In order to restore an Oracle Tablespace, the installed Oracle database and the installation of the windream database is required. Additionally, data of the last complete backup of the Tablespace and the

20 18 windream Data Backup accompanying incremental backups of the Tablespace up to the current date have to be available. Another requirement for the recovery of an Oracle database, a Tablespace, or data files are the rights of the logged-in user. The user must at least have Oracle SYSDBA rights, in order to be allowed to launch the recovery assistant. The database should run in ARCHIVELOG mode, so that the recovery is valid. For the recovery of an Oracle Tablespace, the Tablespace has to be set offline, so that besides the Tablespace also the incremental backup data can be restored. In status OPEN, it is only possible to restore the Tablespace and the data files. The recovery assistant of Oracle guides the user through different opportunities of selection or adjustments that are necessary for the recovery of a Tablespace or the archive log. After the recovery of the windream database, the schedules for the backup strategies should be checked and modified if necessary. Recovery of File Storage The last backup of the file storage has to be restored. In case the last backup was a complete backup, no further data for the file storage have to be restored. If incremental backups were executed after the last complete backup, they have to be restored. You have to take care that data are restored into the same directory path on which the backup was based The windream drive is a network drive and also behaves as a network drive when documents are deleted. The user has to confirm the deletion explicitly, and the data are not saved in the local Recycle Bin. However, windream has a separate recycle bin from which deleted windream documents can be restored or finally destroyed. In the windream Management Console, a corresponding search for deleted documents, e.g. according to user data, can be executed. Single or several documents including index data can be restored over the corresponding functions of the pop-up menu. You can find a detailed description of this function in chapter 8 of the windream manual (windream Administration windream Tools Recovery of Deleted Objects) or in the windream online help. The recovery function is controlled over a filter in the windream configuration of the Server. The file-types that are excluded from recovery because of exceptional features of certain Windowsapplications have to be determined in the list. Documents of these

21 windream Data Backup 19 listed file-types cannot be restored over the 'Restore' function. The corresponding dialog is described in detail in chapter windream Configuration of Server Filter Recovery of deleted Documents in the windream-help or in the manual in chapter 7 (System Configuration Server). ObjectStore / Long-Term Archive In order to restore data in the ObjectStore, the windream ObjectStore has to be installed with the help of the installation medium. The service for the ObjectStore must not be started during the restoration of the backup files. After this, the files that are listed in the chapter Backup of the windream ObjectStore have to be copied into the corresponding directories from the last backup medium. Then, in order to guarantee a data consistency regarding the database references, the backup of the windream database executed at the same point of time has to be restored. Recovery of the Archive or Jukebox Media During the recovery of the archive or the different pools, the different storage media, which are determined as storage places for the pools during the installation of the archive, have to be differentiated. If the whole archive installation should again have to be executed, the same configuration that existed before the data-crash has to be selected. The configuration can be found either in the installation protocol, or it is restored over the configuration files listed in the chapter Backup of the windream Archive. If a medium that has already been terminated is corrupt, it has to be substituted by the corresponding copy. The substitution is executed over the jukebox administration tools that are described in chapter 4 of the archive manual. With the tool 'jukeadm' it is possible to import a CD (copy) so that the CD can be recognized by the archive. In this case, a recovery of the windream database is not necessary. However, a copy of the substituted medium should be created before starting the archive! Registry In case of a backup, the restoration of the windream registry makes only sense, if the complete installation of the windream server was restored. When e.g. only a system backup was restored, and the windream server was newly installed, problems can arise when the paths are different. Thus, all entries including paths are to be checked before a backup. After a new installation it is always recommended in order to check the differences between the backed up and the new

22 20 windream Data Backup registry to directly backup the windream registry-branch and to compare it with the backup (e.g. with windiff).

23 Appendix 21 Appendix Registry The windream Registry includes, as mentioned in the 'Registry' chapter, different static and dynamic entries. In the following, a list of those keys can be found that might change due to e.g. changes in the windream configuration while windream is operating. Those keys should be saved on a regular basis in order to restore them properly. (a respective script that saves those keys in a *.reg-file can be provided on demand). The following listing shows the complete windream registry of a German testsystem, including all keys and the respective values: REGEDIT4 GmbH\windream\3.0] GmbH\windream\3.0\Database] "Servername"="testora2" "Provider"="ORAOLEDB.oracle" "Name"="windream" "PWFile"="C:\\PROGRA~1\\AIS~1.GMB\\windream\\W indream.pwf" "MaxPooledSessions"=dword: a "MaxPooledArchives"=dword: "MaxCachedBinaries"=dword:000003e8 "FulltextEnabled"="*.DOC*.TXT*.XLS*.HTM*.H TML*.PDF*.PPT" "CacheRootFolders"=dword: "CacheDeleteDelay"=dword: a "Temp"="C:\\Programme\\A.I.S. GmbH\\windream\\Temp" "FilestoreDefaultDir"="e:\\datenntdt" "DBIDDefault"="42" "OraTablespaceUsers"="USERS" "OraTablespaceTemp"="TEMP" "OraTablespaceIndex"="USERS" GmbH\windream\3.0\DBG] "Out"="yes" "Level"=dword: "ThrowCOMEvent"=dword:

24 22 Appendix "MaxErrorStackSize"=dword: "StackToClient"=dword: "FulltextTraceopts"="+fatal +error +warning" "TcpServiceTraceopts"="+fatal +error +warning" "ExcludeModules"="" "CurrentModulesSection"="Modules" GmbH\windream\3.0\FSD] "NoRecoverableTemplates"="*.~*.**.TMP*._Q_ DESKTOP.INI*.LCK*.BAK*.??$*.LDB*.LNK*.WB KTHUMBS.DB*.FM.*" "ExcludeProcessList"="explorerwinfile" GmbH\windream\3.0\Fulltext] "Reconnect"=dword: "Newscan"=dword: c "MaxSize"=dword:00000fa0 GmbH\windream\3.0\License] "Name"= "Company"= "Department"= "Key"= GmbH\windream\3.0\NLS] "Language"="049" "Path"="C:\\Programme\\A.I.S. GmbH\\windream\\NLS" "EditMode"="yes" "AvailableLang"="001#049" "BrowserMapping"="de#049,en#001" "LCIDMapping"="049#7/1/0,001#9/1/0" GmbH\windream\3.0\Reporting] GmbH\windream\3.0\Reporting\ArchiveAndDelete] "WriteLog"=dword: "AppendLog"=dword: "DialogShow"=dword: "DialogAutoClose"=dword: "NLSFileName"="WMArcMv" "NLSSection"="ArchiveAndDelete"

25 Appendix 23 "LogFileName"="C:\\Programme\\A.I.S. GmbH\\windream\\Reporting\\ArchiveAndDelete.lo g" GmbH\windream\3.0\Reporting\Export] "WriteLog"=dword: "AppendLog"=dword: "DialogShow"=dword: "DialogAutoClose"=dword: "NLSFileName"="WMODaEx" "NLSSection"="Export" "LogFileName"="C:\\Programme\\A.I.S. GmbH\\windream\\Reporting\\Export.log" GmbH\windream\3.0\Reporting\Import] "WriteLog"=dword: "AppendLog"=dword: "DialogShow"=dword: "DialogAutoClose"=dword: "NLSFileName"="WMODaEx" "NLSSection"="Import" "LogFileName"="C:\\Programme\\A.I.S. GmbH\\windream\\Reporting\\Import.log" "WindowPositionX"=dword: "WindowPositionY"=dword: f "Mode"=dword: GmbH\windream\3.0\Reporting\UndoCheckOut] "WriteLog"=dword: "AppendLog"=dword: "DialogShow"=dword: "DialogAutoClose"=dword: "NLSFileName"="WMODaEx" "NLSSection"="UndoCheckOut" "LogFileName"="C:\\Programme\\A.I.S. GmbH\\windream\\Reporting\\UndoCheckOut.log" GmbH\windream\3.0\Reporting\UserGroup] "WriteLog"=dword: "AppendLog"=dword: "DialogShow"=dword: "DialogAutoClose"=dword: "NLSFileName"="WMOMMC" "NLSSection"="UserGroup" "LogFileName"="C:\\Programme\\A.I.S. GmbH\\windream\\Reporting\\UserGroup.log"

26 24 Appendix "WindowPositionX"=dword: a "WindowPositionY"=dword: "Mode"=dword: GmbH\windream\3.0\Shell] "CCFlags"=dword: "DelayVfsConnect"=dword:00001b58 "CCLastService"="windream DMS-Service"