PowerProtect Data Manager 19.17 Kubernetes User Guide

Roadmap for planning a protection policy

Before you create a protection policy, assemble the following information:

Identify a supported purpose for this protection policy that corresponds to your goal.
For example, performing centralized protection or application-aware backups.
Identify what supported objectives this protection policy should accomplish. Supported protection policy objectives provides more information.
For example, primary backup and replication to a remote server.
Use the following tables to list all required primary backup or retention types and their associated retention periods. Include any additional full backups for extended retention.
For centralized, crash consistent, or application-aware protection, list the backup frequency and start and end times for each primary backup type.
Identify a protection storage system and storage unit where PowerProtect Data Manager should store the primary backup or retention.
For this target, identify any required virtual networks or interfaces, and whether retention locking is required.
If replication is required, identify the remote protection storage system and storage unit.

Table 1. Required backup and retention typesRequired backup and retention types
Primary backup or retention types	Retention period (with units)	Retention period units
Example (full)	1 week	weeks
Full
Synthetic full
Other:
Other:
Other:

Table 2. Centralized protection schedulesCentralized protection schedules
Primary backup types	Creation frequency (with units)	Start and end
Example (full)	1 week	08:00 PM to 08:00 AM
Full
Synthetic full
Other:
Other:
Other:

Table 3. Additional full backups for extended retentionAdditional full backups for extended retention
Primary backup or retention types	Created every (week/month/year)	On the (day of week/month/year)	Retention period
Retained full backup 1 (example)	Week	Saturday	52 weeks
Retained full backup 2
Retained full backup 3