Search <book_title>...

Veritas NetBackup™ Flex Scale Administrator's Guide

Last Published: 2021-07-11

Product(s): Appliances (1.3)

Platform: NetBackup Flex Scale OS

NetBackup master service catalog protection using checkpoints

In NetBackup Flex Scale, you can protect your master service from software failures or from being corrupted using checkpoints. The checkpoints are created for the master service catalog file system every 2 hours according to a schedule. The maximum number of checkpoints is 36. Once the total number of checkpoints exceed 36, the oldest checkpoint is deleted and a new checkpoint is created. A new file system with the name SCRATCH_<XXXXX> is created which acts as a scratch space for the recovery process. This file system is used for syncing and validating data from the checkpoint. The scratch file system is created during initial configuration. The scratch file system is erasure-coded with logging having the same layout (8:4) as the other data file systems. The file system is extended when the NetBackup master service storage grows (during the addition of the sixth node).

All the checkpoints consume storage from the same volume set. As the checkpoints are copy-on-write, only modified data gets pushed to the checkpoints. But depending on data change rate, the checkpoints can consume considerable storage. If the primary fileset cannot allocate storage during the write or file creation operation, instead of returning an ENOSPC error to the user, the oldest checkpoint is automatically deleted to make space.

You can use REST APIs for the recovery of master service catalog file system from the checkpoints. The REST API calls should be made in the following order:

Get the list of checkpoints for the master service catalog file system. This API returns a list of all the available checkpoints for the master catalog file system. The checkpoints can be used to recover the data.

GET /api/appliance/v1.0/netbackup/checkpoints
URI : /api/appliance/v1.0/netbackup/checkpoints
Type : GET
Response Body:
      {
  	"links": {
    	  "self": {
      	    "href": "/api/appliance/v1.0/netbackup/checkpoints"
          }
        },
  	"data": [
    	  {
      	    "type": "netbackup",
      	    "id": "1",
            "links": {
              "self": {
                "href": "/api/appliance/v1.0/netbackup/checkpoints/
																	checkpoint1"
              }
            }
          }
        ]
      }

The checkpoint name which is returned by this API should be passed as input to the API which is called to restore the catalog.

Recover and validate the data from the checkpoint. This API recovers the data from the checkpoint to the scratch space file system and then runs the NetBackup database validation on the recovered data.
```
POST /api/appliance/v1.0/netbackup/checkpoints/restore-catalog/
{checkpointName}
URI: /api/appliance/v1.0/netbackup/checkpoints/restore-catalog/{
checkpointName}
Type : POST
Input Parameter for Request : Checkpoint name
Response: 
	{
  	    "taskId": "string",
  	    "message": "string"
	}
```
This is an asynchronous API and it returns a task ID when API execution is successful. You can find the execution status and details by providing this taskID as input in the GET {taskId} API. The task is also visible in GUI.
Restore the data to the master service catalog file system. This API restores the data from the scratch space file system to the master service catalog file system.
```
POST /api/appliance/v1.0/netbackup/checkpoints/sync-catalog
URI : /api/appliance/v1.0/netbackup/checkpoints/sync-catalog
Type : POST
Input Parameters : None
Response :
	{
  	    "taskId": "string",
  	    "message": "string"
	}
```
This is an asynchronous API and it returns a task ID when API execution is successful. You can find the execution status and details by providing this taskID as input in the GET {taskId} API. The task is also visible in GUI.

Note:

When the master service catalog file system is recovered using an old checkpoint, the master service goes back to the point in time of the checkpoint. The images created after that point in time will remain in the system and cannot be accessed unless they are reimported.

For more details on import, see the Importing backup images, Phase I and Importing backup images, Phase II sections in the NetBackup Administrator's Guide, Volume I.