Vembu BDR Upgrade – Part02
In the previous post, we discussed the reasons why we should upgrade Vembu Backup and Replication Suite. I hope you found my post useful. We will continue to our next part of the upgrade. In this post, we will do what is referred to and commonly ignored Current state analysis. This the most important step while planning an upgrade. Be it Vembu BDR suite or anything.
What is Current State Analysis and what is covers?
It always starts with Why 🙂
So why are we doing this? Our goals and purpose are covered In the previous post.
What is involved in the upgrade?
Which components of Vembu BDR suite are implemented and how are they interconnected.
At which version Vembu BDR is at? and to which version we have to upgrade. The version is already decided for us. It is referred to as Future state requirements.
Are there any risks associated with this upgrade. This could be identified only after you finish Currents state analysis. I have covered this at the end of this post.
What is the time frame available for the upgrade and the resource availability and stakeholders?
The communication plan.
Components involved in Vembu BDR?
The most important thing to check the Vembu BDR deployment model.
Simple Deployment – Only recommended for the evaluation purpose.
Distributed Deployment – Recommended for production
Following are the minimum components involved in Vembu BDR.
Vembu BDR backup server — The windows operating system on which BDR server is supported. So if you are planning to upgrade the OS you check if your OS is compatible with it. I would always recommend at the minimum WS2016. Installation path where Vembu is installed. It is recommended to install on a drive different than Operating system for scalability and to backup configuration. Sufficient space is available on the drive where PostgreSQL is installed.
Vembu VMBackup client — you need this when are backing up the physical server as well. So the upgrading of the client is also essential in this case. Are all the clients in the list of the Supported OS. Following is not important but strongly recommended to patch the Windows version to the latest level.
Backup Storage Repository — The role is installed on a dedicated server and has sufficient space free. It is recommended to have at least 20% free space any point in time.
Source ESXi host — here the version decides up to which level we can upgrade the suite.
Target ESXi host — if you have configured replication.
The backup job schedule — This directly influence when you can upgrade the backup server.
Most of the installation of Vembu does not need any modification from default settings e.g. Ports, Username. But it is strongly recommended to change the default user name. At this stage, it is a good idea to see all credentials are handy and working. If you have secure Vembu servers, please review the firewall ports and firewall rules. I have covered that in details here.
The monitoring environment is impacted. Normally not unless you are upgrading monitoring system as well. For example in case you are using Solarwinds monitoring system then any changes in OS side remains unchanged.
Is your Technical support valid or it is expired. This is also a very important point to remember.
The list is bigger but it can get a lot bigger. However, the idea is simple, plan, plan and plan. The more time you spend in this stage, the less time you will need during installation and troubleshooting post installation. Always keep a window for Rollback, a window for troubleshooting. Things never go as we think or plan.
Upgrade considerations and Upgrade Order
In order to upgrade to Vembu BDR 4.0, you should be at the minimum Vembu BDR Edition v3.9. So, if you are below this version you have to go through multiple upgrade steps. This is not hard but might need to review from the implementation order and the duration aspect.
Do we have Vembu BDS in offsite, then we must upgrade that server first. The procedure to upgrade is covered in the upcoming posts.
Then upgrade the Vembu BDR site. This is the main server.
Now comes the Vembu Backup proxy server in the end. This cannot be automatically pushed.
The output of Current State analysis could be
Key findings, consideration, and recommendations
Gaps found in the environment
Procedure and Approach to fix the gaps
Duration and date finalization for the upgrade
Upgrade order and the Rollback plan
Any other changes planned in the same duration
Teams involved especially on the lines
I have created the following Current State Analysis chart. I think it would be good to keep handy.
Hope you like this post. It is about planning and planning. You might not like at first instance the word ‘Plan’ but it is cannot be ignored. Now the next blog post is actually about how to and full of screens which will help us to identify the upgrade steps and sections. So stay tuned. If you like the post, press like or provide your comments below.
Again – the previous post is here