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. Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide
  3. Restoring clients
  4. About external procedures
  5. External procedure points and names
Veritas NetBackup™ Bare Metal Restore™ Administrator's Guide

External procedure points and names

BMR can run external procedures at the following user exit points during the restore process, in the following sequence:

prediscover

Before discovery of hardware is reported to the BMR server (UNIX clients only).

preformat

Before disks are formatted and partitioned. On Windows systems, the preformat takes place after the system drive is formatted but before any nonsystem drives are formatted.

prerestore

Before files begin to restore.

postrestore

After files are restored.

first boot

After the restore is complete and at the first boot of a restored client. On Windows systems, the first boot external procedure operates as the first user to log on after a client is restored.

An external procedure point name is used as part of the name of each external procedure script that you create. The naming convention for client-specific external procedures is different than for operating system-specific external procedures.

Note:

Do not add a .cmd extension for the external procedures that are intended for Microsoft Windows systems. BMR adds the appropriate file name extension when it generates the scripts during the prepare-to-restore process.

Client-specific external procedure names

Client-specific external procedure names are in the following format:

clientname_externalprocedure

For example, the sol123_prerestore external procedure is started before files are restored on client sol123. (The procedure starts if Run External Procedures is specified during restoration.)

Operating system-specific external procedures names

Operating system-specific external procedure names are in the following format:

externalprocedure.ostype

The ostype is one of the following:

  • aix

    AIX

  • hp

    HP-UX systems

  • linux

    Linux systems

  • sol

    Solaris systems

  • win

    Windows systems

For example, the preformat.linux external procedure is started on Linux clients before drives are formatted. (The procedure starts if Run External Procedures is specified during restoration.)

Feedback

Was this page helpful?
Previous

About external procedures

Next

About managing external procedures

Feedback

Was this page helpful?