Absolutely a swing host would be a good choice there Joerg, but he did mention its not possible to interconnect storage. So there must be some reason he's got a blocker there, hence not recommending it. Would be far easier if he had that of course. Could always do a V2V migration as well with VMware vSphere Converter agent. Install on the OS and let it rip. Might have to find an older download to do that though with some of his older VMs. Would be nice if Veeam would have links to their older downloads with a giant red disclaimer that these should never be used as they're unsupported - one of ..read more

I recently upgraded to V12 because, well, I had to. I put it off for awhile hoping all issues would be cleared by now. My jobs to my cloud provider now crawl. I do still have a V11 guest setup that does backups for one of our legacy apps. It was not pointed to my cloud provider previously. This morning I just pointed it and, yeah from the screenshots below it would appear that old issue in V12 has re-appeared. I do have a ticket open (TAC 07239898) but we got head scratching going on. TAC says its the network thats the bottleneck according to the logs. It seems like a false positive to me. The ..read more

I do a lot of those "migration" and because we have a lot of iSCSI environments the plan A is always to have at least ONE ESXi Host which is connected to the old and new Storage and use this one as a migration point. When having iSCSI i never found a real door stopper... yes sometimes you need to ignore and violate "Best practices" like having only one Link/Path, Binding or Non-Binding swISCSI config within ESXi or what ever but thats just for a short peroid of time. Even when dealing with old Blade chassis i cant think what maybe can impossible. Regards, Joerg Statistics: Posted by Origin 20 ..read more

Thanks Fabian, Sure, understood.. Will go through these links as well.. Statistics: Posted by tanjum — Thu May 02, 2024 8:41 am ..read more

Hello tanjum Please start using exact names when you ask about "storage". It would make it easier for any future reader of this topic. Suggestion: - production storage - backup storage A "network" or "virtual appliance" proxy doesn't require access to the "production storage" subnet. But the proxy must be able to connect to the server with the repository or gateway role. You can use different subnets for all Veeam components and open the necessary ports in the firewall: https://helpcenter.veeam.com/docs/backu ... ml?ver=120 A design recommendation for subnet segmentation is in our user guid ..read more

Hi again, I have gone through the below 4 links to get clarification on what subnet should the proxy be in, but could not find an answer for this. https://bp.veeam.com/vbr/3_Build_struct ... p_proxies/ https://helpcenter.veeam.com/docs/backu ... ml?ver=120 https://helpcenter.veeam.com/docs/backu ... ml?ver=120 https://helpcenter.veeam.com/docs/backu ... ml?ver=120 VM Subnet - 10.21.30.0/24 - 1Gbps link Storage Subnet 10.21.40.0/24 - 10Gbps link So in this case should the proxy be in the VM subnet, or Storage ? Or should the VMs be moved to traverse over the 10Gbps link ? Thank You Sta ..read more

Hello Fabian, Thanks for replying but I'm also wondering why it sticks to that 1 proxy whilst there are 4 other are available. As mentioned in the case even after pressing retry it only finishes the job with that 1 proxy. Statistics: Posted by nvdwansem — Thu May 02, 2024 5:29 am ..read more

true. OS is a thing, too. Statistics: Posted by karsten123 — Thu May 02, 2024 3:39 am ..read more

Man, I couldn't even imagine the pain and suffering they would have to face to jump through multiple upgrades and hardware refreshes to get to a vSphere 8 environment. Can it be done? Sure. Would you spend more time doing that then just migrating? Probably. Depending on the scale of the environment, it might even be a better choice to simply build new VMs on the new environment and migrate services and data to those. Kill two birds with one stone - get a badly needed VMware refresh along with a badly needed OS refresh. Statistics: Posted by tyler.jurgens — Wed May 01, 2024 10:28 pm ..read more

Well, in this case here is what you can do: 1. Deploy a new Linux VM in the cloud 2. Install VAL onto the VM 3. Enable recovery UI by adding the following line to /etc/veeam/veeam.ini under the [recoveryui] section enableOnLiveSystem = 1 4. Attach as many extra disks to the new VM as your original VM had 5. run 'veeamconfig recoveryui' to start Veeam Recovery UI 6. Follow these steps: https://helpcenter.veeam.com/docs/agent ... tml?ver=60 Make sure that you restore to disks that are not used by the current system where you start the recovery UI from. Depending on the AliCloud hypervisor ..read more