07.11.2019 01:13:53 :: Failed to process VM Windows Server Splunk at 2019-11-07T011353 Error: The name 'Windows Server Splunk' already exists.
This is the only error I can see... where are the log files located for a more detailed analysis? Both drives have been copied acc. to the Action list. I can see the VM on the target datastore with all the files.
Just found out that the system is complaining about different CPU functions on source and target servers... both are HP servers but with slightly diff. CPU sets.
Source has an Intel(R) Xeon(R) CPU E5-2695 v2 @ 2.40GHz, the Target an Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
I'm a bit puzzled why this seems to be a problem for the VM migration?!
Looks like there is an existing machine with the same name on the target. Logs analysis should shed more light on the situation.
We always recommend discussing any technical errors and issues directly with our support team. Our engineers will be happy to share knowledge on logs analysis methodology in addition to providing a solution.
Please note, that when you post about any technical error or issue on the forum you must include a support case ID into your post. According to Veeam Forum Rules, topics missing a support case ID will be eventually removed by forum moderators.
Yes, I know! That's why I was asking WHERE the logs are located... couldn't find the Quick Migration logs under %ProgramData%\Veeam\Backup
Am I looking in the wrong place?
In order to safe time and efforts I rather prepare all the detail in advance for a call...
There seems to be a misunderstanding... I know where the general Veeam logs are... but I would like to know WHICH log file(s) contains the information about the Quick Migration process.
I assumed that there's a stand-alone log for that which does not seem to be the case. I found some infos in the SVc.VeeamBackup.log but not the failure reason...
Sending ALL logs seems a real waste of time and bandwidth... the system is quite difficult to reach and data transfer a hassle. But I'll jump through the hoops...
Because this was the second try of the Quick Migration I hoped to find the REAL cause in the logs... the error " Error: The name 'Windows Server Splunk' already exists. " points to a stalled first try... but I haven't got the error for that. So I'll leave that to the poor tech team to sift through the logs.
Hi Oleg... thanks to wishr (Fedor) I uploaded the wrong logs, wasted time and efforts of the Veeam team and me AND had to go back and extract the right logs again with looking incompetent in face of the customer.
That's exactly NOT the way to operate. Fedor, if you don't know the answer, don't post something wrong. This was really UNhelpful...
I appreciate your feedback, but it feels like there is some misunderstanding.
The KB article I linked before includes a list of directories containing logs required for analysis. This list includes the folder containing Quick Migration logs and logs of other jobs as well. How it could be possible that you've uploaded wrong logs?
In any way, when you'd like to get a solution to any technical issue ASAP and in order to simply save your time, you should contact our technical support team and raise a support case in the first place, as requested when you click the "New Topic" button.