Skip to main content
commvault.com commvault.com
Solved

Red Hat Enterprise Virtualisation (RHEV) Questions

  • September 21, 2021
  • 3 replies
  • 591 views
M
Byte
Forum|alt.badge.img+6

Hi Team,

 

We are looking at a requirement to deploy an RHEV-compatible backup configuration on behalf of our customer.

Although I have implemented plenty of ESX configs, this will be the first RHEV, so I have a few questions.

 

1 - Ports required to access the RHEV Manager host .

Which ones do we need to open up?

I can’t see anywhere in available documentation for any ports that I may need to open, but I’m thinking that there should be. I remember in ESX that 903 (or is it 902, ha!) needs to be open so I would expect this to be similar for RHEV.

 

2- The VSA Proxy - Does this introduce another Media Agent for us to manage?

So if, or when we install the VSA client onto our RHEV vm, am I correct in assuming that will also install the Media Agent component? And if it does, we obviously have another server to manager and maintain patch levels etc etc.

 

3 - RHEL 7.7

The vm’s are running at RHEL 7.7 which I think is XFS filesystem by default.

What do we do if we need a granular restoration of a file?

Do we need a new FREL, or can we use an existing?

Alternatively, can we install restore-only agents on each vm and avoid the need for FREL?

 

4 - Any other gotcha’s I need to know about?

May as well ask whilst I’m here!

 

Thanks everyone ….

Best answer by MichaelCapon

Hello @MountainGoat ,

 

Since the VSA will connect to RHEV Manager, ports 443 and 80 will be required.

 

The VSA will be a VM here, Since the process uses the hot-plug method.
So you can Deploy Windows or RHEL VM’s as proxies: https://documentation.commvault.com/commvault/v11_sp20/article?p=3358.htm

For Windows disable Automount and for Linux disable lvmetad.
Red Hat guest tools must be installed in VSA proxy machines.
Ensure that the VirtIO SCSI driver is installed in the VSA, preferably the latest Stable release.

 

You can send the data from the VSA to the MA (via LAN) or have the VSA VM access the Storage as an MA (depending on your requirements).

You can use an existing FREL if it supports the current OS’s Filesystem’s used and has appropriate NW access to the MA etc.
-Note that a RHEL VSA can be used as a FREL (if required) by Installing the MA Package: https://documentation.commvault.com/commvault/v11_sp20/article?p=30829.htm 

 

Depending on the amount of VM’s to protect here, you may want to consider multiple VSA Proxies for load-balancing and some level of fault tolerance.

 

Best Regards,

Michael

View original
Did this answer your question?

3 replies

MichaelCapon
Vaulter
Forum|alt.badge.img+14
  • MichaelCaponVaulter
  • Vaulter
  • 349 replies
  • Answer
  • September 21, 2021

Hello @MountainGoat ,

 

Since the VSA will connect to RHEV Manager, ports 443 and 80 will be required.

 

The VSA will be a VM here, Since the process uses the hot-plug method.
So you can Deploy Windows or RHEL VM’s as proxies: https://documentation.commvault.com/commvault/v11_sp20/article?p=3358.htm

For Windows disable Automount and for Linux disable lvmetad.
Red Hat guest tools must be installed in VSA proxy machines.
Ensure that the VirtIO SCSI driver is installed in the VSA, preferably the latest Stable release.

 

You can send the data from the VSA to the MA (via LAN) or have the VSA VM access the Storage as an MA (depending on your requirements).

You can use an existing FREL if it supports the current OS’s Filesystem’s used and has appropriate NW access to the MA etc.
-Note that a RHEL VSA can be used as a FREL (if required) by Installing the MA Package: https://documentation.commvault.com/commvault/v11_sp20/article?p=30829.htm 

 

Depending on the amount of VM’s to protect here, you may want to consider multiple VSA Proxies for load-balancing and some level of fault tolerance.

 

Best Regards,

Michael

M
1 person likes this
  • M
    MountainGoat
L
Vaulter
Forum|alt.badge.img+14
  • LedoespVaulter
  • Vaulter
  • 248 replies
  • September 21, 2021

1 -  VSA proxy will connect via https to the RHEV Manager host so 443

 

2- This is a VSA RHEV machine, one per datacenter, MA component is not needed unless you want to use it as FREL or to write directly on a library.

 

3 - This depends where is your backup data stored. If you use a physical Linux MA, then it would be the perfect choice as backup data is presented by the MA to itself if configured as FREL.

3.b Alternatively, can we install restore-only agents on each vm and avoid the need for FREL?

Well, this allows to redirect the granular restore to the VM however the backup image needs to be interpreted by a FREL

4 - Newer RHEV versions are better than older.

 

 

MichaelCapon
M
2 people like this
  • MichaelCapon
    MichaelCapon
  • M
    MountainGoat
M
Byte
Forum|alt.badge.img+6
  • MountainGoat
  • Author
  • Byte
  • 37 replies
  • September 21, 2021

Thanks for the clarification everyone.

 

@MichaelCapon , @Ledoesp To clear up my question regarding whether the new Proxy (with a VSA component  installed) would be a Media Agent - I think I was mistaken in the belief that it may of required the MA component.

 

It looks like it doesn’t, as suggested above.

https://documentation.commvault.com/commvault/v11/article?p=115916.htm

 

Clarification appreciated.

MichaelCapon
1 person likes this
  • MichaelCapon
    MichaelCapon

Reply


Most helpful members this week

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings