CommServe rebuild/upgrade path from 11.32 - best practise?

Hi ​@Paul Hutchings,
 

Both Windows and Linux CommServe have their respective advantages, and the choice largely depends on the intended usage.

Currently, the Java Console serves as the primary user interface for managing policies and schedules. Installing the OVA image on Linux primarily provides the web UI, which is more focused on Plans and RPO configurations.

Therefore, using a Windows CommServe at this stage is the ideal approach, as it allows users to retain the existing interface and continue navigating options in the familiar environment.

Refer below link for latest OVA image for both windows and Linux.

https://cloud.commvault.com/commandcenter/#/softwareStore/31016

Thanks Pradeep so it sounds like you’re saying if I download the 11.36 Windows OVA I can import that straight into VMware and then import the latest DR set?

From the install/deploy guide here Deploy the OVA I’m not entirely clear whether this OVA creates a Windows environment that I can login to via the console or if it’s just for the web UI?

I don’t need the CommServe domain joined so if I can download a pre-hardened standalone appliance it’s obviously much simpler.

Hi ​@Paul Hutchings ,

Yes, we can use pre hardened image and then proceed with standard install process and restore the required DR SET.

Pradeep thank you.  I downloaded the OVA today and it looks simple enough.  Question I have is the OVA has multiple virtual disks so is designed to scale and ready to be used as a MA/DDB server etc.

I’m only using it as a CommServe.

When I try to do a test restore of the DR set from my CommServe it doesn’t pick up the DB restore location which I assume is because of the different disk layout.

Can you confirm the default DB restore location on the OVA please?

The csrecoveryassistant.exe doesn’t seem to fill anything in by default.

Also can everything be done with the virtual NIC disconnected so I can stage and test everything before swapping out the production CommServe?

Hi ​@Paul Hutchings ,

By Default the Data files are located under the install directory ContentStore > Data folder.
However, its unusual that the Data file location is missing from the Csrecovery window thats I suspect is because virtual disk.

Refer below document for details and steps on restoring DR SET using CSrecoveryassistant.exe tool.

https://documentation.commvault.com/v11/commcell-console/recovering_commserve_database_using_recovery_assistant_tool_for_windows.html 

Nothing happened here so I’m back with the original question but six months later.

What is the current recommendation for getting off 11.32?

I notice the Arlie/support best practise is now to use the 11.36 Linux appliance and at first glance that looks pretty simple i.e. download and recover DR set and off you go.

Are there still firm reasons to go with the Windows OVA?

Hi ​@Paul Hutchings,

There is no real reason why you must choose Windows over Linux. I usually see the choice for Windows being made out of familiarity with the OS. On the other hand, Linux does not have the issue with license costs.

The CommCell console is a Java application that is only supported on Windows so if you want to have this on your CommServe, Windows is the way to go.

If you want to backup MS365 cloud data, it might be useful to be on Windows as some application types require Windows web server (which is often the same server as the CommServe in small environments) but all other functions should work with a Linux CommServe. You can opt for a separate Windows server that hosts components needed for applications that need these specific components.

As for migration, you can also use CommServe LiveSync to migrate to a new CommServe without downtime. After migration you can either choose to disable LiveSync or deploy a second CommServe and keep CommServe LiveSync enabled for a HA CommServe setup.

CommServe LiveSync For High Availability Disaster Recovery

Kind regards,

Paul

Yeah there’s definitely a bit of the familiarity thing there and I guess I’m not entirely clear how much of the OVA build is 100% “Sealed appliance and Commvault manage the entire thing” and how much is Commvault just giving you the foundations but underneath it all you’ve still got a Rocky Linux distro to manage.

I suppose thinking about it the sensible option might be go with the Windows OVA as in a small environment like ours it’s reasonably simple/trivial to take a DR backup and import it on a replacement CS.

I like the idea of the hardened OVA more than trying to harden an OS directly.

Hi ​@Paul Hutchings,

My experience with the Windows OVA has only been for one environment on 11.28 so this may not be representative but we saw multiple issues with the Windows OVA for 11.28.

The OVA had everything on one disk partition which I am not a fan of. also, the OVA had to be replaced in the end as the OS was hardened to a point where we could not upgrade to a newer feature release.

As I said, it might just have been an issue for that one environment but I still have a preference for manually creating the CommServe and add the hardening myself. It takes longer when creating the CommServe but it should only have to be done once in 5-6 years.

More documentation for hardening the CommServe: Securing the CommServe Computer

Kind regards,

Paul

Hi ​@Paul G ,
Yes, the issue observed in the previous release could have been a one-off occurrence related to hardening. The system is expected to function as intended when hardening is implemented manually.

Thanks both but I’m probably more confused now.

​@Pradeep are you suggesting the latest 11.36 OVA Commvault might not actually work when a Commvault upgrade initiated by Commvault (i.e. a scheduled “install updates”) is needed?

We’re a small environment in Commvault terms so the principle of the OVA is perfect.

Hi ​@Paul Hutchings,

Just go ahead with deployment of the Windows OVA. That will work fine for your small environment.

As Pradeep suggested, my experiences are not representative for all OVA deployments so just ignore it. Sorry that they confused you.

Kind regards,

Paul