"DBSS - Unable To Check Backup Media" alarm fires because space cannot be queried (4371990)

"DBSS - Unable To Check Backup Media" alarm fires because space cannot be queried

"DBSS - Unable To Check Backup Media" alarm fires because space cannot be queried

In some cases messages like the following may appear

ERROR [AGENTNAME-lowPriorityPool-1-[DBSS_Backup_Locations][DATE]] com.quest.qsi.fason.sqlserver.collection.processor.database.backup.DBSSBackupFreeDiskProcessor - Failed to get free space of disk [\\SERVERNAME\SHARED_FOLDER] . Reason: File Not Found java.lang.Exception:File Not Found

or

ERROR [AGENTNAME-lowPriorityPool-7-[DBSS_Backup_Locations][DATE]] com.quest.qsi.fason.sqlserver.collection.processor.database.backup.DBSSBackupFreeDiskProcessor - Failed to get free space of disk [\\SERVERNAME\SHARED_FOLDER\] . Reason: Access is denied. java.lang.Exception: Access is denied.

or

ERROR [AGENTNAME-lowPriorityPool-2-[DBSS_Backup_Locations][DATE]] com.quest.qsi.fason.sqlserver.collection.processor.database.backup.DBSSBackupFreeDiskProcessor - Failed to get free space of disk [\SERVERNAME\SHARED_FOLDER] . Reason: The user name or password is incorrect.
java.lang.Exception: The user name or password is incorrect.

Cause 1

For issues specifically related to SAN drives.

Cause 2

Server or share permissions prevent the monitoring agent from accessing a remove drive.
 

Resolution 1

Workaround

Please contact Support for hotfix HFX-387 for this issue for the 6.3.0.20 cartridge.

Status

This issue has not yet been logged as a defect to be fixed in an upcoming release of the SQL Server cartridge.
 

Resolution 2

There are two requirements necessary to read remote share locations

1. The database agent must be configured to use OS monitoring of the host.
2. The FglAM process (service account) must have access to query the shared folder. This can be accomplished (for example) by
   1. using a common domain account with permissions to the backup location and to run the service,
   2. or using the same local username (when the FglAM server and remote server are not in a domain).

To test the connection from the FglAM and agent to the remote folder:

• Log in to the FglAM machine with the same user that is running the FglAM process

• Open a command prompt

• Run a DIR command to the share location => dir \\SERVERNAME\SHARED_FOLDER\

If any error message are encountered, add the username that is running the FglAM process to the shared location permissions.

 

HFX-387