• Resource Misallocation

Many administrators do a common mistake: Hyper-V virtual hard disks (VHDXs) for everything.
VHDX, despite being beneficial in many ways, are mostly wasteful.

• Imbalance of Memory and CPUs

Microsoft recommends a maximum of 12 virtual CPUs per physical core. Keeping this in mind, it is necessary to have a balance between CPUs and RAM.  Using a Performance monitor tracing helps you get that balance so that you do not run out of memory before you run out CPU.

• Blindly Accepting VM Configuration Defaults

Most people often overlook the options while configuring the VM and end up accepting the default settings. In reality, you only get to have one vCPU in the default settings and the Virtual memory is set to 1 TB (you pretty much would never need this much of Virtual memory, honestly!). For guest OS XP/ Server 2003, the requirement automatically becomes at least 2 vCPUs. By accepting default configurations, you might end up risking the distribution of resource allocation by the host.

• Imbalance of SSD and Spinning Disks

For optimal Hyper-V server manager settings one good Hyper-V Management practice is to have a balance between SSD and spinning Disks via the Hyper-V virtual machine manager. In ideal case, an SSD churns the spinning disk while the Hyper-V server is installed directly over it. So, the SSD’s fast speed must be leveraged on to work with the VM data.

• Not Joining a Domain

Joining a Domain is another sane thing to do for better Hyper-V Management.  Generally Hyper-V hosts should never reside on a perimeter network. Leaving a host in a work-group makes it vulnerable to attacks. An attacker can penetrate and get unauthorized access to all VHDX files.

ALSO READ
Hyper-V vs. VMware vSphere | A Comparison

The golden Tip: Don’t Avoid PowerShell

It is without a doubt that PowerShell requires some effort to learn, however, once administrators get their hands on the awesome tool, they can easily manage multiple tasks in parallel. PowerShell allows the users to get access on the following:

• .NET Framework API
• Windows Management Instrumentation
• Windows Component Object Model
• Command Prompt
• PowerShell Commands

MachPanel automation module for Microsoft Hyper-V – VPS Control Panel

Experience virtualization of virtualization arena of Public, Private and Hybrid clouds like never before. MachPanel brings to you the latest Microsoft Windows 2019/2016/2012 R2 Hyper-V automation solution carefully catered to address them modern needs of virtualization and managing virtualized environments.  With MachPanel, you can offer Virtual Private Servers (VPS) and Virtualization solution enabling Web Hosts to automate Hyper-V based VPS provisioning, management via next-gen feature rich web-based control panel.

Stay ahead of others by adopting MachPanel automation module for Microsoft Hyper-V – VPS Control Panel to empower your cloud business.

Lets TalkRequest a Demo

The post Microsoft Hyper-V Management | 5 Mistakes You Must Avoid appeared first on MachSol Blog.

In SharePoint Online, If any of your Site Collections deleted accidentally Or intentionally and later on for some reasons you need to recover your deleted site even list or list items from SharePoint. Don’t worry, it is still possible to recover all your data. Removed sites moved to SharePoint Tenant Admin recycle bin and from where it can be recovered or can be deleted permanently.

The default retention period for any item is 93 days.

Sites deleted will remain in the SharePoint Tenant Admin Center’s recycle bin for 30 days. And from here you can recover your removed site collection.

After 30 days site collections will be removed from Admin Center Recycle Bin and can only be recovered Using PowerShell!

Recover SharePoint Online Site Collection using PowerShell.

In order to run cmdlet against SharePoint online you need to install “SharePoint Online Management Shell” and then use Connect-SPOService to gain access to your SharePoint online space through PS.

Once done, You can view deleted site collections and see how many days are left before each site collection is permanently deleted.

Run the below command to view the deleted site collections.

Get-SPODeletedSite

To restore a site collection, run the following command

Restore-SPODeletedSite -Identity https://Site-Collection-URL

NOTE : User running the above cmdlet must be a SharePoint Online global administrator and a site collection administrator for the deleted site collections.

Author : Jameel

…

For product & sales related queries, please email us at sales@machsol.com

The post Recover Deleted Site Collections In Microsoft SharePoint Online appeared first on MachSol Blog.