Disabling Deduplication On Specific Backup Policies; Separate Database Full Backups From Incremental Backups - HP 12000 Design Manual

Disabled in the VLS GUI. Otherwise, the last backup of that client will remain in the "Waiting
for next backup" state.
If you have a clustered system that is being backed up, in some cases this may mean the client
name changes when a node fails because the cluster fails over to another node and the backup
application uses that node name (rather than the virtual cluster name).

Disabling Deduplication on Specific Backup Policies

To improve deduplication performance, you can disable deduplication in Command View VLS for
specific backup policies where the backup data has a very high change rate and therefore does
not deduplicate effectively. Examples of such backup policies:
Pre-compressed or pre-encrypted backups
Database redo/archive log file backups (see
Backups)
Database block-level incremental/differential backups (see
from Incremental
NOTE: Never use an external hardware compression or encryption solution in front of the VLS
because this will disable all deduplication and compression inside the VLS. (If all backup data is
pre-compressed or pre-encrypted, it will always be 100% unique data.)

Separate Database Full Backups from Incremental Backups

Because database block-level incremental backups and database logs are always new, unique
data blocks (they are already deduplicated), these incrementals should not be mixed with database
full backups. HP recommends configuring database log file and incremental backups to use a
separate media pool from the full backups to improve deduplication efficiency.
Backups)
Separate Database Full Backups from Incremental
Separate Database Full Backups
Design Considerations 97