Backup does not always mean virtualization, but sometimes it means reducing the number of servers required by an organization through the optimal use of server resources. In order to do this, we also need to make a preliminary introduction in this section. Before doing anything, you need to determine what consolidation is appropriate for your network. For example, determine whether you intend to install multiple Roles or Servers on each server. For example, if you run a greater number of services on each server, that server will be down due to the load. The necessary steps to do this are:
• Specify the scope of virtualization
• Provide a list of workloads
• Determine how to backup and set up Fault Tolerance
• Determine requirements that have a specified work load.
Specify the scope of virtualization
The first step in designing the Consolidation strategy is to determine the scope of the project. For example, virtualization of the whole data center can be a one-to-one risk, each of which may require the installation of virtualization hardware, which will increase the initial cost of the project.
List of workloads
The preparation of a workload list means determining what programs are currently deployed, as well as determining where they are and how they use what version of the operating system. Estimating the resources required for these programs and determining the manager or person responsible for handling this program is one of the vehicles to be included on this list. The compatibility of these programs with each other as well as the ability to virtualize them is another point that should be addressed at this stage. If the program does not work in virtual mode, it should be removed from the Consolidation strategy. The manufacturer or the Licenses may be subject to this non-incompatibility from being in the virtual environment.
Determine the necessary resources
Determining the resources needed to workload is one of the most important issues when you create a workload list. You must first measure the resources that your network uses physically. Then add some value to ensure that it does not suddenly reach its ceiling when it enters the virtual mode. You can use three methods to estimate resources:
1-Use a tool called the Microsoft Assessment and Planning Toolkit that can list the resources needed to virtualize the current physical environment. This tool is free. The output of this program is displayed in Excel.
2. Use System Center Virtual Management to install Agent on the server that you want to analyze. You must pay for the license to use this program. The output of this program is graphically.
3. You can manually run your own resources, for example, using the Performance Monitor console using the Counter that is there.
You can also choose one for backup by using the following three methods:
1-Application Backup: Simple process with small size files, which has a negative impact on system performance when Backup is being started.
2-Workload Backup: Provides backups of virtual workloads through Windows Backup or System Center. This method also has a negative impact on system performance when Backup is being started.
3-Virtualization Host Backup: Take the whole Virtual Backup Machine. Both online and offline. The offline mode of the garden will cause the virtual machine to shut down, so we have the downtime. For Online Backup, the System Center Data Protection Manager is used and a snapshot is created using VSS. So we do not have Downtime.
You can also choose one of the following three methods to set up Fault-tolerance for a virtual machine:
1-Network Load Balancing: For services like the Web, it’s good to use this method.
2-Application Specific Clustering: Programs like SQL Server inherently have the ability to be motivated, which can be used in native environments.
3. Host Clustering: Using the Failover Cluster service, when you have Storage Shared, it can be another way to create fault-tolerance in your virtual environment.
Summarize and analyze the required workload
So far, you’ve got a lot of information about your network infrastructure. The next step is to analyze this information. At this point, determine how the workload can be grouped. Also, at this stage, you should provide the resources you need to estimate. For example, CPU, Memory, hard disk and network equipment.