RDF/IMP and IMPX System Management Manual (RDF 1.3+)

Introducing RDF
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
1-27
Configuring an SMF Environment on the Primary
System
Note that you still cannot map image trail volumes to logical volumes; image trail
volumes must always map to physical volumes.
When using SMF volume mapping with RDF, RDF/MP, and RDF/MPX, the backup
operating system environment must be D46 or higher or G06 or higher; when using it
with RDF/IMP and RDF/IMPX, the backup operating system environment must be D46
or higher or G06.03 or higher.
Configuring an SMF Environment on the Primary System
When configuring an SMF environment on an RDF primary system, make sure that
SMF catalog files are not replicated by RDF to the backup system. There are three ways
to do so:
•
Place the SMF catalog on a primary system volume that is not protected by RDF.
The extractor ignores any audit generated by disks outside the RDF configuration,
and hence will not replicate any changes to the SMF catalog on the primary system.
With this option, you can store the catalog in either the default SMF catalog
subvolume or your own subvolume.
•
Place the SMF catalog in the default SMF catalog subvolume on a volume that is
protected by RDF. The extractor automatically filters out changes to the SMF
catalog if the catalog is in the default SMF catalog subvolume.
If you store the catalog in your own subvolume, the extractor will try to replicate
changes to the catalog, which could have an adverse affect on RDF and any SMF
catalogs with the same subvolume name on the backup system.
•
Place the SMF catalog in a subvolume that is explicitly excluded from RDF
protection (the EXCLUDE clause is described in Section 11, Subvolume- and File-
Level Replication).
Configuring an SMF Environment on the Backup RDF System
All RDF products support replication to SMF logical volumes on the backup system,
with the following restrictions:
1. When replicating to an SMF logical volume, the logical volume must belong to an
SMF pool that contains only one physical volume.
2. Image trail volumes cannot reside on SMF logical volumes.
3. An SMF logical volume cannot be used as the RDF BACKUPSWAP volume.
There are no restrictions on the placement of SMF catalog files on the backup system. If
the backup system could ever become a primary (such as after an RDF takeover, for
example, or as the result of a planned switchover), then the restrictions described in the
preceding topic for primary systems also apply.