windream gmbh, bochumdownload.windream.com/wd40/dokumente/databackup.pdf · may be reproduced or...

windream

Data Backup

windream GmbH, Bochum

Copyright © 2005

bywindream GmbHWasserstr. 219D-44799 Bochum

Issue: 04/05 – 1.0.0.0

All rights reserved. No part of the contents of this bookmay be reproduced or transmitted in any form (print,photocopy, or any other form) or by any means withoutthe express written permission of windream GmbH.

Important NoteAll information and technical specifications in this book have been collectedby the authors with great care. They cannot, however, either guarantee,take legal responsibility for or make any other warranty resulting from theuse of this information.

We would also like to point out that all software and hardware logos andnames are the exclusive property of the Trademark, Brandname or Patentright holders. These are naturally protected by the appropriate laws andtrade agreements.

Table of Contents i

Table of Contents

windream Data Backup 3Reasons for a Backup Strategy 3windream Data Backup 3

Current Status 4Users and Groups 4windream Database 4Backup via SQL Server Enterprise Manager 5Backup via Oracle Enterprise Manager 6windream Database Backup via Seagate Backup Exec 7File Storage 8ObjectStore / Long-Term Archive 8Data and Register Files 9Configuration Files and Logfiles 10CD-R-Archiving 12Automized Generation of Media under Windows 13Automized Generation of Media under UNIX 13Creation of Backup Copies for MO/WORM Media under UNIX

13Registry 13

Backup at runtime 14Backup at a specific date 15Data that might not have been saved 15Recovery of windream Data 16

Basic Requirements 16Users and Groups 16windream database 17Recovery of File Storage 18ObjectStore / Long-Term Archive 19Recovery of the Archive or Jukebox Media 19Registry 19

Appendix 21Registry 21

windream Data Backup 3

windream Data BackupReasons for a Backup Strategy

The objective of this document is to present strategies for anadministrator to backup system data, and particularly windream data,so that they can be recovered in case of a system crash, hard disk orgeneral failure. A prerequisite is in that case, that the backup itself canbe done, while windream is operating, so that windream services havenot to be stopped. This is necessary for the uninterrupted operation ofwindream.

Data sources that are directly connected with windream and that are tobe backed up are the database, the file storage, the user and groupinformation, the program files, Registry-entries, configuration files, andoptionally the ObjectStore. This document describes the physicalstorage locations of the various systems and what data has to be backedup particularly.

The backup of windream data on an operating windream system canlead to the situation, that the backup is not consistent, due to the fact,that among other things not all windream data sources can be backedup simultaneously. In chapter 3 ‘Data Backup at Runtime’ we will showwhat kind of inconsistencies can occur and what steps are necessary toavoid them.

Beside the backup of the windream data, a backup-concept for savingenterprise data should already exist; or rather the systems andparticularly important data should regularly be saved. This documentdoes not serve as a concept for all company data, as it only covers thebackup of relevant windream data.

Note: Please carefully consider the system requirements publishedby windream GmbH, which must be fulfilled to operate awindream system correctly.

windream Data BackupThis approach describes the backup of data generated and administeredby windream in operation mode. These data are the windream filestorage, windream database (SQL Server or Oracle), ObjectStore orwindream long-term archive, the different log-files and scripts createdby the administrator etc.

4 windream Data Backup

Current StatusCurrently, a lot of windream systems are only saved as a full-backup.This means that dynamic and static windream data will be saved byspecific applications. Regarding windream, this means, that e.g. eventhe windream executable files are saved, although they do not changeafter the installation.

Users and Groupswindream obtains user and group information from the Windows user-and group-administration. Depending on the system configuration ithas to be paid attention that all windream users and groups from alldomains used are backed up from time to time. This is necessary toback up user IDs, too, that are used by Windows internally.

A respective tool to back up and synchronize users and groups will beavailable. This tool will export the user and group structure into a filethat 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 usersor groups are possible:

• windream standalone server (no member of another domain, notrusted domains in use): Users and groups of the standalone systemhave 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 areexclusively received from the PDC or from trusted domains:Backup of local groups or users not necessary. Groups and users ofthe 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 areused: Backup of groups or users of all domains used (PDC, local,trusted domains).

• windream server on the PDC (NOT recommended): Backup ofgroups or users of the PDC and trusted domains.

windream DatabaseThe windream database including the installed Stored Procedures withthe Setup can regularly and automatically be saved over the EnterpriseManager of the SQL Server or the Enterprise Manager of Oracle.

For the fulltext catalog ’windreamft’ of the SQL Server used for thefulltext search of windream, a backup possibility does not exist in therespective administration tools. However, the fulltext catalog is refilledafter restoring the windream database in the fulltext table by onceexecuting the function for starting a complete filling.


Fulltext indexing is executed with InterMedia Text over an Oracle Job.It is automatically created and configured with the installation ofwindream.

When the database server cannot be started any more, the database canonly be backed up by copying the relevant files with the explorer.

SQL Server 7 <installationpath>\mssql7\Data\windream.mdfand the logfile windream_log.ldf

SQL Server2000

\<installationpath>\mssql2000data\Data\windream.mdf and the logfile windream_log.ldf

Oracle \<installationpath>\oracle\oradata\<oracledb>\

Backup via SQL Server Enterprise ManagerThe backup, or rather the adjustments for the time schedule areexecuted over SQL Server Enterprise Manager. In the hierarchicrepresentation of the database Server, the windream database ispresented under the folder ‘databases’. If the entry ‘windream’ ismarked, 'All tasks 'Backup database' is called over the pop-up menu,or the listed function ’Backup database’ is called over the right windowunder ‘General’ and ‘Backup’. In the dialog box ‘SQL Server Backup –windream’ different adjustments according to the requirements of thebackup can be executed.

Corresponding to the planned backup method, settings are made in thisdialog box. You can find detailed descriptions of the different areas inthe documentations for SQL Server.

If a scheduled task for the automatic backup of the windream databaseor transaction protocols shall be created, the process can be enabledover the check box for the time schedule. The following dialog box isopened over the accompanying Browse-button; here, furtheradjustments can be executed.

If the rules for the repetition of the backups shall be changed, anotherdialog box has to be opened over the command button for changing.

Available jobs for the backup of the database or transaction protocolsare listed over $Server\Administration\SQL Server-Agent\Jobs, andthe properties are displayed.

The storage place of the transaction protocol is set as default. It islocated in the SQL Server Installation directory. According to theinfrastructure of the database, and because of security reasons, werecommend to save the transaction protocol in another directory or onanother Server. During the backup process, you will have to take carethat also the swapped transaction protocol is included into the regularbackups, too.

The file(s) selected for the backup of the windream database mustregularly be saved on external media (tapes, CD-R etc.), so that the


database, after a total failure or the demolition of the correspondinghard disk, can be restored by the backup files.

Backup via Oracle Enterprise ManagerWhen setting up the Backup jobs for backup of the Oracle database orthe windream Tablespaces over the Enterprise Manager or over theOracle DBA Studio, you have to take care that the services of theOracle Agents and the Oracle ManagementServer are started.Otherwise, the backup functions cannot be executed. This is also validfor the setup of the time schedules forbackup/recovery/export/import of the Oracle database.

When selecting the backup options, you will have to take care that thefirst backup is complete. After that, incremental backups shouldregularly be executed; however, complete backups are additionallyrequired.

The database must operate in archive log mode, if the backup of atablespace shall be valid.

Starting the Enterprise Manager ConsoleThe console of the Enterprise Managers is started over the Oracleprogram group. The login to the Console has to be executed as systemadministrator; as otherwise, there will be no access to the functionalitiesfor the backup of the windream database.

Starting Oracle DBA StudioFor starting Oracle DBA Studio, the same requirements as for theEnterprise Manager Console are valid.

Creating Backup ConfigurationA backup configuration can be created that is used as basis during thebackup strategy selection in the option for predefining a backupstrategy. Different recovery catalogs can be created for the backupconfiguration. Information on the configuration is either filed in acontrol file or in another Oracle database.

Selection of the backup strategy and definition of the timescheduleWhen 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 isselected whether a whole database or only tablespaces, or data filesshall be saved with the backup.

Here, the option ’Complete database’, or even better ‘Tablespaces’should be selected. Then, in the following selection dialog, thetablespace (windream database) is selected.


When selecting the backup options, you have to take care that thedatabase is regularly and completely saved. Besides, an incrementalbackup should automatically be executed, for instance once a day.

windream Database Backup via Seagate BackupExecSeagate provides different Agents with its product Backup Exec; theyare particularly specified for the backup of Oracle and SQL Serverdatabases, tables, and transaction protocols, and also for the backup ofSQL Server and Oracle databases.

Agent for Microsoft SQL ServerThe agent for Microsoft SQL Server is a tool which can be handledintuitively. With this tool, particularly an SQL Server installation can besaved, and a recovery of the SQL Server can be executed.

The Agent accesses SQL Server to save and restore the availabledatabases with their tables and transaction protocols over differentmethods. Here, you should also take care that the consistency of thedatabase and data of the ObjectStore/long-term archive are guaranteedwith a backup. This is why a single backup of user-defined tables doesnot make any sense; rather, a complete backup of the database shouldbe executed once a week, and a backup of the transaction protocolsshould be executed once a day.

Oracle Database AgentThe Windows NT Oracle-Agent as add-on of Backup Exec (SeagateSoftware) allows the backup of the tablespace data, the archived logfilesof Oracle, and the control file backup.

The backup of the data can be executed in database-online mode, sothat 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 generallyrecommended, as with this method the recovery of the database afteran emergency case is easier.

The Oracle Backup-Agent of Backup Exec requires a user account withcertain database rights, in order to access the database for backup ofthe tablespaces, logfiles, or control files. In the Oracle-Database-Agentdescription, 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 whichadjustments are required, in the Oracle-Database-Agent as well.


File StorageThe windream file storage is the storage place for windreamdocuments that are still in the editing period, which depends on thelife-cycle settings. Furthermore, it is also possible to save windreamdocuments of windream version 2.5 or higher, which had been movedto the archive area over ‘Archive immediately’, or because of theexpired editing period in the windream file storage. If all documentsare saved in the file storage, there will be no backup of the windreamObjectStore.

For backup of the windream file storage, it is required to shut downthe windream DMS Service.

The selected directories in the file storage for the different windreamstorages on the windream Server or on a connected drive are therelevant areas for the data backup.

You have to take care that a backup also saves all subdirectories. Thewindream documents are hierarchically filed corresponding to thedetermined value for directory levels in the administration.

ObjectStore / Long-Term ArchivePrecondition for the backup of the ObjectStore is: the mm-dam mustnot have access to the ObjectStore and has to be shut down. On aWindows Server, the service for the ObjectStore has to be stopped.You can find information on how to stop the mm-dam on a UNIXServer in the archive manual.

The ObjectStore is in the area on the hard disks of the Server, whichhad been selected during the installation, or which had been configuredlater. For the backup of the ObjectStore and the accompanyingconfiguration and logfiles it is necessary that the correspondingdirectories are saved with the conventional backup methods.

The data of the ObjectStore are saved in so-called pools. There aredifferent types of pools that can respectively be created when installingthe ObjectStore or later.

It is differentiated between:

• the directory-pool that hierarchically files the data in the folderstructure of the Server,

• the filestream-pool, which serves as BLOB-container for apreviously determined data volume. Filestream-pools are requirede.g. for CD-R Archiving,

• and the Jukebox-pool required for the archiving on media injukeboxes.


Pools are required for filing archived windream documents in the areaof the document-type administration of the windream ManagementConsole. If index data shall also be archived during the archiving ofdocuments, a pool of the ObjectStore has to be assigned to thecorresponding document-type.

In any case, you have to consider the different registers that areadministered in connection with the ObjectStore or rather the long-term 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 thefollowing tables. The most important files or directories, which, ifpossible, should be regularly saved (e.g. each day), are the objectregister in the directory .\data\mm-dam\, the 'mm-arc.ini', 'user.cfg'and the directory .\Pools\ in the directory .\data\mm-dam\. Thisdirectory also contains the BLOB-register that includes information ona pool and particularly on the BLOBs saved there.

Data and Register FilesThe data and register files of the ObjectStore are as default saved in thedirectory <MMUNIXVAR>\mm-dam\ (UNIX) or .\mm-dam\(Windows). You have to take care on which Servers the different poolshad been configured, so that all data are saved on all Servers used. Inthe following table, different files that must be saved for each pool-typeare listed:

Object to besaved

Path Filename Description

Pools \mm-dam\Pools\

In this directory,a furtherdirectory thatmust be savedexists for eachpool.

Object register Object register Object registerthat contains allentries for theBLOBs in thedifferent pools.

FilestreamPool

\data\mm-dam\Pools\<Poolname>

<WorldID>.<Poolname>.status

<Worldid>.<Poolname>.volume

Here, thevolume-file(BLOB-container) and astatus-file aresavedcorresponding tothe name of the


Server (WorldID)and thefilestream-pool(e.g. PERM).

BlobRegister .\data\mm-dam\Pools\<Poolname>\

<WorldID>.<Poolname>.br

The BLOB-register(s) of afilestream-pool(at least one file)contain(s)information onthe pool and onthe single BLOBsof a pool.

DirectoryPools

\data\mm-dam\Pools\<Poolname>

<Worldid>.<Poolname>.<nr>

<Worldid>.<Poolname>.<nr>.req

In this directoryall files are filedas binaries in so-called BLOBsand in theaccompanyingdescription-filescorresponding tothe name of theServer (WordID)and the directory-pool (e.g.TEMP).

ObjectRegister $(MMUNIXVAR)\mm-dam\

ObjectRegister Object registerwith all entriesfor the BLOBsin the differentpools.

MediaRegister $(MMUNIXVAR)\mm-dam\

MediaRegister.<Jukebox-name>

Information onstatus of media ina CD-R Jukebox.The name of thejukebox describesthe name of thejukebox definedin the fileObjectRegister.

Configuration Files and LogfilesThe 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


storage depend on the storage media used. In the following table thedifferent files are listed:

Object to besaved

Path Filename Description

Configurationfiles

.\data\conf mm-arc.ini Configurationfiles for start ofmm-arc andmm-dam, andindications forconfiguration ofjukewrite.pl(Windows only)

Configurationfile forarchive user

.\data\conf mmpasswd.cfg Containsencryptedarchive users(Windows,UNIX) createdwith mmpasswd.

Logfiles .\data\log mm-arc.log

mm-dam.log

mm-tcp.log

Logfiles for thedifferentServices

Registry-entries

$HKLM/Software/A.I.S.GmbH/windreamObjecstore/

Saving ofregistry-entriesfor thearchive/ObjectStore underWindows in afile

Configurationfile forjukewrite

c jukewrite.cfg Configurationfile for thefunctionjukewrite(jukewrite.plunder Windows)

Configurationfile fordobackup

$(MMUNIXVAR\mm-dam\dobackup\

seite_.cfg Configurationfile for mediabackup underHP-UX

Configurationfile fordobackup

$(MMUNIXHOME\etc\

dobackup.cfg Configurationfile for mediabackup underHP-UX

Mmunix.cfg $MMUNIXHOME\etc

Mmunix.cfg Configurationfile for startup


script

mm-dam.cfg \opt\MegaMedia\etc

mm-dam.cfg Configurationfile for startingthe Archivebackend Serviceunder UNIX

Mm-arc.cfg \opt\MegaMedia\etc

mm-arc.cfg Configurationfile for startingthe Archivefrontend Serviceunder UNIX

Logfiles $(MMUNIXVAR)\mm-dam\log

<Logfile-name>

Logfiles in thesubdirectory oftheMediaRegistergivinginformation onthe recordingprocess of CD-Rs, e.g.jukewrite.log

Trace files (MMUNIXVAR) \log

UNIX:\var\spool\MegaMedia\log

<Logfiles> Different logfilesare saved in theindicateddirectory.

CD-R-ArchivingFor CD-R archiving, at least two BLOB-Containers (also namedVolume-Files ) with 640 MB are created for each pool during theinstallation of the archive. These BLOB-Containers serve as acollection of the windream documents, as CD-Rs cannot be recordedincrementally. If the Volume file is filled, the whole content is writtenon a CD-R. Corresponding programs that are described in the Archivemanual can execute this either automatically or manually.

In this context the second BLOB-Container is necessary, as it isrecorded as soon as the first one is filled. This makes an uninterruptedstorage of data into the ObjectStore possible.

For recording a CD, the service for the windream ObjectStore has tobe closed, or rather the mm-dam under UNIX. This is necessary for aproblem-free recording of a CD. Many recorders can record a CD onlyin a state free of vibrations. This cannot be guaranteed when media ischanged.


With the command jukewrite (under Windows: jukewritr.pl) completevolume files (also named BLOB-Containers) are recorded on a CD.For the writing process you can configure how many copies shall becreated (Option: --copies=<number>). The configuration of jukewrite(jukewrite.pl) is executed over the configuration file jukewrite.cfg. Thefile jukewrite.log contains all log outputs, which, during a writingprocess, are created corresponding to the parameters determined in theconfiguration file.

You can find more information on this topic in chapter 5 of the archivemanual (Generation of media with CD-R Jukeboxes).

Automized Generation of Media under WindowsWith the help of ‘Scheduled tasks’, a process can be started regularly orin a certain time frame under Windows. For this it is necessary to createa timetable that regularly executes the file ‘jukewrite.bat’. With this, theregular creation of media can be automized. The file jukewrite.bat is inthe directory \bin\. It contains all necessary data for a correct launchof a media backup.

Automized Generation of Media under UNIXWith the command cron, an automatic recording during night can becontrolled under UNIX. A detailed description of the command croncan be found in the respective UNIX documentation.

Creation of Backup Copies for MO/WORM Mediaunder UNIXThere are different procedures for creating MO/WORM backupcopies under UNIX, which depend on the operating systems used: onthe one hand the media backup for directly controlled MO/WORMjukeboxes, and on the other hand for indirectly controlledMO/WORM jukeboxes.Concerning directly controlled MO/Jukeboxes, Windows, AIX andSolaris platforms are supported. There, copies can be created with thetool ‘jukecopy’, which is described in chapters 4 and 5 of the Archivemanual. An incremental backup of the data is executed by adding thedifference 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 underHP-UX for continuing the copy are enabled over the function‘dobackup’. Here, an incremental backup is executed as well so that notall data of the original WORM/MO have to be copied. The regularprocess of backup can be controlled over the ‘Cron’-function as well.

RegistryThe important registry entries for windream are stored under the key:


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 NTwithout conversion.

After the installation of the windream server only specific entries of thekey, e.g. for the reporting, are changed by adjusting the windreamconfiguration. These entries are listed in the appendix of this documentunder Registry.

Backup at runtimeBackup of windream data has to be carried out by a systemadministrator, who is logged in as windream main user at the sametime.

While saving all relevant windream data at runtime, you have to beaware that specific objects in the file-storage are in current access, andmight not be backed up. This chapter shows which inconsistenciesmight occur.

When saving windream data, it has to be observed, that certaintaskplans used for the backup of database, FileStore, and possibly ofthe ObjectStore are matching. In case of a data recovery, all backup-files of a specific date have to be restored. This is absolutely necessaryfor the correct referencing of windream documents in the FileStore orBLOBs (binary large objects) in the ObjectStore via the database,because the links have to link to real existing documents in theFileStore or to BLOBs in the ObjectStore.

BLOB is the abbreviation for binary large object. They are the smallestpossible storage unit in the windream ObjectStore. A BLOB isseparated in so-called dataparts, which can contain additionalinformation (e.g. database-information) beneath the document itself.

All data, that is to be backed up, has to be listed in a backup-schedulewith their regularly backup-dates and the way of backup, to generate acomplete overview for the administrator.


With the use of mirrored servers and raid-arrays it is possible to ensurepermanent data security concerning general operating system functions.

Backup at a specific dateNormally, not all windream data can be saved at a specific point intime. Thus it is not possible to guarantee complete consistency.Depending on the backup time, differences between the metadata inthe database and the links to the files in the FileStore / the BLOBs inthe ObjectStore can arise.

The sequence of the different steps of the backup is relevant in thatcase. Firstly the database and secondly the file / ObjectStore have to bebacked up. The difference, that was generated due to the differentbackup times, could then be determined on the base of the transactionlog of the database.

Other data like the user- and group-information, DCOM-configuration, net-config, registry, shadow user information and theprogram files should not change (or at least only very little) during thatdifference of times. The administrator should not change any user- orgroup- information during that time.

Data that might not have been savedSeveral services and systems can have access to windream documentsduring an online backup, so that files might not be backed up, becausethey are locked.

The operating system itself can have access to specific files, so thatthese files cannot be accessed by the backup procedure.

windream users might have opened windream documents, thus thesedocuments cannot be saved.

Documents could be accessed via the windream web portal andbecause of that are locked and cannot be saved.

The windream fulltext-service is running and is extracting fulltext fromwindream documents. Those files cannot be saved, either. The backup-tool should here start the process again after some time.

For the document archiving process, the windream agent can bestarted in a scheduled task. The archiving task should be scheduledbefore or after the backup task. In that case a close analysis of thenecessary period of time for both processes should be done in order toavoid collisions. An overlapping of both processes should definitivelybe avoided.


Recovery of windream Data

Basic RequirementsFor a complete recovery, the operating system and the requiredprograms have to be restored. Among others, the required programsare SQL Server or the Oracle Server including the windream databasethat is installed with the Setup of the windream Server. TheObjectStore/archive has to be installed as well, which allows therestoring of windream data. Furthermore, the user groups and usersincluding their assignments have to be created again.

When installing the windream Server, you have to take care that for filestorage the same directory path on which the backup of the file storageand the database are based is again created.

Users and GroupsWhen restoring windream data, it must be differetiated between therestoration of a complete Windows Server and the recovery ofwindream data.

When a complete server is to be restored, it has to be taken intoconsideration that the windream user- and group-structure has to berestored. With the help of the respective recovery tool (which will besupplied by windream GmbH) it is possible to restore a formerexisting structure.

When only windream data has to be restored, an adjustment of userIDs with the recovery tool is essential to provide system integrity.

When restoring the user- and group-structure it has to be differentiatedbetween different system architectures in use. The following listingpresents some possible configurations and the related recoveryprocedures:

1. The windream server is installed on a standalone system, which isnot a member of a domain and there are no trusted domains inuse. The user- and group-structure of the standalone-system has tobe restored after the complete Setup of the Windows Server. Thus,an import of the relevant data via the recovery-tool is necessary. Inthe following step the user-IDs have to be adjusted to thewindream database.

2. The windream Server is installed on a server which is member of adomain (the server is neither a PDC nor a BDC). User and groupinformation are exclusively received from the PDC or from trusteddomains. It is not necessary to restore the local users and groupsfor using windream. Ensure that the user-IDs are adjusted.

3. In case the local system has received windream users, too, it will benecessary for a completely new installed server to restore the user-and group-structure. A following adjusting process has to be done.


4. when the windream server is installed on a PDC, the restorationprocess is equal to 1.

windream databaseSQL ServerIn case the complete SQL Server is concerned with data loss, it has tobe reinstalled. The respective installation medium should be available.

Then, the windream database and the windream database fulltext-extension have to be selected and installed with the windream Serverinstallation (user-defined).

After that, the last backup file created by the database should berestored in the corresponding directory (e.g.\MSSYL7\Backup\<Name of backup file>), or the respectivemedium should be made available, in order to restore the database withthe help of the recovery function in the Enterprise Manager of theSQL Server.

Select the entry ’windream’ in the list of the databases over theEnterprise Manager of SQL Server. In the right window of theManagement Console, among others, the group for backup isdisplayed. There, select the function for restoring the database. In thedialog box for restoring the database, the database can be restoredfrom a backup file, or from a medium. Select the respective option andconfirm with ‘OK’.

After having restored the windream database, the schedules for theregular backup of the database and transaction protocols should bechecked and adjusted.

The Enterprise Manager of SQL Server 7.0 does not offer theopportunity of saving the fulltext catalog (look at chapter ’Backup ofthe windream Database'). As the fulltext table with all entries has beenrestored with the recovery of the windream database under the entryfulltext, the fulltext catalog 'windreamft' created for the new installationmust 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 executedover the respective function and when the fulltext catalog 'windreamft'is highlined.

As the fulltext table can be very complex, the creation of the indicescan take some time.

OracleIn order to restore an Oracle Tablespace, the installed Oracle databaseand the installation of the windream database is required. Additionally,data of the last complete backup of the Tablespace and the


accompanying incremental backups of the Tablespace up to the currentdate have to be available.

Another requirement for the recovery of an Oracle database, aTablespace, or data files are the rights of the logged-in user. The usermust at least have Oracle SYSDBA rights, in order to be allowed tolaunch the recovery assistant.

The database should run in ’ARCHIVELOG’ mode, so that therecovery is valid.

For the recovery of an Oracle Tablespace, the Tablespace has to be setoffline, so that besides the Tablespace also the incremental backup datacan be restored. In status ‘OPEN’, it is only possible to restore theTablespace and the data files.

The recovery assistant of Oracle guides the user through differentopportunities of selection or adjustments that are necessary for therecovery of a Tablespace or the archive log.

After the recovery of the windream database, the schedules for thebackup strategies should be checked and modified if necessary.

Recovery of File StorageThe last backup of the file storage has to be restored. In case the lastbackup was a complete backup, no further data for the file storage haveto be restored. If incremental backups were executed after the lastcomplete backup, they have to be restored.

You have to take care that data are restored into the same directorypath on which the backup was based

The windream drive is a network drive and also behaves as a networkdrive when documents are deleted. The user has to confirm thedeletion explicitly, and the data are not saved in the local Recycle Bin.However, windream has a separate recycle bin from which deletedwindream documents can be restored or finally destroyed.

In the windream Management Console, a corresponding search fordeleted documents, e.g. according to user data, can be executed. Singleor several documents including index data can be restored over thecorresponding functions of the pop-up menu. You can find a detaileddescription of this function in chapter 8 of the windream manual(windream Administration – windream Tools – Recovery of DeletedObjects) or in the windream online help.

The recovery function is controlled over a filter in the windreamconfiguration of the Server. The file-types that are excluded fromrecovery because of exceptional features of certain Windows-applications have to be determined in the list. Documents of these


listed file-types cannot be restored over the 'Restore' function. Thecorresponding dialog is described in detail in chapter ‘windream –Configuration of Server – Filter – Recovery of deleted Documents’ inthe windream-help or in the manual in chapter 7 (SystemConfiguration – Server).

ObjectStore / Long-Term ArchiveIn order to restore data in the ObjectStore, the windream ObjectStorehas to be installed with the help of the installation medium. The servicefor the ObjectStore must not be started during the restoration of thebackup files.

After this, the files that are listed in the chapter ’Backup of thewindream ObjectStore’ have to be copied into the correspondingdirectories from the last backup medium.

Then, in order to guarantee a data consistency regarding the databasereferences, the backup of the windream database executed at the samepoint of time has to be restored.

Recovery of the Archive or Jukebox MediaDuring the recovery of the archive or the different pools, the differentstorage media, which are determined as storage places for the poolsduring the installation of the archive, have to be differentiated. If thewhole archive installation should again have to be executed, the sameconfiguration that existed before the data-crash has to be selected. Theconfiguration can be found either in the installation protocol, or it isrestored over the configuration files listed in the chapter ‘Backup of thewindream Archive’.

If a medium that has already been terminated is corrupt, it has to besubstituted by the corresponding copy. The substitution is executedover the jukebox administration tools that are described in chapter 4 ofthe archive manual. With the tool 'jukeadm' it is possible to import aCD (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 beforestarting the archive!

RegistryIn case of a backup, the restoration of the windream registry makesonly sense, if the complete installation of the windream server wasrestored. When e.g. only a system backup was restored, and thewindream server was newly installed, problems can arise when thepaths are different. Thus, all entries including paths are to be checkedbefore a backup. After a new installation it is always recommended inorder to check the differences between the backed up and the new


registry to directly backup the windream registry-branch and tocompare it with the backup (e.g. with windiff).

Appendix 21

AppendixRegistry

The windream Registry includes, as mentioned in the 'Registry' chapter,different static and dynamic entries. In the following, a list of thosekeys can be found that might change due to e.g. changes in thewindream configuration while windream is operating. Those keysshould be saved on a regular basis in order to restore them properly. (arespective script that saves those keys in a *.reg-file can be provided ondemand).

The following listing shows the complete windream registry of aGerman testsystem, including all keys and the respective values:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0]

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Database]"Servername"="testora2""Provider"="ORAOLEDB.oracle""Name"="windream""PWFile"="C:\\PROGRA~1\\AIS~1.GMB\\windream\\Windream.pwf""MaxPooledSessions"=dword:0000000a"MaxPooledArchives"=dword:00000004"MaxCachedBinaries"=dword:000003e8"FulltextEnabled"="*.DOC�*.TXT�*.XLS�*.HTM�*.HTML�*.PDF�*.PPT""CacheRootFolders"=dword:00000001"CacheDeleteDelay"=dword:0000000a"Temp"="C:\\Programme\\A.I.S.GmbH\\windream\\Temp""FilestoreDefaultDir"="e:\\datenntdt""DBIDDefault"="42""OraTablespaceUsers"="USERS""OraTablespaceTemp"="TEMP""OraTablespaceIndex"="USERS"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\DBG]"Out"="yes""Level"=dword:00000000"ThrowCOMEvent"=dword:00000003

22 Appendix

"MaxErrorStackSize"=dword:00000064"StackToClient"=dword:00000001"FulltextTraceopts"="+fatal +error +warning""TcpServiceTraceopts"="+fatal +error +warning""ExcludeModules"="""CurrentModulesSection"="Modules"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\FSD]"NoRecoverableTemplates"="*.�~*.*�*.TMP�*._Q_�DESKTOP.INI�*.LCK�*.BAK�*.??$�*.LDB�*.LNK�*.WBK�THUMBS.DB�*.FM.*""ExcludeProcessList"="explorer�winfile"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Fulltext]"Reconnect"=dword:00000078"Newscan"=dword:0000012c"MaxSize"=dword:00000fa0

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\License]"Name"="Company"="Department"="Key"=

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.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"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Reporting]

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Reporting\ArchiveAndDelete]"WriteLog"=dword:00000001"AppendLog"=dword:00000001"DialogShow"=dword:00000000"DialogAutoClose"=dword:00000000"NLSFileName"="WMArcMv""NLSSection"="ArchiveAndDelete"

Appendix 23

"LogFileName"="C:\\Programme\\A.I.S.GmbH\\windream\\Reporting\\ArchiveAndDelete.log"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Reporting\Export]"WriteLog"=dword:00000001"AppendLog"=dword:00000001"DialogShow"=dword:00000001"DialogAutoClose"=dword:00000000"NLSFileName"="WMODaEx""NLSSection"="Export""LogFileName"="C:\\Programme\\A.I.S.GmbH\\windream\\Reporting\\Export.log"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Reporting\Import]"WriteLog"=dword:00000001"AppendLog"=dword:00000001"DialogShow"=dword:00000001"DialogAutoClose"=dword:00000000"NLSFileName"="WMODaEx""NLSSection"="Import""LogFileName"="C:\\Programme\\A.I.S.GmbH\\windream\\Reporting\\Import.log""WindowPositionX"=dword:00000140"WindowPositionY"=dword:0000012f"Mode"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Reporting\UndoCheckOut]"WriteLog"=dword:00000001"AppendLog"=dword:00000001"DialogShow"=dword:00000001"DialogAutoClose"=dword:00000000"NLSFileName"="WMODaEx""NLSSection"="UndoCheckOut""LogFileName"="C:\\Programme\\A.I.S.GmbH\\windream\\Reporting\\UndoCheckOut.log"

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Reporting\UserGroup]"WriteLog"=dword:00000001"AppendLog"=dword:00000001"DialogShow"=dword:00000001"DialogAutoClose"=dword:00000000"NLSFileName"="WMOMMC""NLSSection"="UserGroup""LogFileName"="C:\\Programme\\A.I.S.GmbH\\windream\\Reporting\\UserGroup.log"

24 Appendix

"WindowPositionX"=dword:0000013a"WindowPositionY"=dword:00000122"Mode"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\A.I.S.GmbH\windream\3.0\Shell]"CCFlags"=dword:00000100"DelayVfsConnect"=dword:00001b58"CCLastService"="windream DMS-Service"