Backup and Restore 2 Manual
BRCOM RESTORE Command
Backup and Restore 2 Manual—522696-019
7-60
SQL/MX Restore Examples
To restore hard link, you must restore the complete set of hard-linked files. For
example:
BR> RESTORE =mytape, OSS (/usr/project/file1,
BR+> /usr/project/file2,/usr/project/file3);
If you have backed up and restored all the hard links, the links all point to a single
inode. If you backed up an incomplete set of hard links, the hard links are severed
after you restore the files. If you backed up only file1 and file2, file3
remains pointing to the original inode and its contents. Files file1 and file2
point to another inode and its contents. Therefore, the hard links are effectively
severed from file3 to file1 and file2.
Do not restore an incomplete set of hard-linked files. For example:
BR> RESTORE =mytape, OSS (/usr/project/file1,
BR+> /usr/project/file2);
You have not restored /usr/project/file3. Because you did not restore the
complete set, this command might result in these objects not getting restored.
Instead error messages are generated indicating that the link could not be created.
Restoring OSS Objects Containing ACLs
To restore ACLs contained in OSS objects specify the OSSACL job option. For
example:
BR> RESTORE $m1,OSS (/acls/file1,tgt /acls/tmp1),ossacl
on,listall on,tapedisposition bot;
SQL/MX Restore Examples
When you specify an SQL/MX object, that object and all its subordinate objects are
restored with these exceptions:
Any catalogs and schemas that already exist on disk are left unchanged.
Any tables that exist both on tape and on disk are dropped and then restored from
tape unless the table contains constraints, views, triggers, or stored procedures.
For information about dropping objects and procedures to check if a table has
constraints, views, triggers, or stored procedures, see the MXCI command
SHOWDDL in the SQL/MX Installation and Management Guide.
The SQL/MX examples are for:
Restoring with KEEPGFN Job Option on page 7-62
Restoring All SQL/MX Catalogs on page 7-65
Restoring an SQL/MX Catalog on page 7-65
Restoring a Delimited SQL/MX Catalog on page 7-66
Restoring an SQL/MX Schema on page 7-66