Hi @Adel BOUKHATEM , thanks for the question!

Gridstor (link below) allows you to have multiple Media Agents connected to multiple data paths for redundancy.

This way, if MA1 is down, MA2 can take over (and if both are online, you can have some balance involved.

Take a look at this document and see what the feature offers.  I have a feeling you’ll like what you see!

https://documentation.commvault.com/11.24/expert/10842_gridstor_alternate_data_paths.html

Hi @Mike Struening, thanks a lot for your reply.

Actually, I got a bit lost. The GridStor allows changing the path for a backup in case a Media fails.

What I am looking for, is how to make sure that both Media Agents have access to the same LUN without corrupting the data: I guess this is a prerequisite for the grid store. Or maybe it shouldn’t have access to the same LUN, I don’t know.

Sharing a mount path seems to be an answer:

https://documentation.commvault.com/11.24/expert/9374_sharing_mount_path.html

However, we are using SAN not LAN. But the link below doesn’t realy helps:

https://documentation.commvault.com/11.24/expert/9788_san_attached_libraries_configuration.html

Can you please enlighten me to better understand? Appreciate it a lot.

When you use LUN's which are assigned to 2 media agents in a non-clustered environment you should use mount path sharing as both OS cannot claim the file system at the same time.

Depending on the OS you will get optimal results using:

• Transport type Data Server - IP for linux media agents
• Transport type regular and point to an UNC path for windows media agents

This way you will still have a dependency on the media agent which has the LUN assigned to the OS.
If the OS is down, access to the LUN is not possible.

Therefore you might want to shift your method towards a SAN Data Server setup which allows different media agents to access the same LUN's simultaneously, keep use of global dedup, allows FC connectivity and removes the dependency on specific Media Agent to access the LUN:

https://documentation.commvault.com/11.24/expert/9562_shared_san_data_server.html

Please note that there are OS and hardware dependencies when configuring this solution:

https://documentation.commvault.com/11.24/expert/9569_shared_san_data_server_system_requirements_for_fibre_channel.html

Hi @Jos Meijer ,

Thanks a lot for your response.

So according to you, the best option is to configure a “SAN Data Server”, which I guess is configured as below:

https://documentation.commvault.com/11.24/expert/9576_configure_fibre_channel_san_data_server_with_san_attached_storage.html

I still have a question,

Is “SAN Data Server” which I guess is mount path sharing, the best way to assure the High availability for Media Agents?

Thanks a lot for your help !

Hi @Adel BOUKHATEM 

What do you mean by High availability : for backup ? for restore ? for both ?

Hi @Laurent ,

At the first position, it is the backup; However, I still think that we must be able to restore at any moment even if one Media fails. So I would say both.

Hi @Adel BOUKHATEM ,

Your welcome

Based on your requirements this would be an affective method to provide a shared storage location via FC to multiple media agents and ensuring HA for both backup and recovery.

Other methods will require IP based solutions or will lack HA.

Looking forward to hear the results

Hi @Jos Meijer ,

It seems that I got my answer. Thanks all for your help, much appreciated !

Best Regards

Your welcome @Adel BOUKHATEM