A while back I posted about Service Pack 2 for Backup Exec 2012 and Service Pack 3 for Backup Exec 2010 being in beta. Well, testing is over and the day has come. Both service packs have been released. And this is what they include.[Read more…] about Backup Exec 2010/2012 Service Packs released
The number of heartbeat datastores for host is 1, which is less than required: 2
The number of heartbeat datastores for host is 0, which is less than required: 2
I ran into these errors recently after configuring High Availability on a brand new VMware ESXi 5.1 cluster. I had used SanDisk cards for my ESXi operating system and planned to use a LeftHand Virtual SAN Appliance with only one LUN so I was only going to ever have one shared datastore. I knew I would have to squelch this error right away.[Read more…] about The number of heartbeat datastores for host is 1, which is less than required: 2
V-79-57344-65072 – The connection to target system has been lost. Backup set canceled.
I ran into this error recently at one of my clients with their new Backup Exec 2012 implementation. The jobs would sometimes work, but mostly they would fail with the error above. They would also fail at seemingly random byte counts. The implementation was backing up two servers. One of the servers was also the media server and this local backup always succeeded as expected and without incident. The other server, the one that was often failing, was the one with the remote agent.
This made me quickly look towards the network. As a test, I kicked off the problematic backup and monitored the network bandwidth usage in Task Manager on both servers. I also had a continuous ping going between the two servers. The first thing that became apparent was that the network bandwidth (100Mb switch) was completely saturated during the backup. Both servers continually reported a steady hold at 100% network utilization.
Then it happened. At first, I saw the continuous ping start to fail between the two servers. Then I noticed the network links as being reported down on both servers. I could only assume at this point the switch that connected these two servers together was having problems. I logged into the switch and checked the uptime. Lo and behold the switches uptime was just a couple of minutes. I repeated this test a few more times and even tried different switch ports and network cables. Same result every time. The switch kept rebooting. I could only assume this older switch could not handle the constant 100% network load.[Read more…] about Backup Exec 2012 Jobs Keep Losing Connectivity To Remote Agents
Storage system [FOM NAME] ([IP ADDRESS]) did not join the management group [MANAGEMENT GROUP NAME].
The required directory /etc/lefthand/data is not mounted. Please restore OS using recovery media.
I ran into this error recently while trying to add an HP LeftHand Failover Manager (running on Hyper-V) to a management group with two HP LeftHand VSAs (running on VMware ESXi 5.1). We were using SAN iQ 10.5.
I tried blowing the FOM away multiple times and reinstalling from scratch but this did not help. I ended up calling HP and this is a known issue that they are working on. There is no patch yet but there is a workaround.[Read more…] about Can’t join an HP LeftHand FailOver Manager to Management Group
I was recently building a VMware ESXi multi-host environment with a LeftHand Virtual SAN and I needed 6 Port Groups for my design. I already had one pre-existing Port Group that was a 2GB uplink to my Layer 3 switch.
Everything was going great until I tried to create Port Group number 7. This seemed odd to me as I knew my IOS version should at least support 128 Port Channel Groups.
After some digging, I discovered this 2960G only supports 6 Port Channel Groups. This was unfortunate but not a deal-breaker. I knew I would not be using Vmotion very often on this cluster so I let that run on a single Gigabit Ethernet port. This allowed me to re-architect my solution for only 4 Port Channel Groups.
Just thought I’d pass this one along. You don’t often see switches restricted to this few port-groups.
So, I finally got to set up my first Gen8 server. It is a ProLiant DL360e Gen8. Two actually. At first, I was very happy with all the new advancements. No more searching for a SmartStart CD you say! Brilliant! No more confusion on SmartStart version compatibility? Wicked! (Yes, there is a VERY fine line of SmartStart CD’s that will support both a ProLiant DL360 G4p and putting Server 2008 R2 on it – I like to live dangerously!). So, as many of you already know Intelligent Provisioning replaced SmartStart CDs. The cool part is, you just boot right into it. Its an option – F10 at POST. Neat huh? And it looks so sharp too. (Check the image below)
They have this neat feature called Firmware Update that will directly connect to HP.com (or a local update server) and get all your firmware updates for you. Very neat. Especially useful if we are using an OS like VMware ESXi. So I configured the network settings on both my servers and got the error in the screenshot below.
I checked my settings a dozen times on both servers, tried different IPs, different NIC ports on the server and sadly no luck. It just wouldn’t connect. I called HP and the first tech has me update from v1.30 to v1.40.88. Sadly this did not help. I called back (different tech this time) and they told me this is a known issue with certain servers running certain system firmware versions and that they are working on it.
Insert sad face. 🙁
This seems like a really cool feature. I just wish I could test it. Until then, I will be going back to downloading the bootable Service Pack for ProLiant DVD.