modify virtual device node fails replication

[jmerchan]

Hello

We have changed virtual dvice node from SCSI 0:1 and SCSI 0:2 to SCSI 1:0 and SCSI 2:0 adding new virtual disk controllers to the virtual machines

We have try to modify de replication job deleting and adding the virtual machine, selecting disks to include in backup, etc... and nothing

Have we to delete the older replicas?

thanks in advance

[Vitaliy S.]

Hi Jose, what version of Veeam B&R are you running?

[tsightler]

This is probably not a hardware change that we can detect and replicate. Making the change manually won't work because when we start the next replication cycle we always revert the most recent snapshot which effectively reverts all of your changes. My suggestion would be to delete all the snapshots on the target replica, make the changes, and then use replica mapping to restart the replication job.

[jmerchan]

Sorry, replications fails with this message:

15/07/2012 1:16:43 :: Processing configuration Error: Controller with BusNumber 1 was not found

we have Veeam v6.0.0.181

[Vitaliy S.]

Jose, please avoid posting log snippets as it is described when you click New Topic. As to your error message, then I believe Tom's suggestion should fix your problem, so I would give it a try.

[guru_reggie]

Hi guys,

Just wondering how this went..? I have the same issue after adding a 2nd SCSI controller to a VM yesterday.. My backup works fine, but the replication fails with the same error as earlier in the post.. I've removed the snapshots from the replica but still no success.. I'm on B&R 6.5.0.109..

Many Thanks,
Mike...

[chrisdearden]

Hi Mike, after removing the snapshots , did you use the replica mapping feature ? it should avoid the need to send another full over.

[guru_reggie]

Sure did mate.. Get the same error..

[chrisdearden]

and the target VM now has the correct device settings ( and no snapshots ? )

[guru_reggie]

Do I need to manually add in the new SCSI Controller and 3 x disks to the target VM..? Isn't that what Veeam should be doing.?

Snapshots are all removed (my restore points)...

Not sure we should really need to all this manual process just to add some disks to our backups dude...

[chrisdearden]

Adding the volume isn't usually the problem , its adding the additional controller. If you had just changed a disk, it deletes the snapshots manually.

[guru_reggie]

OK - so I just add an additional controller to my replica then.? I'll give it ago...

[guru_reggie]

Seems to be working now Chris - thanks for the help.. A little surprised that Veeam doesn't pick up the 2nd bus tho.. Maybe in v7

Have a great Christmas.!

[chrisdearden]

fair point - I think its because we create a new VMX for the replica rather than copying an existing one

[roelvdw]

Hi
I have changed the disk settings of a VM from IDE to LSI Logic SAS.
But when I wan't to replicate VM after changing disk controller to LSI Logic SAS , i get the error "Controller with BusNumber0 not found"

How to solve this problem?

Kind regards

[DavidReimers]

I've got a replica job running pretty well and it includes the Veeam server itself. In line with the best practice in the FAQ, today I added an additional SCSI (LSI SAS) disk controller to the VM.

However, when the replication job runs, I now get a failure when replicating the Veeam server: "Processing configuration Error: Controller with BusNumber 1 was not found".

I did a little searching and couldn't come up with anything. Do I need to remove the VM from the replication job and re-add it?

Thanks,
Dave

[veremin]

Do I need to remove the VM from the replication job and re-add it?

Consolidate first all existing snapshot on replica VM, then make a corresponding changes there (add a new SCSI device to this VM), and finally put into use replica mapping functionality. Thanks.

[DavidReimers]

In the end I simply removed the VM from the replication job, deleted the replica, and re-added it. All working fine now.

[foggy]

Also the way to go, thanks for updating.