Hi, our DBA noticed some special behavior of the commvault sql agent. They noticed that the agent is scanning for a SQL Stored Procedure & Assembly (CLR) at the time a backup is scheduled  :

USE [DB] SELECT count(object_id) FROM [SYS].[objects] WHERE object_id = OBJECT_ID(N[DBO].[proc_CheckRbsInstalled]) and [type] in (N'P.N'PC')

The behavior is the following : 

connection to db#1 and executes query on db#2… connected to db#2 it executes on db#3 , ...

Why is the sql agent acting like that ( our dba's don't like that process ) ? ( Why is it checking that store proc. ( proc_CheckRbsInstalled ) ?)

Certainly looks unusual and any DBA with a keen eye would be suspicious. I suspect it is connected to a niche Commvault feature for SQL Server Table Archiving?

Edit: See David's answer

Hi Lionel,

CV runs many queries as part of its backup/discovery process.

You will see that we perform certain checks against each DB as the job progresses as well as collecting backupset information as the jobs complete to allow CV to perform consistency checking against the log backups.

The check you've highlighted here is to see whether the instance/databases are configured for RBS. We do this by checking if the stored procedure exists.

https://docs.microsoft.com/en-us/openspecs/sharepoint_protocols/ms-wssfo3/6d9b5c75-b83d-472c-bb5d-fa7f75fd31d7

I believe this is part of RBS-Aware backup for SharePoint Content Databases:

https://documentation.commvault.com/commvault/v11/article?p=17813.htm

In the SQLiDA.log you can see it performing the RBS status checks.

Is there anything in particular about this behaviour that the DBA is having issues with?

David

Hi Anthony,

It won't be for table level, it will be for RBS support. The Table Level stuff uses VSS and block-level technology.

David

Thanks David, I have ammended my response.

Hi David,

here's what the DBA respond to me then ( in short ) :

So every MSSQL instance is a sharepoint for CV???

It is always better to check system tables [master file type will not change over time] and not a name of a stored procedure…

To check if RBS is active YOU DO NOT need this…

Just do… on server level…

strComputer = "."

‘ ComputerManagement12 = MSSQL2014… ComputerManagement11 = MSSQL2012… etc…

Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\Microsoft\SqlServer\ComputerManagement12")

Set colItems = objWMIService.ExecQuery("SELECT * FROM FilestreamSettings",,48)

For Each objItem in colItems

    Wscript.Echo "-----------------------------------"

    Wscript.Echo "FilestreamSettings instance"

    Wscript.Echo "-----------------------------------"

    Wscript.Echo "AccessLevel: " & objItem.AccessLevel

    Wscript.Echo "IncompleteOperation: " & objItem.IncompleteOperation

    Wscript.Echo "InstanceName: " & objItem.InstanceName

    Wscript.Echo "IsClustered: " & objItem.IsClustered

    Wscript.Echo "RsFxVersion: " & objItem.RsFxVersion

    Wscript.Echo "ShareName: " & objItem.ShareName

Next

and If you don’t want to use WMI…

You can just do…

EXEC sp_configure filestream_access_level

You might want to open a ticket with Support as the tech assigned can deal with Development directly for questions such as this.