Commvault Commserve live sync Implementation
HTML-код
- Опубликовано: 19 авг 2024
- This video explain how to deploy commserve live sync. It require you to go through CVfailover video first and then go through this video.
Link of Multi instancing:
documentation....
Great stuff Ramveer. You are rocking always !!!...
thank you for the video..what's about the new Auto Recovery ,please?
Nice Video, But you did not corrupt the DDB. This is the normal operation. After failing over the CommServer, DDB will go to maintenance mode and it will resync with CommServer database. DDB resync will take some time based on the prune record that has to be synced with CS DB.
Hi girish
Thank you for your words. But I actually did corrupt my ddb. I cut that part in video.
@@CVBackupMasterMinds Ohh okay.. Great video and appreciate your effort to make this video..
Thankyou
Why did you stopped uploading tutorials ..?
Hi
Will be uploading soon
@@CVBackupMasterMinds Thanks . Can you guide us Commserve Cluster configuration implementation.
Hi,
Can you please come up with major troubleshootings videos as well facing in db backup and vm backup.
Thank you for a superb session!
I've the following questions in mind, can you clarify?
1. You somewhere mentioned that the DNS entry will be automatically updated to resolve the DRCV upon failover. But it did not change, you manually changed it to make the backup work. Is there a way for the DNS to automatically resolve DRCV? as it is not possible for everyone to do this DNS updates.
2. While configuring LiveSync, you have talked about the monitoring interval (under Advanced) as 5 mins, but you did not specify how we setup the Witness servers? Only then the failover can happen automatically!
Correct me if I mislead. Appreciate your response.
Also please speak on the Multi Instancing registry entry updates.
Hi Ramveer, i m hving a doubt here.
1. Is it mandate to the prod client name to be cvfloat in the instance 1?
2. why we are installing the cvfailover as multi instance? can't we perform this with instance 1?
Hi satyajit
1) concept was to keep same commcell name on both commserve so that name management process can be avoided at the time of failover. You can use cvfloat or any other name. But if you want to use different commcell name then at dr time you have to perform name management operation which can be time consuming
2) cvfailover or live sync is actually the process of backup and restore (this is how it sync DBs), so dr commserve has commserve package installed (instance 1) which can’t report to any other commserve. Therefore if i want to restore anything on dr commserve i have to make sure this server report as a client to primary commserve. Therefore I installed second instance on dr commserve and make it report to primary commserve.
For any query write us to ramveer2090@gmail.com
@@CVBackupMasterMinds
Hi ramveer,
If in case we have given two different names for both commservers.
Instead of changing the commserver name on each client, can we add a new entry in DNS with the dr commserver name.
In this case total 4 entries will be there in DNS.
cs1 client name - CS1 IP
cs1 hostname - CS1 IP
cs2 client name - CS2 IP
cs2 hostname - CS2 IP
Hi Ramveer,
How can I Contact you to get the complete course. Please let me know.
Commvault 11.19 has new feature called "Configuring Multiple CommServe Hostnames for Disaster Recovery" which is different from using "CommServe Floatrting Name". This is actually a better method. Cna you do a demo for the new method? documentation.commvault.com/commvault/v11_sp19/article?p=122417.htm
Hi Ramveer,
Could we initiate fail-over on 2nd instance process manager of primary Commserve instead of going to dr commserve process manager.
Yes you can if its still reachable
@@CVBackupMasterMinds thank you :)