There is out-of-box content to apply the updates (which, I believe, do check for disk space as part of their Relevance), but performing other pre/post patch orchestration such as taking backups or automated testing of applications post-patch is outside the scope of the Patch content.
There are workplans in the Server Automation plans that can accomplish this, and some customers have developed or contracted out developments to integrate into their existing Orchestrators or CMDB applications.
There are ways to take SQL Backups using SQL Server Management Studio; or the tsql.exe command line; or any number of third-party backup management software such as Tivoli Storage Manager from IBM, or Veritas NetBackup, or Backup Exec, or …well, lot’s of tools. It depends a lot on what you have available in your company.
The “right” way to capture and maintain your backups is probably beyond what the BigFix forum can help with… but if you have reason to think that your data isn’t getting backed up, that should be a very high priority to get corrected.
So, just an thought…can we take backup via BigFix and store in share location ?
I know we need to use third party tool to take backup but here we need to totally depend on other applications which can delay our sql patching.
Hence was thinking if we can take the back up via BigFix and than perform the actual patching activity.
As of now client is using a tool which do pre check, take backup and then perform Patching.