Hi Team,
I was documenting about the feasibility of the Air Gaping on commvault, and found the picture below.
Can someone guide me where can I find and download the concerned workflows ?
Thanks in advance.
Solved
Commvault Air Gap Orchestration Workflow
Best answer by DMCVault
Let me explain this a bit further though...
Air gapping is mostly architecture, with some software configuration. It first starts with isolating storage. For on premises setups, you would want to architect the solution wherein a secondary or tertiary copy of data is segmented/isolated from the production environment - often referred to as a “vault” environment, or “clean room”. This would typically require network configurations. Ideally the isolated storage can only communicate out to the production environment using Commvault encrypted tunnels. This can be direct one-way, or using a gateway in-between. Use Commvault network topologies to configure the rules for how the resources will communicate to one another.
Gapping is the process of shutting down the communication tunnel periodically. This can be done a few ways, and may require minor customization (and depends on requirements and architecture):
- If you are using virtual media agents then then just enable power management on the media agent. This will shut the media agent down when not in use - super simple, no scripts or workflows needed.
- If you are using a virtual gateway to manage communications between production and vault, you can create a workflow that power manages the gateway by using the VM Utilities predefined activity.
- In the event you don't want Commvault controlling the “gapping”, and would like to control it externally, you can run a command via Windows Task Scheduler (gxadmin command), or CRON (commvault start/stop command) on the Media Agent.
Let me know if you have questions.
- Vaulter
- 53 replies
- Answer
Let me explain this a bit further though...
Air gapping is mostly architecture, with some software configuration. It first starts with isolating storage. For on premises setups, you would want to architect the solution wherein a secondary or tertiary copy of data is segmented/isolated from the production environment - often referred to as a “vault” environment, or “clean room”. This would typically require network configurations. Ideally the isolated storage can only communicate out to the production environment using Commvault encrypted tunnels. This can be direct one-way, or using a gateway in-between. Use Commvault network topologies to configure the rules for how the resources will communicate to one another.
Gapping is the process of shutting down the communication tunnel periodically. This can be done a few ways, and may require minor customization (and depends on requirements and architecture):
- If you are using virtual media agents then then just enable power management on the media agent. This will shut the media agent down when not in use - super simple, no scripts or workflows needed.
- If you are using a virtual gateway to manage communications between production and vault, you can create a workflow that power manages the gateway by using the VM Utilities predefined activity.
- In the event you don't want Commvault controlling the “gapping”, and would like to control it externally, you can run a command via Windows Task Scheduler (gxadmin command), or CRON (commvault start/stop command) on the Media Agent.
Let me know if you have questions.
1 person likes this
Mike Struening wrote:
Let me find out. I know some people I can check with.
Thanks
DMCVault wrote:
Let me explain this a bit further though...
Air gapping is mostly architecture, with some software configuration. It first starts with isolating storage. For on premises setups, you would want to architect the solution wherein a secondary or tertiary copy of data is segmented/isolated from the production environment - often referred to as a “vault” environment, or “clean room”. This would typically require network configurations. Ideally the isolated storage can only communicate out to the production environment using Commvault encrypted tunnels. This can be direct one-way, or using a gateway in-between. Use Commvault network topologies to configure the rules for how the resources will communicate to one another.
Gapping is the process of shutting down the communication tunnel periodically. This can be done a few ways, and may require minor customization (and depends on requirements and architecture):
- If you are using virtual media agents then then just enable power management on the media agent. This will shut the media agent down when not in use - super simple, no scripts or workflows needed.
- If you are using a virtual gateway to manage communications between production and vault, you can create a workflow that power manages the gateway by using the VM Utilities predefined activity.
- In the event you don't want Commvault controlling the “gapping”, and would like to control it externally, you can run a command via Windows Task Scheduler (gxadmin command), or CRON (commvault start/stop command) on the Media Agent.
Let me know if you have questions.
Thanks,
- Vaulter
- 53 replies
We have a pre-canned workflow available now:
https://documentation.commvault.com/11.26/essential/147278_starting_or_stopping_network_gateway_to_create_air_gap.html
DMCVault wrote:
We have a pre-canned workflow available now:
https://documentation.commvault.com/11.26/essential/147278_starting_or_stopping_network_gateway_to_create_air_gap.html
Wow! That’s very useful, thanks a lot
1 person likes this
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.