A SAS Viya backup for SAS Cloud Analytic Services (CAS) might fail when you have a distributed server with a CAS secondary controller (also called a CAS backup controller).

When the failure occurs, the /opt/sas/viya/config/var/log/cas/default/cas_YYYY-MM-dd_host-name_pid.log file on the secondary CAS controller contains an INFO message stating that the backup is started. That notification is followed by errors similar to what is shown here:

This problem happens when the CAS backup runs on both the primary and secondary controllers. The backup files cannot be copied from the secondary controller over to the /opt/sas/viya/config/backup directory on the primary controller.   

The backup directory is also called the local vault for the backup. 

In SAS Viya 3.3 when you have a distributed CAS server and also a secondary CAS controller, use the following workaround:

• You must share the /opt/sas/viya/config/backup directory on the primary CAS controller with the secondary CAS controller. Using a symbolic link is not supported for this purpose.

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

Operating System and Release Information

An update for this issue is available for SAS Viya 3.3. For instructions on how to access and apply software updates, see the Managing Your Software section of the SAS Viya 3.3 Administration document at