SAS® Deployment Backup and Recovery Tool server- and datasource-specific logs are not generated and.or might be missing content


In SAS® 9.4M9 (TS1M9) on Windows systems, performing backup and recovery operations with the SAS Deployment Backup and Recovery Tool (DBRT) might not generate all expected log files, or certain log files might be generated with little or no content. This issue does not appear to occur on Linux deployments.

The backup and recovery jobs might complete, but diagnostic and audit logs are incomplete or missing.

This issue is a regression that affects SAS 9.4M9 on Windows. 

Cause

A defect in SAS 9.4M9 on Windows causes DBRT logging configuration files to use file path syntax that prevents Log4j from correctly resolving log destinations.

Workaround

For SAS 9.4M9 on Windows, you can temporarily resolve the issue by modifying the affected logging configuration files and restarting the SAS environment. 

To work around this issue, complete the following steps:

1. Back up the existing files.

Create backups of the following directories

2. Update the log file locations.

Modify <SASHome>\SASPlatformObjectFramework\9.4\SASDeploymentBackup\serverlog4j2.properties as follows:

Modify <SASHome>\SASPlatformObjectFramework\9.4\SASDeploymentBackup\utilitylog4j2.properties as follows:

3. Update Log4j configuration references.

Modify <SASHome>\SASPlatformObjectFramework\9.4\tools\admin\sas-recover.ini as follows:

Modify <SASHome>\SASPlatformObjectFramework\9.4\tools\admin\sas-backup.ini as follows:

Modify <SASHome>\SASPlatformObjectFramework\9.4\SASDeploymentBackup\BackupServer.ini as follows:


4. Restart all SAS services and servers in the deployment.

5. Validate the fix.

Run a new backup and recovery operation and verify the following: