Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Assets in IT that Must Not be Virtualized

DZone's Guide to

Assets in IT that Must Not be Virtualized

·
Free Resource

We are aware of the advantages that virtualization offers in the IT landscape. Yet, there remain a few assets, which ought not to be virtualized.

Although virtualization helps organizations cut costs, allows systems to communicate more efficiently, uses resources better, and improves administrative competencies, we should not lose sight of the fact that what an organization intends to achieve can only be fulfilled if IT departments are still in place.

Among the resources that should not be virtualized include some programs that still need an attached hardware device in order to function. This device is required for the program to be licensed so that it cannot be stolen. For example, we need firewalls that make use of application-specific integrated circuits (ASICs), which cannot be virtualized.

It is not advisable to virtualize a system or an application that consumes RAM usage and needs multiple CPUs. For instance, these apps include database and video streaming as all these are physical devices.

We cannot, obviously, virtualize apps or OSs that have licenses or support agreements. This is because you cannot request for support when something goes wrong, according to the agreement.

Mission critical applications that are yet to be tested also should not feature in the virtualization list.

Also included in that list would be applications that depend on your physical environment as a virtual device and its host are prone to failure at any point of time.

Applications that depend on your virtual environment must not be virtualized as you are putting them at a massive risk in case downtime strikes owing to factors like power outages, which are beyond our control.

Any system with secure data, which should not be shared with others, should not be virtualized if you do not want security risks. Permissions may be created on virtual machines to deny others the capability to control them. But if those users possess the ability to control the host systems, they can bypass your controls.

Virtualization should be avoided for any system or application on which synchronization is a must.

Desktop PCs that are functioning well should also not be virtualized.

It is harmful to virtualize certain old physical devices that have archival information that can be duplicated.

To be included in the list also are physical systems that host the virtual devices because one needs to know the consequences and variations between what is needed by the hosts and what needs to duplicated. 

Topics:

Published at DZone with permission of Ravi Namboori. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}