HP Reference Information Storage System Version 1.6 Administration Guide revision 2 (T3559-90809, September 2007)
8 D ata m an agem ent
This chapter discusses the following topics:
•
Replication, page 61
•
Smartcell Cloning, page 64
•
Reprocessing , page 66
•
Repository level retention, page 68
•
Database and data backup, page 70
Replicatio
n
NOTE:
This view is available only if a replicated system is configured.
Use the Replication view to monitor and to start or stop replication for a domain on a remote system.
Replication status is updated after each polling cycle. Therefore, it could be up to five minutes after you
start replication before you see results on the graph of replication rates. Errors and warnings, however,
are displayed as soon as they happen on the system. (The Replication view is unavailable until at least
one domain on the PCC host system is configured for replication.)
A failed replicated smart cell triggers allocation of new primary and secondar y smart cells on the replica
site. When the original site returns to service , it automatically becomes the replica site for ne w primary
and secondary smar t cells. Depending on configuration, some administration might be necessary for
continued d ata storage. Specifically, if the system uses Selective Archiving, the replica site mining servers
must be configured a nd enabled to start m ining to the replica site.
If the primary site is not available for queries, users must enter the address of the replica site, instead
of the primary site, in their browsers.
NOTE:
In order for the Replication view to display statistics from the remote system, a RISS remote authorization
user must be set up in Account Manager. See RISS Remote Authorization in "User account
information"onpage53.
Tabl e 33 Link to Replication view
Origin
Link
left menu
Data Management > Replication
Database Replication
IMPORTANT:
When installing a replica RISS, finish db2 replication before starting JBoss on all other servers, otherwise
some RISS applications will not be able to access db2 b e cause db2 tables are locked by the db2
replication process.
Administrator Guide
61