VMware vShield is part of the vCloud Networking and Security (vCNS) suite. Its latest version 5.5 has reached EOGS (end of general support) in September 2016 and has been replaced by NSX for vSphere.
We still see quite a lot of vShield installations in productive environments. Mainly used for agentless guest introspection together with security solutions like Trendmicro DeepSecurity, McAfee Move or others. Now that many customers consider migrating from vSphere 6.0 to vSphere 6.5, they have to face the fact that vShield is no longer supported from vSphere 6.5 onwards. And it is crucial to take product compatibility into account. There is a relationship between different vSphere, NSX and security product versions.
Veeam Backup and Replication has a deep integration into NetApp hardware since version 8. Yet there is still no NAS Backup Support for SMB and NFS Shares (v10 Feature or 9.5 Ux). The question arises how to back up NAS data from older NetApp boxes, when the ONTAP version is simply too old for Veeam integration and you can’t utilize NDMP, NFS or SMB protocol for direct NAS backup?
I will outline a real-life scenario where a customer has an old Netapp (7+ years old) with single controller holding very important data (I will not comment on that). 🙂
How can we integrate these datasets into an existing Veeam infrastructure?
I’ve created a cheap and dirty(?) method how to synchronize the content of that old Netapp box with a Linux VM which can be easily backed up by Veeam. The content of the Netapp NFS share will be replicated into a Linux VM (1st copy), backed up to disk by Veeam (2nd copy) and archived to tape (3rd copy, 2nd media type) which is then kept in a fireproof safe (offsite). It was possible to fulfill the 3-2-1 rule (3 copies, 2 types of media, 1 copy offsite).
Good morning Chicago. Tomorrow VeeamON 2018 will take place here at McCormick Convention Center close to Lake Michigan. Staff has been busy the whole weekend to get everything set for the opening on Monday. I had a short glimpse at the exhibition hall yesterday, where people were laying out carpet and setting up booths and banners. I’m curious how it will look like tomorrow. Stay tuned for updates.
Today I’m writing about a use case, which is not very popular amongst IT professionals. Troubleshooting by parsing system logs. Sounds attractive as a dental surgery.
Almost any system and any component logs events, warnings and errors into some kind of internal log. Emphasis is on any and internal, because that’s part of the problem. Log information isn’t usually easy accessible. And once you’ve copied all logs to a common location, you need to scroll through it by a text editor. This is cumbersome and tricky. If you – for example – have to align events from a server with events from a switch, you’ll need multiple steps to achieve it. A very time-consuming procedure. If you have bad luck (Murphy says, you will..), one of the components is unavailable, because an error occurred. No log – no analysis. Continue reading “Increase efficiency with vRealize Log Insight”
First aid if VCSA root partition turns out to be too small
I recent times I frequently see vCenter server appliances (VCSA), whose root partitions ran out of free space. As a result services are unable to start after reboot. There are some tricks to free some space on root but on the long run you should increase the partition size.
Sounds simple – but it’s quite tricky and a bit dangerous. Don’t try this at home! 😉