Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for Oracle Administrator's Guide
  3. Appendix D. XML Archiver
  4. Performing an XML export archive
  5. Writing to a directory versus writing to a storage unit
NetBackup™ for Oracle Administrator's Guide

Writing to a directory versus writing to a storage unit

One important aspect of the parameter file is the DIRECTORY parameter. If you specify the DIRECTORY parameter, the bporaexp (bporaexp64 on some platforms) command writes the backup files to the operating system directory you specify. NetBackup does not write the files to a storage unit.

For example, assume that the archive test1 contains one table, USER1. If the directory parameter is specified, NetBackup creates certain files when you run the bporaexp command.

Windows:

DIRECTORY=\db\netbackup\xml

UNIX:

DIRECTORY=/db/netbackup/xml

Table: NetBackup files for example table USER1 shows the files NetBackup creates when you run the command.

Table: NetBackup files for example table USER1

File

Content

Windows: \db\netbackup\xml\test1\test1.xsd

UNIX: /db/netbackup/xml/test1/test1.xsd

Master XML schema for table USER1

Windows: \db\netbackup\xml\test1\USER1\TEST1.xsd

UNIX: /db/netbackup/xml/test1/USER1/TEST1.xsd

Table schema for table USER1

Windows: \db\netbackup\xml\test1\USER1\TEST1.xml

UNIX: /db/netbackup/xml/test1/USER1/TEST1.xml

XML document for table USER1

If the DIRECTORY parameter is not specified, NetBackup writes the backup images to a storage unit. A NetBackup backup set is created and cataloged under the name:

Windows:

\Oracle\XMLArchive

UNIX:

/Oracle/XMLArchive

All NetBackup for Oracle bporaexp backups are cataloged using this convention.

Alternatively, if the parameter file does not contain the DIRECTORY parameter, NetBackup creates and catalogs the following files:

Windows:

\Oracle\XMLArchive\test1\test1.xsd
\Oracle\XMLArchive\test1\USER1\TEST1.xsd
\Oracle\XMLArchive\test1\USER1\TEST1.xml

UNIX:

/Oracle/XMLArchive/test1/test1.xsd
/Oracle/XMLArchive/test1/USER1/TEST1.xsd
/Oracle/XMLArchive/test1/USER1/TEST1.xml

In production, do not use the DIRECTORY parameter in the bporaexp parameter file. When you write to a storage unit, NetBackup offers the features that include searching and cataloging with the NetBackup catalog and automatic handling of output that exceeds file system limits. With the DIRECTORY parameter, file system limits, such as a 2 GB maximum, can cause an error.

To run bporaexp on the client, run the following command:

bporaexp [username/password] parfile = filename | help=y

On some UNIX platforms, the bporexp64 command is used.

Feedback

Was this page helpful?
Previous

Running bporaexp on the client as an Oracle user

Next

About bporaexp parameters

Feedback

Was this page helpful?