When a cluster of SAS Web Application Server instances is configured in the SAS middle tier, the SAS 9.4 Deployment Backup and Recovery tool might report the following failure:

You might see this failure during a regularly scheduled backup or when you execute batch commands for the tool.

The problem occurs when the format of the BackupHistory.xml file is damaged as a result of more than one process modifying the file during a backup.

The problem that causes the failure is resolved in SAS 9.4 (TS1M2).

Click the Hot Fix tab in this note to access the hot fix for this issue.

Important: If you are experiencing the problem reported in this SAS Note, you must perform the steps required for the hot fix documented below. Any backups that exist before you follow the steps required for the hot fix will no longer be restorable. For this reason, SAS recommends that you run sas-backup using the SAS Deployment Backup and Recovery tool before and after installing the hot fix.

Note:If you are not experiencing the problem reported in this SAS note, renaming the BackupHistory.xml file is not required.

Steps Required for the Hot Fix

1. Find and rename all copies of the BackupHistory.xml file.

The BackupHistory.xml file can be found in the following locations.

• The central vault location
• configuration- directory\Levn\Backup\dropzone
• configuration- directory\Levn\Web\WebAppServer\SASServer1_XX\temp\SASDeploymentBackup_APPHOME
2. Perform an ad hoc (unscheduled) backup now. This step re-creates the BackupHistory.xml file.

To perform an ad hoc backup, run the sas-backup batch command per the instructions in the "Using the Deployment Backup and Recovery Tool" section of the SAS^® 9.4 Intelligence Platform: System Administration Guide.

3. Apply the hot fix using the instructions in the hot fix documentation.
4. After applying the hot fix, perform another ad hoc (unscheduled) backup now.

If a hot fix is not available for your version of SAS software, use the following steps to resolve the problem.

Workaround: Use If No Hot Fix Is Available for Your Release of SAS Software

Important: Any backups that exist before the workaround is implemented will no longer be restorable after the workaround is implemented. For this reason, SAS recommends that you run sas-backup using the SAS Deployment Backup and Recovery tool after you perform the workaround.

Step 1: Modify the configuration so that only the SAS Web Application Server instance in the cluster runs the scheduled backup.

In this step, you select one SASServer1_X instance to run the scheduled backup. You then change the configuration for the other SASServer1_X instances to prevent them from running during the scheduled backup. By default, the SAS Deployment Backup and Recovery tool is configured in server name SASServer1. The SASServer1_X instance that you choose to run the backup must remain started in order for a scheduled backup to run.

1. Select one SASServer1_X instance to run the backup.
2. For all other SASServer1_X instances, locate the applicationContext.xml file:

configuration-directory\Levn\Web\WebAppServer\SASServer1_X\sas_webapps\sas.svcs.admin.backup.war\WEB-INF\spring-config\applicationContext.xml

3. Edit the file and comment out the following bean definition, as shown here:
<!--<bean name="backupServiceApplicationListener" class="com.sas.svcs.backup.spi.BackupServiceContextListener" > <property name="username" value="@{publish.user}" /> <property name="password" value="@{publish.password}" /> <property name="userService" ref="userService" /> <property name="sessionService" ref="sessionService" /> </bean>-->
4. Repeat steps B and C for all SASServer1_X instances except the one chosen to run the backup.

Step 2: Find and rename all copies of the BackupHistory.xml file.

The format for the existing BackupHistory.xml file is incorrect. To resolve the formatting error, find all copies of the file for your deployment and rename the files. When the next backup is run, a new BackupHistory.xml file with correct formatting is created.

The BackupHistory.xml file can be found in the following locations.

• The central vault location
• configuration-directory\Levn\Backup\dropzone
• configuration-directory\Levn\Web\WebAppServer\SASServer1_XX\temp\SASDeploymentBackup_APPHOME

Step 3: Perform an ad hoc (unscheduled) backup now.

This step is required to re-create the BackupHistory.xml file. SAS recommends that you perform this step immediately after you perform the workaround rather than waiting for a regularly scheduled backup.

To perform an ad hoc backup, run the sas-backup batch command per the instructions in the "Using the Deployment Backup and Recovery Tool" section of the SAS^® 9.4 Intelligence Platform: System Administration Guide.

Note: If, at a later time, you or someone else modifies the schedule by using the sas-add-backup-schedule or sas-remove-backup-schedule, then you must restart all SASServer1_X instances.

Operating System and Release Information

A fix for this issue for SAS Middle Tier 9.4_M1 is available at: