cancel
Showing results for 
Search instead for 
Did you mean: 

[14.11.2019 00:16:40] Info [CSnapReplicaVmxMerger] Removing scsi from config 'VMHM01_replica'. Current version '4', minimal needed '7' [14.11.2019 00:16:40] Info [VmxFile] Removing Scsi. [14.11.2019 00:16:40] Info [VmxFi

[14.11.2019 00:16:40] Info [CSnapReplicaVmxMerger] Removing scsi from config 'VMHM01_replica'. Current version '4', minimal needed '7' [14.11.2019 00:16:40] Info [VmxFile] Removing Scsi. [14.11.2019 00:16:40] Info [VmxFi

cstang
New Contributor

From Veeam Support

As you can see the replication job creates a brand new virtual disk for that affected machine.

Base on that I would suggest as follow:

 

1. To get everything back on track I would suggest to upgrade to at least version 7. Just so you are aware upgrading them will not mean that cleanup will be done automatically. Replica vmdk's should be cleaned up manually.

 

2. If that does not help please remove the affected VM out from the job and create a brand new test job just for that VM to try out.

1 REPLY 1

samantha_lynn
Esteemed Contributor III

Can you elaborate on what your question is? What type of HiveManager are you trying to deploy? What are the resources available on the server you are using?

GTM-P2G8KFN