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™ for SAP Administrator's Guide
  3. Appendix H. Configuring split mirror backups
  4. Local-host snapshot method: nbu_snap (Solaris SPARC platform only)
Veritas NetBackup™ for SAP Administrator's Guide

Local-host snapshot method: nbu_snap (Solaris SPARC platform only)

The nbu_snap snapshot method is for Solaris (SPARC) clients only. It makes copy-on-write snapshots for any SAP Oracle databases that reside in UFS or Veritas File Systems (VxFS).

For the nbu_snap methods, you must identify a cache device for the copy-on-write process. The cache device is a raw disk partition, either a logical volume or physical disk. It stores the portions of the client's data that the incoming write requests change while the copy-on-write is in progress.

For the cache device, do not select an active partition that contains valuable data. Any data in that partition is lost when the snapshot is complete. Specify the raw partition as the full path name of either the character special device file or the block device file.

For example, specify the following:

  • Solaris (SPARC) raw partition: /dev/rdsk/c2t0d3s3 or /dev/dsk/c2t0d3s3

  • VxVM volume: /dev/vx/rdsk/diskgroup_1/volume_3 or /dev/vx/dsk/diskgroup_1/volume_3

    Do not specify wildcards (such as /dev/rdsk/c2*) as paths.

The cache partition must be unmounted and must reside on the same host as the snapshot source (the client's data to back up). The partition must have enough space to hold all the writes to the partition that can occur during the backup. Note that backups during off-peak periods normally require a smaller cache than a backup during peak activity.

For more information, see the NetBackup Snapshot Client Administrator's Guide.

Configuring NetBackup for SAP with the local-host snapshot method (nbu_snap)

  1. On the production database host, install NetBackup Client, which includes the NetBackup Snapshot Client, and NetBackup for SAP.
  2. Identify a cache device for the copy-on-write process. Manually select the snapshot method on the Advanced Snapshot Options dialog box.
  3. Specify the raw cache partition using one of the following methods:
    • Specify the raw partition in the default cache device path for snapshots field. (Open NetBackup Management > Host Properties > Clients. Then in the Client Properties dialog box, expand UNIX Client > Client Settings). This setting applies to the client in all policies.

    • In the Advanced Snapshot Options dialog box, specify the cache device path value field. This cache setting applies to all clients in the current policy and overrides the cache setting in the client settings dialog box.

Feedback

Was this page helpful?
Previous

About configuring split mirror backups

Next

Local-host snapshot method: VxVM (Solaris SPARC, HP-UX, Windows)

Feedback

Was this page helpful?