How to batch backup a file system path to a repository

Ops Center Protector User Guide

Version

7.7.x

Audience

anonymous

Part Number

MK-99PRT002-08

ft:lastEdition

2023-10-26

It is assumed that the following tasks have been performed:

The Protector Master software has been installed and licensed on a dedicated node. See Installation Tasks and License Tasks.
The Protector Client software has been installed on the source node where the file system path resides.
The Protector Client software has been installed on the destination node where the Repository will reside.
Permissions have been granted to enable the Protector UI, required activities and participating nodes to be accessed. In this example all nodes will be left in the default resource group, so there is no need to allocate nodes to user defined resource groups. Refer to How to configure basic role based access control.

This task describes the steps to follow when protecting data that resides on a file system, to a repository, using batch mode backup. The data flow and policy are as follows:

Figure. Batch Data Flow

Table. Path Backup Policy
Classification Type	Parameters	Value
Path	Include	C:\testdata

Operation Type	Parameters	Value	Assigned Nodes
Backup	RPO	10 mins	Repository
	Retention	1 hour
	Run Options	Run on RPO

Locate the source node in the Nodes Inventory and check that it is authorized and online. This node is where the production data to be backed up resides.
For a file system backup using a Path classification, a basic OS Host node is required. It is not necessary to create the source node in this case since all Protector client nodes default to this type when installed. See How to authorize a node.
Locate the destination node in the Nodes Inventory and check that it is authorized and online.
This node is where the repository will be hosted and is identified as the Proxy Node when creating the repository in the next step.
Create a new Repository node using the Repository Storage Node Wizard and check that it is authorized and online.
The Repository node type is grouped under Storage in the Node Type Wizard. You can direct data from multiple nodes to a single repository so there is no need to create a new repository if a suitable one already exists. See How to add a node, and How to authorize a node.
Define a policy as shown in the table above using the Policy Wizard, Path Classification Wizard and Backup Operation Wizard.
The Path classification is grouped under Physical in the Policy Wizard. See How to create a policy.
Draw a data flow as shown in the figure above, that shows the OS Host source node connected to the Repository destination node via a Batch mover, using the Data Flow Wizard.
See How to create a data flow.
Assign the Path-Backup policy to the OS Host source node and the Backup operation to the Repository destination node on the data flow.
Select the Standard Store Template when assigning the operation to the repository. See How to apply a policy to nodes on a data flow.
Compile and activate the data flow, checking carefully that there are no errors or warnings.
See How to activate a data flow.
Locate the active data flow in the Monitor Inventory and open its Monitor Details.
The policy will be invoked automatically to create an initial backup and then repeatedly according to the RPO specified in the policy. The policy can also be manually triggered from the source node in the monitor data flow. See How to trigger an operation from an active data flow.
Watch the active data flow via the Monitor Details to ensure the policy is operating as expected.
For a healthy data flow you may periodically see:
- An animated resynchronization icon appear above the batch mover each time the RPO is reached.
- Transient Node Status icons appear over nodes and associated information messages displayed to the right of the data flow area.
- Backup jobs appearing in the Jobs area below the data flow that cycle through stages and ending in Progress - Completed.
- Information messages appearing in the Logs area below the data flow indicating rules activation, replication and resynchronization events.
For a problematic data flow you may see:
- Permanent Node Status icons appear over nodes and associated warning messages displayed to the right of the data flow area.
- Backup jobs appearing in the Jobs area below the data flow that cycle through stages and terminating in Progress - Failed.
- Warning and error messages appearing in the Logs area below the data flow indicating failed events.
Review the status of the Repository via the relevant Generation 1 Repository Details and the stores via the relevant Gen1 Repository Store Details, to ensure backup snapshots are being created.
Repositories require ongoing surveillance to ensure that they are operating correctly and sufficient resources are available to store your data securely. See How to view the status of a repository.

New snapshots will appear in the Gen1 Repository Store Details periodically as dictated by the RPO of the policy. Old snapshots will be removed periodically as dictated by the Retention Period of the policy. The retention period of individual snapshots can be modified here if required.