Forum Discussion

Local_IT's avatar
Local_IT
Level 3
4 years ago
Solved

Same kilobyte and backup time when backup "Full Backup" or "Diff Incr Backup"

Hello,

Veritas Netbackup : V.8.2
Policy Type : VMware
Vcenter : 6.7 U3
VM saved : W2012 ; W2016 ; W2019
All options check : "file recovery" ; "exclude deleted blocks, swap,.." ; "block-level..." ; "Use accelerator".
Schedule : Full_Monthly ; Full_Weekly ; Incr_Daily.
Duplication : yes.


Would you know, please, why when I check report in "Reports > Client Backups", I've almost the same value for "kylobytes" and for "Elapsed Time" whether it is a "Full Backup" or a "Differential Incremental Backup" ?

 

ClientBackup Date/TimePolicyNb of FilesKilobytesGBTBSchedule NameSchedule TypeElapsed Time
VM_Name6 déc. 2021 20:00:41Policy_name1801212570650202.720.2Incr_DailyDifferential Incremental Backup00:38:49
VM_Name4 déc. 2021 17:31:11Policy_name283127212808228202.950.2Full_MonthlyFull Backup00:17:46
VM_Name3 déc. 2021 20:00:38Policy_name1170212458349202.620.2Incr_DailyDifferential Incremental Backup00:18:16

Thanks

  • quebek's avatar
    quebek
    4 years ago

    Hello

    This is 'known' issue if you use accelerator and vmware policy type - even though the KB are the same for full and diff check the number of files here and there - only if full all files are being 'mapped' while in diff the changed ones.

    Let me send you to doc

    https://www.veritas.com/content/support/en_US/doc/21902280-136588229-0/v77418134-136588229

    Some excerpt:

    • Supports the full backups and incremental backups. Every Accelerator backup (from a full schedule or incremental schedule) results in a complete image of the virtual machine.

    • You can use incremental backups (cumulative or differential) as follows: To reduce the file-mapping overhead and to reduce the number of files that are recorded in the NetBackup catalog. Cumulative backups may involve more file-mapping because they do not use the random indexing method to determine which files have changed. In some cases, differential backups may be faster than cumulative backups.

    Taken from https://www.veritas.com/content/support/en_US/doc/21902280-136588229-0/v77417993-136588229

  • quebek's avatar
    quebek
    Moderator
    4 years ago

    Hello

    This is 'known' issue if you use accelerator and vmware policy type - even though the KB are the same for full and diff check the number of files here and there - only if full all files are being 'mapped' while in diff the changed ones.

    Let me send you to doc

    https://www.veritas.com/content/support/en_US/doc/21902280-136588229-0/v77418134-136588229

    Some excerpt:

    • Supports the full backups and incremental backups. Every Accelerator backup (from a full schedule or incremental schedule) results in a complete image of the virtual machine.

    • You can use incremental backups (cumulative or differential) as follows: To reduce the file-mapping overhead and to reduce the number of files that are recorded in the NetBackup catalog. Cumulative backups may involve more file-mapping because they do not use the random indexing method to determine which files have changed. In some cases, differential backups may be faster than cumulative backups.

    Taken from https://www.veritas.com/content/support/en_US/doc/21902280-136588229-0/v77417993-136588229