Configuring and using an MSDP build-your-own (BYO) server for universal shares
Table: Process for configuring and using universal shares with an MSDP build-your-own (BYO) server describes a high-level process for setting up an MSDP build-your-own (BYO) server for Universal Shares. (On an appliance, the universal share feature is ready to use as soon as storage is configured.) See the linked topics for more detailed information.
Table: Process for configuring and using universal shares with an MSDP build-your-own (BYO) server
Step | Description |
|---|
1 | Identify a machine. Make sure that the MSDP BYO server complies with prerequisites and hardware requirements.
See MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure universal shares..
|
2 | In the NetBackup web UI, create a universal share.
See Create a universal share in the NetBackup Web UI Administrator's Guide. |
3 | Mount the universal share that was created from the NetBackup web UI.
See Mounting a universal share created from the NetBackup web UI. |
4 | Configure a universal share backup policy. |
5 | Optionally, use the ingest mode to dump data or to load backup data from a workload to the universal share over NFS/CIFS. When ingest mode is turned on, the backup script triggers the universal share to persist all the data from memory to disk on the client side at the end of the backup or the dump. Ingest mode is faster than normal mode as it does not guarantee all the ingest data is persisted to disk until the ingest mode is turn off. See Using the ingest mode. |
6 | Restore from a universal share backup. Besides offering a fast data protection process, the Protection Point offers two powerful restore methods: Client-based restore: Data protected using a Protection Point (see step 4 in this table) is restored using the exact same method as restoring data from a standard client backup: Restore to the original universal share. In this case, the original universal share must be present. Specify the universal share path as the restore destination and the media server where universal share resides as the client. However, for large data restores, consider restoring to an alternate location. Restore to an alternate location. A standard NetBackup client must be installed on any system where the restore is directed.
Provisioned restore (Instant Access): A Protection Point is a point-in-time (PIT) copy of the data as it existed on the Universal Share when any Protection Point was initiated. This PIT copy of the data can be exported as a separate network share of the Protection Point data. This PIT copy of the Projection Point is called a provisioned copy of the data. The data in this provisioned share is not necessarily connected to any data in the primary universal share. It can be used as an autonomous version of the PIT Protection Point data. Any changes to this provisioned copy of the data have no effect on data in the original universal share. It also does not have any effect on the source PIT copy of the data. The PIT copy can be mounted on the originating system where the universal share was previously mounted. It can also be provisioned on any other system that supports the mounting of a network share. In this sense, the NetBackup Protection Point provides a method of copy data management that offers you another powerful way of using the data that is managed with NetBackup. The process of provisioning a Protection Point is performed using a NetBackup API. This API and all NetBackup APIs are described in the NetBackup API Reference documentation, which is located on the NetBackup primary server (https://<primary_server>/api-docs/index.html). It can also be found online.
|
