In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-04-06 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >
Share
Shulou(Shulou.com)06/03 Report--
Recently, because the Exchange mailbox server (IBM X3650M2) has been used for too long, it is recommended to eliminate and replace it. The newly purchased Dell R730 server is migrated directly to the VM virtual machine through P2V. Gigabit network speed is OK:
After the migration is complete, the original server is idle. I wanted to build a Veeam virtual machine backup server a long time ago, but I couldn't test it because of insufficient resources. This is a good time to use this server to install and configure Veeam Availability Suite.
Veeam is a third-party virtualized data center backup and recovery company with Veeam Availability Suite as its main software, including Veeam Backup & Replication and Veeam ONE. Veeam Availability Suite combines Veeam Backup & Replication's industry-leading backup, restore, and replication capabilities with Veeam ONE's advanced monitoring, reporting, and capacity planning capabilities. Veeam Availability Suite provides all the features you need to reliably protect and manage your VMware vSphere and Microsoft Hyper-V environment, helping you build a high-availability data center through:
High-speed recovery: quickly restore the content you need in the way you need.
Avoid data loss: excellent recovery point objectives (RPO) and streamlined and efficient disaster recovery
Proven recoverability: ensure that every file, application, or virtual server can be restored every time
Effective use of data: low-risk deployment using a test environment similar to a production environment
Comprehensive perspective: proactively monitor problems and issue alarms so as not to affect the operation of the system
Veeam Availability Suite9.5 supports the following vmware platforms:
The following virtual machines are supported:
The following file levels are supported:
The steps are as follows:
Download Veeam Availability Suite 9.5 installation files
Can be downloaded directly on the official website: https://www.veeam.com/cn/
Official documentation Center: https://www.veeam.com/cn/documentation-guides-datasheets.html
Veeam Backup & Replication 9.5 User Guide for VMware vSphere: https://helpcenter.veeam.com/docs/backup/vsphere/overview.html?ver=95
Second, set up the installation environment
1. Install ESXI5.5 update3b (vCenter environment is 6.5e)
Since the VMware compatibility of IBM X3650M2 supports a maximum vSphere version of ESXI 5.5U3, the IBM server is reconfigured (12 disks: 2 147g disks as Raid1, ESXI,9 block 300g disks as Raid5 data disks, and one 300g disk as global hot backup), install ESXI and add to vcenter.
2. Install the backup server (Windows 2012 R2)
Because there are many Windows 2012 R2 virtual machines in vms, according to the system installation requirements (below), it is recommended that the backup server be installed the same or higher than the current operating system version.
VBR main components, including the following 4
Backup server: software main program
Veeam Backup & Replication console: components that protect virtualized environments
Backup proxy server: the main process of backup and restore operations
Backup repository server: storage device used to manage the entire backup and recovery
For more information, please refer to: https://helpcenter.veeam.com/docs/backup/vsphere/system_requirements.html?ver=95
Third, install VBR
1. Mount the ISO installation file to the virtual machine, and click Install on the left to start the installation.
After installing .net Framework4.5.2, you are required to restart the system, and the installation will continue automatically after reboot.
2. Accept the agreement and click next.
3. Enter the path to the License file and click next. Wait until the installation is complete before adding
4. Install it on disk C by default, and click next.
5. To install the missing components, click Install to start the installation (need to be downloaded automatically).
When the installation is complete, click next
6. If no other configuration is needed, click Install for default installation.
To specify special settings (such as specifying a SQL database, etc.), select "Let me specify different settings". Click next
7. Specify the VBR service account. Default is fine. Next step
8. Specify the name of the independent database and the authentication method. You can also use the default options to install a new database. Click next
When using an external database, you need to build the database first.
9. Specify the VBR service port. Default is fine. Click next
10. Specify the Write cache folder, which defaults to disk C.
11. Check whether the configuration information needs to be modified, and then click Install to start the installation.
Installation completed
4. Configure VBR
1. Open the desktop "Veeam Backup & Replication Console" shortcut and start VBR. As follows:
2. To add a backup storage location, click "Backup Repositories", which is stored in E:\ Backup by default.
If necessary, click "Add Repository" to add.
You can also select the default backup store and click "Edit Repository" to edit.
3. Add vSphere Virtualization platform
Select "VIRTUAL MACHINES" and click "Add Server" in the upper left corner. The following dialog box pops up, enter the address of the vCenter server and verify the account password. Next, save the configuration after successful verification.
After the addition is successful, you can perform operations such as Backup, Replication and so on. As shown below:
Use VBR for backup (Backup) and restore (Restore) operations
1. Select "BACKUP&REPLICATION" and click "Backup Job" in the upper left corner. The following dialog box pops up, enter the backup name, and next
2. Click "Add..." to add a virtual machine
Click "Exclusions..." and select the disk that does not need to be backed up (if necessary)
By default, back up all disks. If you want to back up only the system disks (note: disks, not partitions), select "Disk 0:0 only". Or select the disk you want to back up from "Selected disks".
3. Select the storage location of the backup
Click Advanced to make advanced settings, such as backup method, data compression, notification, CBT, etc. Next step
Client settings, default can be. Next step
4. Select the start time of backup job
Configuration complete, click apply, finish.
5. After the job is created, click Start to start the backup immediately.
Backup speed, completion rate and other information can be seen in Job progress. (because the traffic is relatively large during the day and the speed is relatively slow.)
Backup is complete. Check the backup log to see the detailed information.
After the backup is completed, the following files are generated in the backup directory. By comparison, you can see that the data of the original 35.8GB is compressed into 12.1GB.
The first full backup will take longer and the incremental backup will be faster.
Note:
"if the virtual machine has a snapshot during the first backup, another snapshot is generated during the veeam backup and deleted after the backup completes."
But the backup will have a warning: Changed block tracking cannot be enabled: one or more snapshots present.
When the backup is complete, the status is Warning.
Reason: if the virtual machine has snapshots, CBT (Changed Block Tracking) is off by default. This is due to vmware restrictions.
Solution: delete all snapshots, let VBR enable CBT on the virtual machine, and then recreate the snapshot after the backup is completed. (when backing up, VBR will add a new ctkEnabled entry with a value of TRUE in the parameter configuration option of the virtual machine. The figure below). Once the CBT feature is enabled, snapshots will no longer block CBT.
You can also manually enable CBT before backing up and then back up. The methods are as follows:
Enable the CBT method: http://kb.vmware.com/kb/2078214
To enable CBT on a virtual machine:
1 >. Power off the virtual machine.
2 >. "right-click the virtual machine, and click Edit Settings."
3 >. Click the options tab.
4 >. Click General under the Advanced area, and then click configuration parameters. The configuration parameters dialog box opens.
5 >. Click add Row.
6 >. Add the ctkEnabled parameter and set its value to true.
7 >. Click add row, add scsi0:0.ctkEnabled, and set its value to true.
Note: the scsi0:0 in scsi0:0.ctkEnabled indicates that the SCSI device is assigned to the hard disk added to the virtual machine. A SCSI device, as shown at 1:1 by scsi0:0, scsi0:1, or scsi, is provided for each hard disk added to the virtual machine. Enabled (or disabled) CBT on each disk separately.
8 >. Power on the virtual machine.
9 >. In the home directory of the virtual machine, verify that each CBT-enabled disk also has an vmname-ctk.vmdk file.
To disable CBT, ensure that there are no snapshots on the virtual machine.
For more information, see Consolidating snapshots in ESX/ESXi 3.x and 4.x (1007849) and Consolidating snapshots in vSphere 5.x/6.0 (2003638).
To disable CBT:
1 >. Power off the virtual machine.
2 >. "right-click the virtual machine, and click Edit Settings."
3 >. Click the options tab.
4 >. Click General under the Advanced area, and then click configuration parameters. The configuration parameters dialog box opens.
5 >. Set the ctkEnabled parameter of the desired SCSI disk to false.
6 >. Power on the virtual machine.
About CBT:
Part of virtual machine management is the use of data protection, including snapshots. Incremental snapshots are faster and more efficient because they can capture content that has changed since the last iteration. This increases the frequency of snapshots and uses less storage space. For disaster recovery purposes, it also requires less network bandwidth to replicate snapshots to remote sites.
However, incremental snapshots usually require a mechanism to track these changes. VMware calls this mechanism change Block tracking (CBT), which can be invoked by backup software tools by using vStorage API for data protection. If there is no VMware CBT, you will need to track the change block through backup or snapshot management tools.
If you plan to use incremental snapshots in a VMware environment, it is important to enable VMware CBT for protected virtual machines. This usually requires shutting down the virtual machine and adding the ctkEnabled parameter to the virtual machine's configuration parameters dialog box according to the documentation provided by VMware. You can confirm that VMware CBT is enabled by checking each virtual disk and snapshot for .vmdk files with .ctk tags, such as vmname-ctk.vmdk or vmname-000139-ctk.vmdk.
Once VMware CBT is enabled, there is little reason to disable it. However, you can usually enable CBT by setting the ctkEnabled parameter to false and removing the existing snapshot of the virtual machine.
6. Restore backup
1 >. Through overall recovery
Select "BACKUP&REPLICATION", click "Restore" above, and the following dialog box pops up. Select "Entire VM" to restore the entire virtual machine, next
Click "Add VM" and select "From backup..."
To add the virtual machine that you just backed up, click Add
Then click "Point..." and select a full backup (Full) node. Once confirmed, the next step
Choose to restore to a new location, next
Select the target host host to restore to, click Host … Make a modification
To select the target resource pool for recovery, click Pool... Make a modification
Select the target storage and VM disk type. Click "Datastore..." and "Disk Type...". Make a modification
Select the name of the restored virtual machine and the storage folder.
Select the network card of the restored virtual machine, or click Disconnected to cancel the network card connection.
Recovery reason, skip
Check whether the recovery information is correct, complete and start the recovery.
Recovery process
After the virtual machine is restored, start normally
2 >. Restore from a VMDK/VMX file
"after opening the recovery wizard, select VM files." Next step
Select the restored virtual machine, next
Select restore point
Select the target host, the directory where the recovery files are stored (you can create a new one, as shown below), and the files to be restored. Next step
Complete, start recovery
Recovery succeeded
Compared with the recovery task, you can see that the overall recovery is twice as fast as the file recovery.
Files in storage after recovery
Select the .vmx file and right-click to register the virtual machine
After the registration is successful, boot up. Recovery is successful!
Use VBR for synchronization (Replication) and recovery (Restore) operations
The biggest difference between synchronization and backup is that the target side of synchronization is also a virtual machine, but the data of the virtual machine is synchronized with the original virtual machine.
1 >. Synchronous operation
Select "BACKUP&REPLICATION", click "Replication job" in the upper left corner, pop up the following dialog box, and enter the synchronization name. Next step
Select synchronized virtual machine, excluded disk (same as backup), virtual machine source (optional backup files), and so on. Next step
Select the synchronization target host, resource pool, virtual machine folder, storage, etc., next
Select the synchronization policy, specify the target name after synchronization, the synchronization point held, and so on.
Click Advanced Advanced Settings to configure traffic, notifications, CBT settings, and so on. After confirmation, the next step
Configure data transfer by default.
Configure client processing and configure application-aware processing (such as file exclusion, etc.) as needed. Next step
Configure a synchronization schedule, which can be set to synchronize once a day or at regular intervals.
Check the summary and the job creation is complete
If it is set to be synchronized at regular intervals, such as 5 minutes, the job starts execution automatically.
After the synchronization is successful, a virtual machine is generated on the target host
2 >. Restore operation
Select "BACKUP&REPLICATION"-- > "Replicas", then click on the virtual machine to be restored, right-click "Failover Now...", and open the restore operation wizard
Select the virtual machine that needs to be restored (by default), and then select the restore point
Click finish to start the recovery.
After a successful restore, the virtual machine is automatically turned on on the target host
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.