Data Domain: Enabling DD Boost API Logging - Precert Logs

Question: What is DD Boost Precert Logging? DD Boost Precert Logging is a diagnostic logging feature that records DD Boost API transactions between a DD Boost client and the Data Domain system.
Answer: It is commonly used for troubleshooting performance issues, failures, latency, and communication problems.

Question: What does Precert Logging capture? Precert logging captures DD Boost API activity including read operations, write operations, backup activity, restore activity, DD Boost library interactions, API call timing information, and client-side latency indicators.
Answer: It provides detailed visibility into DD Boost API behavior for troubleshooting and performance analysis.

Question: Why are no precert logs being generated? Verify that the ddboost_precert.ini file exists, is located at the operating system root, the log directory exists, the log directory is writable, and a new backup or restore operation has started.
Answer: Missing configuration, incorrect placement, permission issues, or lack of new DD Boost activity are the most common causes.

Question: Does enabling precert logging immediately generate logs? The configuration only enables logging capability.
Answer: No, log files are generated only when new DD Boost API requests are received.

Question: Why doesn't my currently running backup generate precert logs? Precert logging only captures API activity initiated after the configuration is detected.
Answer: Existing backup or restore jobs continue without generating precert logs.

Question: Do I need to restart my backup or restore job? If the job was already running when logging was enabled, start a new operation.
Answer: Yes, a new backup or restore job is required to generate precert logs.

Question: What is the most common reason precert logging does not work? Common causes include ddboost_precert.ini not being at the root level, being accidentally named ddboost_precert.ini.txt, a missing log directory, or insufficient permissions.
Answer: Configuration and filesystem issues are the most frequent causes.

Question: Where should the ddboost_precert.ini file be placed? 

Linux: /ddboost_precert.ini. Windows: C:\ddboost_precert.ini.

Answer: The file must reside in the operating system root directory.

Question: Can the ddboost_precert.ini file be stored in another folder? The DD Boost plugin only checks the operating system root directory.
Answer: No, the file must be stored at the root.

Question: How can I verify the file is not actually

ddboost_precert.ini.txt

Open File Explorer, enable File Name Extensions, and verify the filename.
Answer: Ensure the file is named 

ddboost_precert.ini and not ddboost_precert.ini.txt.

Question: Why is the DDLog directory empty after enabling logging? Possible causes include no new DD Boost activity, permission issues, or a configuration file that was not detected.
Answer: Run a new backup, restore, or DDPCONNCHK test to generate activity.

Question: What is DDPCONNCHK and why is it useful? DDPCONNCHK is a DD Boost connectivity validation tool.
Answer: It can generate DD Boost API activity and quickly confirm that precert logging is working.

Question: Can DDPCONNCHK be used to test my configuration? Engineers frequently run DDPCONNCHK after enabling logging.
Answer: Yes, it is a common way to verify logs are being generated before reproducing a problem.

Question: Why are my precert logs growing so quickly? Precert logging records every DD Boost API call.
Answer: Large backup environments can generate significant log volume in a short time.

Question: How much disk space should I allocate? A common recommendation is 

num_log_files=3 and log_file_size=500.

Answer: This provides approximately 1.5 GB of log storage before rotation occurs.

Question: Can precert logs fill a filesystem? Logging can consume significant disk space if not monitored.
Answer: Yes, full filesystems can result in backup failures, outages, and service interruptions.

Question: What is the purpose of num_log_files? This parameter controls the number of rotated log files retained.
Answer: For example, num_log_files=3 creates ddboost_precert.log, ddboost_precert.log.1, and ddboost_precert.log.2.

Question: What is the purpose of log_file_size? This parameter defines the maximum size of each log file in MB.
Answer: For example, log_file_size=500 allows each file to grow to 500 MB before rotation.

Question: What does ddcl_logs_include=true do? It enables DD Boost Client Library logging information within the precert logs.
Answer: The recommended setting is ddcl_logs_include=true.

Question: What does ddcl_logs_sev=4 mean? This parameter controls logging severity.
Answer: Severity level 4 provides detailed troubleshooting and debugging information.

Question: Do I need BoostFS debug logging in addition to precert logging? Additional logging is not always required.
Answer: For BoostFS-specific issues, enabling both often provides a more complete diagnostic picture.

Question: For BoostFS, do I need to unmount and remount? Unmounting and remounting reinitializes BoostFS activity.
Answer: In many cases, yes, this helps initiate new DD Boost activity.

Question: What is the correct BoostFS debug logging syntax? The correct syntax is -o log-level=debug.
Answer: Do not use --o log-level=debug because only a single dash is valid.

Question: Why did remounting BoostFS suddenly make precert logs appear? Remounting creates a new initialization cycle for BoostFS.
Answer: Logging begins when new DD Boost API activity occurs and the plugin detects the configuration file.

Question: Is restarting an application equivalent to remounting BoostFS? Any action that creates new DD Boost API activity can trigger logging.
Answer: Usually yes, examples include restarting RMAN, backup software, or running DDPCONNCHK.

Question: Can RMAN generate precert logs without unmounting BoostFS? RMAN can initiate new DD Boost API requests directly.
Answer: Yes, starting a new RMAN operation is normally sufficient.

Question: How do I disable precert logging? Delete ddboost_precert.ini or rename it to ddboost_precert.ini.disabled.
Answer: Logging only activates when the exact filename ddboost_precert.ini exists.

Question: Do I need to reboot the host after removing the ini file? The plugin checks for the configuration file during future operations.
Answer: No, rebooting is not required.

Question: What permissions should be used on Linux? Example permissions include 

mkdir /DDLog, chmod 777 /DDLog, and chmod 777 /ddboost_precert.ini.

Answer: The DD Boost process must be able to read the configuration file and write to the log directory.

Question: Where are BoostFS logs stored by default? 

Linux: /opt/emc/boostfs/log. Windows: C:\BoostFS\Log.

Answer: These locations are separate from DD Boost precert logs.

Question: Are BoostFS logs and precert logs the same thing? BoostFS logs contain mount activity, filesystem operations, and application events.
Answer: No, precert logs contain DD Boost API transactions, library communications, and I/O timing data.

Question: What logs should I provide to Support? Depending on the issue, collect ddboost_precert.log, rotated precert logs, BoostFS logs, DDPCONNCHK output, application logs, and requested support bundles.
Answer: Providing all relevant logs helps accelerate troubleshooting.

Question: What should I do if logs still are not generated after following this KB? Collect evidence such as the ddboost_precert.ini location, log directory listing, DDPCONNCHK output, BoostFS mount command, and permissions information.
Answer: Submit the collected information to Dell Technical Support for further analysis.