Advantages of using Commvault WorkFlow

I created two important workflows on Commvault, they create and mount snapshot to hosts from EMC VMAX 3 and Hitachi VSP. They have been working without problems for months. 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.

Secondly, security is very important every time. Normally, employees in “server team” can access your management server. Maybe, the other teams can also access your management server. So, they can access and change your script. But, if you use a workflow, only authorized employees can find and change scripts. On the other hand,  you can encrypt and hide passwords used in the scripts and even authorized employees can’t see passwords of important service users that are embedded in the script.

Thirdly, you don’t have to think about logging, mailing, catch errors, create alarms, etc. So you must only write pure codes. All the other stuff is ready. Normally, if you want to write a good script, you have to think about this stuff that most of the code consists of these. So, it’s hard to read and find something in the code like this. However, in Commvault Workflow, you can focus on pure code.

Finally, It can be integrated with CommVault features like IntelliSnap®, backup, restore, etc. Therefore, currently, the biggest problem is to create a consistent snap. And you can solve this problem easily with IntelliSnap® integrated scripts. Also, if you need periodically backup and restore scripts, you have all needs in the tool.

Consequently, Workflow in Commvault has many advantages and I only mentioned the most important ones here, but there are more.  As well, you can use ready-made scripts. You can find more information on the links below.

Commvault workflow design

Security Tips for Storage and Backup Admins

1. EMC Networker: Change “remote access” option *@*  on every client” –>

2. Veritas Netbackup: Remove No.Restrictions file –>

3. EMC VMAX: Change default password of SMC user in unisphere (take snapshot or backup before changing. If you would get “Failed to authenticate user.” error, there is no way to fix except restore or reinstall. And, If you reinstall unisphere you will loose performance database. There is a trick to not get this error.)

4. EMC VPLEX: Change default passwords of VPLEX. Default passwords of VPLEX is already complex, but anyone can find default passwords of service, admin and root users in the documents.

5. Commvault: Activate Ransomware Protection –>

Security expolit on Netbackup (No.Restrictions)

Sometimes we or some consultants put No.Restrictions file in “INSTALL DIR\netbackup\db\altnames” directory, this option  makes our work easier. But it is a security risk, because of every netbackup client on the your network can restore data from any other clients. So, anybody can restore data of your important servers, then they can lookup and/or copy your important datas. To close this security exploit, you must delete the file No.Restrictions.