Advantages of using Commvault WorkFlow

 

I created too many important workflows on Commvault. The use cases where I used workflows are as follows:

  • Repetitive restore tests,
  • Conditional backup that makes some operations before it,
  • Create snapshots and mount snap disks to hosts from Hitachi, EMC, and HPE storages.
  • They have been working without problems for years. So, I would like to talk about the advantages of using a Workflow.

First of all, the biggest advantage is the central management. Usually, snap scripts are distributed on different folders in different management servers. You can find them in “Task Scheduler” or “Crontab” if you are a little bit clever and lucky. But, it is a big deal in some environments. Also, the second deal is to find related files and figure out connections. If you use Commvault Workflow, all authorized employees can find and change scripts easily. And, to understand and see the big picture is very easy. You need a little time ( maybe minutes) to understand. On the other hand, in normal scripts, it can take hours, maybe days.

Read More


Protect Commvault Disk Libraries from Ransomware

To protect disk libraries from Ramsomware, you can activate Ramsomware Protection on properties of Commvault Media agent

http://documentation.commvault.com/commvault/v11/article?p=features/disk_library/t_enable_ransomware_mediaagent.htm

Another important feature, you can get alert if commvault backed up encrypted ransomware files

http://documentation.commvault.com/commvault/v11/article?p=features/disk_library/r_ransomware_protection.htm


Commvault Simpana 10 SP11 güncellemesi sırasında çıkan hata çözümü

Commvault Simpana 10 SP11 güncellemesi sırasında MSSQL servisleri kapandıktan sonra açılmıyor ise ve Event viewer Application Loglarında aşağıdaki hataları görüyor iseniz:

* Initializing the FallBack certificate failed with error code: 15, state: 1, error number: 6000.
* TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
* TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
* SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

 Çözüm:

Read More