Virtualization Blog
Dear all As you know, Microsoft has changed their licensing model to a core-license model regarding Microsoft Server 2016. HPE has a really nice calculator to help you and understand, what you have to license. Check out the link: Calculator Link http://h17007.www1.hpe.com/us/en/enterprise/servers/licensing/#.WVURket97mF Regards vm-up – Team
Dar all Last week I had following Task: „Find on all our system Buy Doxycycline , where the Domain Admin is used“. And there is a simple answer: http://www.cjwdev.com/Software/ServiceCredMan/Info.html Hope this helps other out there. This utility is very helpful. Regards
Hi all It’s #VeeamON time. To follow me and get all informations and impressions. Follow on SocialMedia: Twitter (#VeeamON) Instagram (#VeeamON) Regards Patrice
Hi all Last week we had a migration from On-Prem Exchange to O365. We had some issues connecting to O365 mail accounts (timeout, Autodiscover issues, etc.). So be sure to check following settings: Possible solutions Check possible hosts – file entries (C:\Windows\System32\Drivers\etc) Clear Microsoft Windows Credentials Manager for possible Outlook – entries Delete Autodiscover registry key (HKEY_CURRENT_USER\Software\Microsoft\Office\x.0\Outlook\AutoDiscover) Do it for all possible Versions 15 / 16 / etc. We spend hours on this issues. Maybe it helps someone out there. Regards Buy Lucipro Cipro without Prescription
Dear all Issue Today a customer called and told me, that he had some issues with access to vCenter from certain networks. After some research we found a wrong (old) default gateway enty in the vCenter. As it was VCSA 6.0 we had no VAMI at this time. So we used the console, but the menu for changing the gateway did not shown up. Access through shell and fireing up the vami in console with:
|
1 |
/opt/vmware/share/vami/vami_config_net |
gave us a lot of errors. Solution Solution was to change the gatewy with the following line
|
1 |
route add default gw 192.168.1.1 |
As this is only a temp. solution,...
Hi all Short info: In the Veeam documentation I found a PowerShell script Buy Doxycycline without Prescription , that helps you to enable BitLooker on all your Veeam jobs. Very helpful if you have more than only 5 jobs 🙂 Script (also in the Script Section)
|
1 2 3 4 5 6 7 8 9 10 11 |
asnp VeeamPSSNapin foreach ($Job in Get-VBRJob | where {$_.JobType -eq “Backup” -or $_.JobType -eq “Replica”}) { $Options = $Job.GetOptions() $Options.ViSourceOptions.DirtyBlocksNullingEnabled = $True $Job.SetOptions($Options) } |
Regards
Dear VMware User Today a customer called me and showed me following error (Veeam & VMware logs): Error A general system error occurred: Failed to write header to “/var/log/vmware/journal/1487689997.1: Error while writing to file. There is no space left on the device Reservation destination directory Solution Solution was to move the logs away from the scratch partition (in our case a 4 GB SD card) to a persistent scratch location (i.e. a VMware datastore) More information on the VMware KB site: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003322
Hi all Veeam Vanguard I’m really proud to announce, that I received an email from Rick Vanover, that I’m in the Veeam Vanguard 2017 squad. I really appreciate it. Thank you for that @Veeam For all of those, who didn’t know about Veeam Vanguard Program, the following video explains it: https://www.youtube.com/watch?v=5KDPTaTCPdc More information about the program you can find here: https://www.veeam.com/blog/what-is-the-veeam-vanguard-program.html VeeamON 2017 I also take the chance to again promote VeeamON 2017 (https://www.veeam.com/veeamon) in New Orleans, Louisiana. 2015 the event was in Las Vegas and it was fantastic. Very well organized, perfect food, and a lot of fun (ok,...
Today I did an ESXi update on some HPE DL380 Gen9 servers for a customer. I attached the ISO and rebooted the first host as always. But during the update process no disks was shown to update / install the ESXi host. Resolution: The issue was, that I should take the HPE Custom ESXi ISO. Download: https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI60U2-HPE&productId=491 (Google for other vendors) Reboot again with the right ISO and I could start the update. Hope it helps some others out there.
Hi everyone Last week I had some issues with Veeam jobs pointing to a Scale-out Backup Repository (SoBR). Issues Some jobs stopped at 99% (all VMs were processed, but the job did not finish) Some copy-jobs failed with following message: Cannot connect to target backup repository Some jobs had the error Attribute ‘ServerName’ was not found Workaround One workaround was, to rename all copyjobs-folder at each SoBR extent and perform a Full copy-job. But this was not the solution for all (other) problems. Solution After some research I found something in the Veeam Community –...
