Recently I posted how to run the Ubiquiti UniFi Controller in the cloud using services like Linode, Vultr, or DigitalOcean. However, a few people has asked if I could post instructions on how to run the UniFi controller in Docker, similar how I have CrashPlan running in Docker.
I was recently upgrading a VMware environment from vCenter Server Update 3b to Update 3e and during the scheduled change I had also planned on upgrading VMware Update Manager to Update 3e and ran into the following error:
VMware Workstation unrecoverable error: (vthread-3)
GetProcAddress: Failed to resolve ENGINE)load_aesni: 127
You can request support.
Looking for a possible solution at the VMware Knowledge Base came back with no results and to error message wasn’t overly useful either with “VMware Workstation unrecoverable error: (vthread-3)” as Workstation wasn’t installed on this server.
Earlier this month NAKIVO released version 6.1 of their Backup and Replication application which only adds to their popular 6.0 version adding features like Microsoft Exchange instant object recovery and log truncation as well as other features. As part of the VMware vExpert program NAKIVO has given me a NFR license to try NAKIVO Backup and Replication v6.1 in my home lab and I want to share my initial thoughts about this new version that I’ve had running for the last couple weeks.
Recently I replaced my wireless router, an Asus RT-AC66U, with an Ubiquiti EdgeRouter X router and Ubiquiti UAP-AC-LR access point. Both of which are a HUGE step up over traditional consumer wireless routers.
The Ubiquiti access points use software called the Ubiquiti UniFi controller to configure and control the access points which can be installed locally or in the cloud – allowing you to manage the access points no matter where they are located.
To automate the install process, I created a simple script to deploy the Ubiquiti UniFi Controller in the cloud on a Ubuntu server, and have also tested the script on three popular VPS providers: Linode, Vultr, and DigitalOcean – all three worked perfectly!
Altaro VM Backup is a company who offers a backup solution for small to medium sized businesses and have been around for a while that started out offering backup software for Hyper-V, but has now expanded to VMware as well. Altaro asked if I would be interested in trying for free as part of the vExpert program in my home lab.
I help out a few small companies here in town so having another backup solution to possibly suggest certainly wouldn’t hurt, so I decided to give it a try and below are my steps to setting it up and thoughts about the software so far.
Microsoft recently pushed out a “Convenience Update“, a sort of rollup of rollups for Windows Server 2008 R2 SP1 and Windows 7 machines. This “Convenience Update” however comes with an incompatibility issue with VMware virtual machines that are using VMXNet3 network adapters, which causes the network to become unresponsive.
I’ve mentioned how to create a bootable VMware ESXi installer USB flash drive in an older post, but wanted to detail the steps I use to create an ESXi bootable install drive.
Creating a bootable flash drive is very useful for machines without a CD-Rom or remote access like an iDRAC where you can virtually mount an ISO image – such as the Intel NUC.
The process is very easy with just one tool needed, Rufus – if you don’t already have it go ahead and download it now!
Admittedly the process in the old guide wasn’t always roses. Crashplan would push out an update and that update would, at times, break the Synology Crashplan client from PC Load Letter and backups would stop running for a couple days – maybe a week. Patters being the awesome guy he is, usually updated his Synology Crashplan package quickly and all was good again.
Then last year in DSM 5.2, Synology added support for Docker which opened up the possibility to run all sorts of software in a virtual container running on your Synology NAS. One such software being Crashplan and below I’m going to show how I now have Crashplan running in Docker on my Synology DS1815+ NAS!
We’ve ran into an issue trying to get VMware SRM and SRA 184.108.40.206 along with EMC Recoverpoint 4.1.2 to communicate with one another and would receive this error in SRM:
SRA command discoverArrays failed. Failed opening session for user to site mgmt IP.
Please see server logs for further details.
After some digging around a bit and talking with the Storage Team and EMC we found out that this is due to the SRA’s using HTTP by default and Recoverpoint 4.1.2 does not accept HTTP, but instead only accepts HTTPS or port 443. The steps below is how to get everything to default HTTPS and then communication will resume.