DP9: functionality question

Slight hijack of another thread..

Another test would be to tun the specific backup with the NO_LOG option to see if the catalog updated to the IDB is the bottleneck

What does the log actually provide?  Is it for the humans or does DP need it?

Parents
  • Hello Vince,

    From the DP administrator guide page 129:

    IDB key growth and performance parameters
    Key
    parameter Impact on IDB growth Impact on IDB performance
    Administrator's Guide
    Chapter4: Internal Database
    HPE DataProtector(9.07) Page90of 463
    Logginglevel Defines how muchdataabout files and
    directories is writtentotheIDB, andthe
    requiredstoragespace.
    Influences theconvenienceof browsing
    dataforrestore.
    Catalog
    protection
    Defines how longinformationabout
    backedupdata(suchas filenames and
    fileversions)is kept intheIDB.
    If thecatalogprotectionexpires, datais
    not removedfrom theIDB immediately. It
    is removedonthesameday whenall the
    catalogprotectionfordataontheentire
    mediaexpires.
    None.
    Actual IDB growthdiffers accordingtowhat periodof timethecatalogprotectionis set to(relatively
    short periodof time, thesameperiodas usedforthedataprotection)andtheeffectivelogginglevel.
    MajorIDB growthlasts until thecatalogprotectionexpires. Afterthat, thegrowthis minimal and
    determinedby thegrowthof thebackupenvironment.
    Influence of Logging Level on IDB
    Thedifferent logginglevel settings influencetheInternal Databasegrowth, theconvenienceof
    browsingfilesystems forrestore, and, insomerarecases, backupperformance.
    Thedataprovidedbelow applies tofilesystems backups. If youperform disk image, onlinedatabaseor
    NDMP backup, asmall amount of datais storedintheIDB.
    No Log Only object informationis stored, typically 2kB perfilesystem object.
    Log Directories Sameas No log, andinaddition, 30bytes perbackedupdirectory arestored.
    Log Files Sameas Log directories, andinaddition, 12bytes perbackedupfileare
    stored.
    Log All Sameas Log files, andinaddition, 18bytes perbackedupfilearestored.

Reply
  • Hello Vince,

    From the DP administrator guide page 129:

    IDB key growth and performance parameters
    Key
    parameter Impact on IDB growth Impact on IDB performance
    Administrator's Guide
    Chapter4: Internal Database
    HPE DataProtector(9.07) Page90of 463
    Logginglevel Defines how muchdataabout files and
    directories is writtentotheIDB, andthe
    requiredstoragespace.
    Influences theconvenienceof browsing
    dataforrestore.
    Catalog
    protection
    Defines how longinformationabout
    backedupdata(suchas filenames and
    fileversions)is kept intheIDB.
    If thecatalogprotectionexpires, datais
    not removedfrom theIDB immediately. It
    is removedonthesameday whenall the
    catalogprotectionfordataontheentire
    mediaexpires.
    None.
    Actual IDB growthdiffers accordingtowhat periodof timethecatalogprotectionis set to(relatively
    short periodof time, thesameperiodas usedforthedataprotection)andtheeffectivelogginglevel.
    MajorIDB growthlasts until thecatalogprotectionexpires. Afterthat, thegrowthis minimal and
    determinedby thegrowthof thebackupenvironment.
    Influence of Logging Level on IDB
    Thedifferent logginglevel settings influencetheInternal Databasegrowth, theconvenienceof
    browsingfilesystems forrestore, and, insomerarecases, backupperformance.
    Thedataprovidedbelow applies tofilesystems backups. If youperform disk image, onlinedatabaseor
    NDMP backup, asmall amount of datais storedintheIDB.
    No Log Only object informationis stored, typically 2kB perfilesystem object.
    Log Directories Sameas No log, andinaddition, 30bytes perbackedupdirectory arestored.
    Log Files Sameas Log directories, andinaddition, 12bytes perbackedupfileare
    stored.
    Log All Sameas Log files, andinaddition, 18bytes perbackedupfilearestored.

Children