-
- Expert
- Posts: 203
- Liked: 12 times
- Joined: Dec 04, 2012 2:18 pm
- Full Name: Both
- Contact:
Upgrading to V8 this weekend - question
I plan on upgrading a customer to V8 from 6.5 this weekend, one of their VM's is affected by the CBT bug. My plan is, in this order.
Perform the upgrade
Run the script against the affected VM (CBT)
Then run a backup on affected VM
Is that correct or I need to go into the datastore and remove the file for the affected VM that is created due to the CBT bug or will that backup in V8 take care of that?
Also, I have a replication job for the same affected VM, do I simply delete the replica after the V8 backup has completed and restart the replica from scratch?
Thanks
Perform the upgrade
Run the script against the affected VM (CBT)
Then run a backup on affected VM
Is that correct or I need to go into the datastore and remove the file for the affected VM that is created due to the CBT bug or will that backup in V8 take care of that?
Also, I have a replication job for the same affected VM, do I simply delete the replica after the V8 backup has completed and restart the replica from scratch?
Thanks
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Upgrading to V8 this weekend - question
Correct.Is that correct or I need to go into the datastore and remove the file for the affected VM that is created due to the CBT bug or will that backup in V8 take care of that?
CBT reset should be enough, no need to start replication jobs from scratch.Also, I have a replication job for the same affected VM, do I simply delete the replica after the V8 backup has completed and restart the replica from scratch?
Thanks.
-
- Expert
- Posts: 203
- Liked: 12 times
- Joined: Dec 04, 2012 2:18 pm
- Full Name: Both
- Contact:
Re: Upgrading to V8 this weekend - question
So I need to go into the data store to delete the file or not?
Are you sure about the replication? I'd hate to continue replicating the job after the CBT reset and then have a disaster whereby I need to spin up the replicated machine to find its corrupt?
Are you sure about the replication? I'd hate to continue replicating the job after the CBT reset and then have a disaster whereby I need to spin up the replicated machine to find its corrupt?
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Upgrading to V8 this weekend - question
You can either do this or not, depends on the script you're going to run. Please check this topic for more info > how to fix CBT issue without powering prod VM ?ashman70 wrote:So I need to go into the data store to delete the file or not?
Yes, there is no need to do full replication cycle. After you reset CBT, Veeam backup server will calculate digests on source and target ends to make sure target VM is not affected by this VMware bug.ashman70 wrote:Are you sure about the replication? I'd hate to continue replicating the job after the CBT reset and then have a disaster whereby I need to spin up the replicated machine to find its corrupt?
-
- Expert
- Posts: 203
- Liked: 12 times
- Joined: Dec 04, 2012 2:18 pm
- Full Name: Both
- Contact:
Re: Upgrading to V8 this weekend - question
I am not sure I understand the scripts now, seems there are many variables that need to be changed depending on the environment.
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Upgrading to V8 this weekend - question
If you are not sure how to use these scripts, then you can reset CBT flag yourself via this KB article (http://www.veeam.com/kb1113). In this case CTK files should be indeed deleted manually.
-
- Expert
- Posts: 203
- Liked: 12 times
- Joined: Dec 04, 2012 2:18 pm
- Full Name: Both
- Contact:
Re: Upgrading to V8 this weekend - question
Thanks I did and followed the KB article.
-
- Expert
- Posts: 203
- Liked: 12 times
- Joined: Dec 04, 2012 2:18 pm
- Full Name: Both
- Contact:
Re: Upgrading to V8 this weekend - question
FYI the upgrade was very smooth, no issues at all.
-
- Product Manager
- Posts: 20413
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Upgrading to V8 this weekend - question
Thank you for coming back and confirming that the mentioned approach worked for you; highly appreciated!
Who is online
Users browsing this forum: No registered users and 40 guests