VMware application-aware
|
Full
|
All the data is backed up.
|
Full
|
Monthly
|
Synthetic Full
|
Only the data that has changed since the last synthetic-full or full backup is backup up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage.
|
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
|
12 hours
|
Log
|
The transaction logs are backed up.
|
|
30 minutes
|
VMware crash-consistent
|
Full
|
All the data is backed up.
|
Full
|
Monthly
|
Synthetic Full
|
Only the data that has changed since the last synthetic-full or full backup is backed up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage.
|
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
|
12 hours
|
Kubernetes crash-consistent
|
Full
|
The namespace metadata and persistent volumes are backed up.
|
Full
|
Daily
|
Synthetic Full
|
Only the data that has changed for persistent volumes on VMware first-class disks since the last synthetic-full or full backup is backed up. The namespace metadata and all other persistent volumes are backed up in full. Although not all the data is copied over the network, the result is still a full backup in storage.
|
A combination of full and differential backups are performed, followed by a merge operation that produces a full backup in storage.
|
12 Hours
|
File System centralized
|
Full
|
All the data is backed up.
|
Full
|
Monthly
|
Synthetic Full
|
Only the data that has changed since the last synthetic-full or full backup is backed up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage.
|
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
|
12 hours
|
Microsoft Exchange Server centralized
|
Full
|
All the data is backed up.
|
Full
|
Weekly
|
Synthetic Full
|
Only the data that has changed since the last synthetic-full or full backup is backed up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage.
|
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
|
12 hours
|
Microsoft SQL Server centralized
|
Full
|
All the data is backed up.
|
Full
|
Daily
|
Differential
|
Only the data that has changed since the last differential backup or the last full backup if there are no other differential backups is backed up.
|
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
|
12 hours
|
Log
|
The transaction logs are backed up.
|
|
30 minutes
|
Network Attached Storage
|
Full
|
All the data is backed up.
|
Full
|
Daily
NOTE:It is recommended to perform a full backup after updating to
PowerProtect Data Manager 19.12.
|
Synthetic Full
|
Only the data that has changed since the last synthetic-full or full backup is backup up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed files are copied over the network, but the result is still a full backup in storage.
|
An incremental backup is performed, followed by a merge operation that produces a full backup in storage.
|
Daily
|
Oracle centralized (Application Direct)
|
Full
|
All the data is backed up.
|
Full
|
Daily
|
Incremental Cumulative
|
Only the data that has changed since the last level 0 full backup is backed up.
|
Differential
|
12 hours
|
Incremental Differential
|
Only the data that has changed since the last incremental differential backup or the last full backup if there are no other incremental differential backups is backed up.
|
Incremental
|
6 hours
|
Log
|
The archived logs are backed up.
|
-
|
30 minutes
|
Oracle centralized (Oracle Incremental Merge)
|
Full
|
All the data is backed up.
|
Full
|
Daily
|
Synthetic Full
|
Only the data that has changed since the last synthetic-full or full backup is backup up. An operation to merge these changes with the last synthetic-full or full backup produces a full backup in storage. Only the changed files are copied over the network, but the result is still a full backup in storage.
|
A differential backup is performed, followed by a merge operation that produces a full backup in storage.
|
12 hours
|
Log
|
The archived logs are backed up.
|
-
|
30 minutes
|
Block Volume
|
Synthetic Full
|
Backs up only the blocks that have changed since the last synthetic-full or full backup, and then performs an operation to merge those changes with the last synthetic-full or full backup in order to produce a full backup in storage. Only the changed blocks are copied over the network, but the result is still a full backup in storage.
|
An incremental backup is performed, followed by a merge operation that produces a full backup in storage.
|
6 hours
|
Snapshot
|
Saves the state of the volume or volume group and all files and data within it at a particular point in time. Snapshots provide a method of recovery for data that has been corrupted or accidentally deleted. You can use snapshots to restore the volume or volume group to a previous state.
|
|
15 minutes
|