Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager 19.15 Microsoft SQL Server User Guide

Microsoft SQL Server operational log files for backup and restore operations

The Microsoft application agent uses the Microsoft SQL Server operational log file <program_name>_{cent|self}_<date_and_time>_<trace_ID>.log for centralized and self-service backup and restore operations integrated with PowerProtect Data Manager on a Microsoft SQL Server host.

Example logs for Application Direct operations:

  • Operational log for centralized backup:

    ddbmsqlsv_cent_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log

  • Operational log for centralized restore:

    ddbmsqlrc_cent_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log

  • Operational log for self-service backup:

    ddbmsqlsv_self_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log

  • Operational log for self-service restore:

    ddbmsqlrc_self_20210729193042_TRACE_ID81adc95d817a1151EXEC_IDa15c4d5c6cc3be6d.log

Example logs for VM Direct operations:

  • Operational log for centralized full backup:

    msagentcon_cent_<date_and_time>_<trace_ID>.log

    msagentcon_cent_20220110225147_b84156867446134a_80d7aa6817fba5c2.log

  • Operational log for centralized TLOG backup:

    ddbmsqlsv_cent_<date_and_time>_<trace_ID>.log

    ddbmsqlsv_cent_20220110225203_b84156867446134a80d7aa6817fba5c2.log

  • Operational log for centralized full restore:

    msagentrc_cent_<date_and_time>_<trace_ID>.log

    msagentrc_cent_20220110233331_TRACE_ID_b1d721e93e8efa85_EXEC_ID_bbb6ec0de4c98023.log

  • Operational log for centralized TLOG restore:

    ddbmsqlrc_cent_<date_and_time>_<trace_ID>.log

    ddbmsqlrc_cent_20220111143527_TRACE_ID8ba1d54326cd8fb1EXEC_IDae318092dce5bdf0.log

  • Operational log for tail log backup:

    ddbmsqlsv_cent_20220111144533_TRACE_ID84897b4095326fd0EXEC_IDb9850192b6d8cedd.log

  • Operational log for self-service full restore:

    msagentrc_self_<date_and_time>_<trace_ID>.log

    msagentrc_self_20220111145318_TRACE_ID_ae360518ea36e815.log

  • Operational log for self-service TLOG restore:

    ddbmsqlrc_self_<date_and_time>_<trace_ID>.log

    ddbmsqlrc_self_20220111145447_TRACE_IDbadeadf11898892f.log

  • Operational log for TSDM full backup:

    msagentsv_cent_<date_and_time>_<trace_ID>.log

    msagentsv_cent_20230710225203_b84156867446134a80d7aa6817fba5c2.log

The operational logs are deleted after 15 days by default. To override this default behavior and have the logs deleted before 15 days, you can add the parameter setting purgeOperationalLogDays = <number_of_days> in the file <installation_path>\MSAPPAGENT\settings\.ddbmcon.msappagentconfig. Based on this parameter setting, the logs older than the <number_of_days> are deleted.

For example, with the following parameter setting, the operational logs are deleted after 5 days:

purgeOperationalLogDays = 5

NOTE:

Debug logs are deleted after 30 days.

For VM Direct, the PowerProtect Data Manager export log for backup or restore must include the trace ID.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\