Restoring a Docbase/Repository from the Database and File Store Backups:

1) Create a fresh docbase using Server Configuration Utility. Ensure that you create the fresh
docbase with same repository name, repository ID, database name, repository owner name
and password as in the production repository.
All the above details can be obtained from the server.ini file of the production repository.
Eg: Repository name = prod_docbase
Repository ID = 39351
Repository owner name = dmadmin
Password = PASSWORD
Obtain the docbase owner and password from the Content Server Administrator of the
production repository.
2) As a consequence of the above step, we will have a file store created on the Content Server
host (\data\ prod_docbase) and table space (prod_docbase) created on the database server
(MSSQL 2000).
3) Connect to the Enterprise Manager on the SQL server machine and open the Databases folder.
4) Right Click the database (prod_docbase) corresponding to the repository created in the step 1.
Choose the option All Tasks and then click Restore Database.
5) A Restoration menu will pop up. Choose the appropriate .BAK file (prod_docbase_db) to be
restored. Choose Force Restoration while restoring the database. Also choose appropriate path
for .mdf and .ldf file, which are created during restoration. Generally these files are created under
the folder Drive: \Program Files\My SQL server\MSSQL\Data or LOG.
6) Once the restoration is complete, you will find that the original tablespace (created in Step 2)
has been replaced by the tablespace corresponding to Backup database (prod_docbase_db).
7) Open Query Analyzer with the user account of sa and connect to the docbase
(prod_docbase) created in above steps. Change the docbase owner to dmadmin by executing the
following query:
EXEC sp_changedbowner dmadmin
Disconnect with prod_docbase.

8. Reconnect to prod_Docbase in Query Analyzer with the user account of docbase owner
dmadmin( i.e user id : dmadmin and pwd : PASSWORD) and execute the following sql
scripts:

Update dm_mount_point_s set host_name = newhost \\ here newhost =

hddlgsdhil0405 <<machine name of new host>>

Update dm_server_config_s set r_host_name = newhost

Update dm_server_config_r
set projection_targets = newhost where projection_targets = oldhost \\

Update dm_type_s set views_valid = 0

Update dm_job_s set target_server =

docbasename.docbasename@newhost where target_server =
docbasename.docbasename@oldhost \\ docbase name= prod_docbase

9) Ensure that the preserve_existing_types key in the SERVER_STARTUP section in server.ini is

set to TRUE:
preserve_existing_types=T
10) If the server and content files of the copy reside on a drive different from the
drive used by the production repository (for example, drive D: instead of drive
E :), update the tables dm_location and dm_server_config_s through sql scripts or manually
changing the entries in the tables on the SQL server.
Alternately, use IDQL to update the file_system_path attribute of the dm_location and
dm_mount_point objects to the new location:
Update dm_location objects
Set file_system_path=newpath where file_system_path=old path
Update dm_mount_point objects
Set file_system_path=newpath where file_system_path=old path
11) Using IDQL execute the following scripts:
Update dm_user objects

set user_os_domain =new_machine_name

where user_os_domain =old_machine_name
12) Update the install_owner, smtp_server and r_install_domain as per local environment.
13) Replace the aek.key and dbpassword.txt files in your local environment by the
corresponding aek.key and dbpassword.txt from production environment (of the same docbase
you are restoring)
Locations for these files are:
\DM_HOME\dba\config\docbase_name\dbpassword.txt
\ DM_HOME\dba\secure\aek.key
14) Copy the content files under \data\prod_docbase.
15) Restart the Content Server and SQL SERVER machines.
16) Start the Docbroker and BFW_docbase service.
17) DTS configuration required after that.
18) Index Server configuration from DA-Tools, need to change all required ports.
19) Then need to setup LDAP objects
20) If repository is connected with external XRD then need to create database link, then create
synonyms of all required tables and then register it.
21) If there were any TBO running on your source repository than all needs to be placed under
/dba/java_methods of new repository.