What is veeam software? what is veeam backup? what is veeam cloud connect? Learn about veeam
I. introduction veeam .
Veeam Backup & Replication is no longer a name so familiar for the current virtualization implementations. The role of this solution in the problem is backup, restore and secure virtual infrastructure data meet completely the requirements of any magnitude or complexity of the Vmware virtualization environment and currently supports both Hyper-V. Some of the main concerns that this solution delivers:
-Support for ESX/ESXi virtualization environments Vmware and Microsoft Hyper-V
-Enhanced with distributed backup architecture for the great environment and welfare academic journals
-In addition to the backup solution also comes in in this focused product is Replication.
-Supports fast restore direct system (start the virtual machine directly) from backup files that have been compressed and dedup without restore the virtual machine file storage system.
-Diversify the modes of restore from a backup: restore the virtual machine, the virtual machine files, files inside the virtual machine's OS or data of a specialized application such as AD, Exchange ...
-Supports incremental backup (Incremental Forward and Reversed Incremental Backup)
-Enhanced archiving capabilities with features that compress and deduplication reduces the amount of investment for the system backup
-Provide report and the results of real-time backup parameters,
2. The model design method and standard veeam backup replication
The simple solution is to just and small businesses
This program contains only a physical or virtual server on the deployment of veeam backup Server (backup is the Management Agency (backup), direct receiving and processing backup including data processing and compression, but he did up) Is the role of a task is backup library storage and storage backup data connection.
With just one simple solution Backup server when applied in large environments with multiple VMs and Jobs would not be a reasonable solution in terms of performance. And from there arose the problem is to deploy discrete multiple Backup Server will reduce the load and increase performance to the problem of backing up but a matter of "discrete" arose to a problem in management focus it will become the pressure for the administrator. Therefore from the Veeam v6 has developed a new component called Backup Proxy sole mission is to receive and process the data backup from the target then taken to storage in the Backup Repository. Themselves administrators now just a Backup Server plays a central role in managing the Jobs backup system also "load backup" will be leveled will spread to the Backup Proxy offload the backup server and strengthening more performance backup system latency.
This solution results in solving the consolidated information backup between sites in a large-scale system (Multi-Site). Now a new component appears Veeam Backup Enterprise Manager responsible only provide a web interface centralized management of all backup jobs on the system are dispersed geographically while it processes the backup operation still be managed and executed at the site Detached à enhance the ability to focus on large-scale models.
Welcome to part two of our series on the Veeam backup solution in this section, we will continue to overview revolves around knowledge of backups and backup methods carry VBR mode brings.
Overall portfolio compared with the first part as follows:
I Introduction
II. Overview
1. The active ingredient
2. The standard model designed for Veeam Backup & Replication solution
3. The backup in VBR mode
4. The method of backup storage in VBR
3. The backup mode in VBR
With Veeam Backup as the backup solution for virtual infrastructure will be completely different from the traditional. With traditional data regardless of the backup is the file, the data of "apps" also for infrastructure virtualization applications, guestOS is the concept that the backup software later no longer interested anymore, but our main concern is the set of virtual machine files (.vmdk, .VMX, snapshots ...). Therefore it should produce a number of ways to back up specific differentiation for infrastructure virtualization:
Network Mode
Virtual Appliance Mode
Direct San Access Mode
+ Network Mode
Network Mode is the basic model for determining the environment ethernet the environmental transmission of data backup. With this method there are some precautions:
Workload weighing on both the Host ESXi is hosted VM and Backup Proxy due to receive and process the data backup (compression, dedup) before storage in the repository
Easily causing traffic congestion management of ESXi by IP interaction with the host is IP used as a management
processing speed backup for this method is the slowest compared to other methods
image
process work Network modes:
The initial backup server will manage backup jobs and decide the backup proxy and backup repository will assume the role of proxy and the repo list is available (by default). Then the backup process will take place closed as follows:
1. Backup the selected Proxy sends requests to ESXi hosts needed to confirm the location on the VM datastore (line 1)
2. The host is hosted VM will start the VM snapshot and copy the data and send them to block proxy backup processed through ethernet line (line 3.4)
3. Backup Proxy after finishing its processing tasks will data transfer required for Backup storage repository (5)
4. Remove the snapshot on the VM
+ Virtual Appliance Mode
This is a special mode only for environmental concept and server virtualization Backup Proxy role is a "virtual machine" on the environment with the need to backup VMs. This mode based on the ability to hot-add the SCSI device's virtual ESXi to mount the disks of the VM to the backup to the proxy server and then directly reading the block data through the communication port SAN ESXi hosts rather than through network as step 2.4 of the Network Mode as its main advantages advantage of the performance of the SAN environment brings than go through the network mode network management influence. However storing backup data would also like line 5 of network mode is via ethernet (for NFS, CIFS, iSCSI) and SANs continue if applicable based RDM, Virtual Disks ...
Note one detail: Backup Proxy forced to lie on the Host to be configured "see" all the VMs on SAN system files. Because the VMDK file only sees the new ESXi mount them on the backup proxy.
The working process of the virtual appliance model:
1. The position information of the backup server of VM was confirmed to lock the snapshot files in your vmdk VMS by datastore backup agent to send a request
2. Mount vmdk file on the backup agent to confirm (automatic or user-defined forum administrator.
3. Through communication, virtual machine backup proxy host ESXi st read data block processing and return backup repo
4. Finally, all of the files and delete detach vmk from VM snapshot snapshot
St + direct access
This is a special model completely changed the thinking mode in virtual environment backup. This model than the other "sugar" data as we will see below, now here's the data directly from the backup proxy information on the St. Through the processing of network environment. Three, with the repo server.
This process operation is through the data line will be five or six "relay station" mode, and another wasted too much "relay station":
Network mode: St - esxi > > > backup repo backup agent
Appliance mode: St - > "stack esxi" - > backup - > backup repo agent
ST: direct access backup - > backup repo agent in St.
Note: this method requires backup is equipped with a special agent to see all in the Saint (only supports all three blocks as big as a football club or level of iSCSI does not support NFS)
Workflow:
1. Backup Server determines the information of the backup VMs should then proceed through snapshot VM Backup proxy.
2. Backup Proxy SAN environment through direct access to the VM Files lying on the SAN and backed up, processed and taken to the Backup repo
3. Remove snapshot VM
4. The method of storing backups in VBR
This item we I will learn VBR support how storing backup data of VM how through two mechanisms:
Reversed incremental backup
Forward incremental backups
also, VBR also supports two optional backup support for the other two :
Synthetic Full
Active Full backup
+ incremental backup Reversed
True to its name, as well as storage similar to the way traditional backup methods will only backup data changes ie changes in the VM's VMDK. Determining the change is support directly from VMware through a technology called Change Block Tracking (similar bits in Windows), this technology will allow "marked" change data of the VMDK file in during use as compared with the previous backup. Returning to Reversed incremental backups we will start the sequence as follows:
Times first backup using this method will create a full backup (note in VBR without defining a method full backup individually that would be an option in the incremental backups), so backup first time will require the use of the full backup option. Then save with filed .vbk
The following backup times using incremental backup method (just backup the data block different from previous backups). The results will give a combination of the new data block.
The "New Data Block" after receiving would be combined with the previous full backup files .vbk to create full backups with the latest state data. Also besides the system will automatically generate incremental file backups .vrb reversed version contains the "old data block" has been replaced by "the new data block". So we will always have a new backup and the most recent full backup status. And this entire process will repeat a backup lifecycle.
This method completely brings the reliability and savings for users with the ability incremental forever and save disk space when only contains a full backup on the backup system as well as ensuring that the coexistence of reverse incremental allow users to restore back each time desired.
+ Forward incremental backup
Similarly, a method in this method will also issue support backup change data blocks but with the way, storage is completely different and closer to more traditional:
The first time will be a full backup and how on
The next time the same will backup the "block new data" but instead recombine into a full version is simpler this way the time the backup after the backup first just back up "block new data" and include them in .vib file
image
+ Synthetic Full
Synthetic full options are applied specifically for incremental backup Forward nature because of its backup storage. The special thing here is that "life cycle" exists for the backup. All backup solutions are needed lifecycle certain backup storage for 1 week, 1 month, 1 year ... VBR also need to support this, but due to the special nature of the forward incremental backup should the turning cycle is not easy because it is incremental forever archives only recently changed to use the block while the full version is the first backup should always exist this was against the rules lifecycle backup.
Therefore Synthetic full launch of this feature solves the irregularities of the full version by allowing the cycle defined recombine synthetic full backups that fit your backup storage lifecycle "enterprise"
Examples of this in backup incremental will always be performed every day except Thursday, a week before the full version from backup incremental, a combination of full text.
Also, choose to use the complete synthetic backup also brought another option allows creating a complete version of the new version of the full version of backup, before switching to the opposite incremental open. Vrb so there will always be she A complete backup system allows to save hard disk space.
Like a wallet for the fifth day to create a basically complete, from Sunday to Thursday will switch to the opposite is incremental. Vbr file format
+ Active Full Backup
is optional to give some businesses wishing to perform full backup under certain cycle directly from the virtual environment, not through the mechanism combining full version are with the incremental to ie create synthetic full backups Synthetic full backup.
I. introduction veeam .
Veeam Backup & Replication is no longer a name so familiar for the current virtualization implementations. The role of this solution in the problem is backup, restore and secure virtual infrastructure data meet completely the requirements of any magnitude or complexity of the Vmware virtualization environment and currently supports both Hyper-V. Some of the main concerns that this solution delivers:
-Support for ESX/ESXi virtualization environments Vmware and Microsoft Hyper-V
-Enhanced with distributed backup architecture for the great environment and welfare academic journals
-In addition to the backup solution also comes in in this focused product is Replication.
-Supports fast restore direct system (start the virtual machine directly) from backup files that have been compressed and dedup without restore the virtual machine file storage system.
-Diversify the modes of restore from a backup: restore the virtual machine, the virtual machine files, files inside the virtual machine's OS or data of a specialized application such as AD, Exchange ...
-Supports incremental backup (Incremental Forward and Reversed Incremental Backup)
-Enhanced archiving capabilities with features that compress and deduplication reduces the amount of investment for the system backup
-Provide report and the results of real-time backup parameters,
 |
| what is veeam software? what is veeam backup? what is veeam cloud connect? Learn about veeam |
II. General overview
In this section will provide more detail about Veeam Backup & Replication solution includes the architecture and features of it at the same time as the concepts necessary to understand the processes of operation and handling of Veeam Backup & Replication
1. active components
Veeam Backup & Replication first is not a solution for a standalone application that it is a solution for an application is designed in modular method allows more customizable user preferences the magnitude of virtualization and the environment in the configuration. Like the installation package of the Veeam will include many ingredients collected (Components) to set up a complete backup infrastructure. In a role, that component will play the role of core process and a few other components are optional to add support for the operation of the active plate management business needs some other component will be added.
However note one thing these components can fully deploy a common operating system (physical or virtual) or separate pieces on more air support for expanding demand, performance, management ...
Veeam Backup & Replication will include the following components. Some can be installed using integral or some other files are configured in the active process of other components:
2 Veeam backup server
Is a physical or virtual server package installed Veeam Backup & Replication is the main nuclear role for the entire backup infrastructure has the task of making the central place to configure and control backup operations on system restore. The main function:
Manage bthe ackup tasks, replication and restore
The schedule for the backup job as well as determine the allocation of resources (this concept is needed to understand the method and store the backup in the following section)
Is where the configuration and management of other components in the backup infrastructure.
Note: Veeam backup server default deployment it will have two default component comes as a proxy Backup and backup repository.
3 Backup Proxy
While Veeam Backup Server deployment is complete, the server will bear the entire mission to a backup process including job back up and handle the traffic backup from the virtual machine when performing the backup. Then the backup data will be pushed directly to home is the Veeam Backup server. Such cases are only accepted in extreme environments with a small amount of job and VM limits but in large environments, it totally tripping problem that my server performance endured
To completely separate the task of handling the traffic backup as well as optimize and create more customizable environment Veeam has for leaving a component called a Proxy Backup is the server having the only task is to receive and process the data backup ( including work to compress and dedup) when such data result from the backup proxy is the data backup will be stored in the Backup Repository.
This component is implemented only for window server (physical or virtual) in your virtual environment. To optimize performance for much more than backup local time then the design out many proxy back-ups is absolutely necessary. In this case, the Backup server will coordinate "workload" are out of the proxy to enhance performance.
4 Backup Repository
Is the place used to store backup data, copy the VM and the data on the backup repository replicate? Ve technically is a folder on the system's storage business. The use of the concept of all necessary Partial repository for separate environments where storage backup can back up the intent to distribute the load over multiple systems.
About Backup Repository has several categories as follows:
Window server with local storage
Linux server with local or mount NFS
CIFS (SMB) share
The determination of servers (window or Linux) as the backup repository, the backup server will automatically deploy agents needed down servers that control the storage of all data backups and other features.
5 Veeam Backup Enterprise Manager
As an extension to the consolidated tasked to manage backup jobs from all servers on Veeam Backup system through an administration interface from the web browser.
6 Veeam Backup Search
As part extended search support file data file in the data backup window only support.
7 U-AIR Wizards
Enhanced data recovery capabilities for application-specific data such as Exchange Server, Active Directory
In this section will provide more detail about Veeam Backup & Replication solution includes the architecture and features of it at the same time as the concepts necessary to understand the processes of operation and handling of Veeam Backup & Replication
1. active components
Veeam Backup & Replication first is not a solution for a standalone application that it is a solution for an application is designed in modular method allows more customizable user preferences the magnitude of virtualization and the environment in the configuration. Like the installation package of the Veeam will include many ingredients collected (Components) to set up a complete backup infrastructure. In a role, that component will play the role of core process and a few other components are optional to add support for the operation of the active plate management business needs some other component will be added.
However note one thing these components can fully deploy a common operating system (physical or virtual) or separate pieces on more air support for expanding demand, performance, management ...
Veeam Backup & Replication will include the following components. Some can be installed using integral or some other files are configured in the active process of other components:
2 Veeam backup server
Is a physical or virtual server package installed Veeam Backup & Replication is the main nuclear role for the entire backup infrastructure has the task of making the central place to configure and control backup operations on system restore. The main function:
Manage bthe ackup tasks, replication and restore
The schedule for the backup job as well as determine the allocation of resources (this concept is needed to understand the method and store the backup in the following section)
Is where the configuration and management of other components in the backup infrastructure.
Note: Veeam backup server default deployment it will have two default component comes as a proxy Backup and backup repository.
3 Backup Proxy
While Veeam Backup Server deployment is complete, the server will bear the entire mission to a backup process including job back up and handle the traffic backup from the virtual machine when performing the backup. Then the backup data will be pushed directly to home is the Veeam Backup server. Such cases are only accepted in extreme environments with a small amount of job and VM limits but in large environments, it totally tripping problem that my server performance endured
To completely separate the task of handling the traffic backup as well as optimize and create more customizable environment Veeam has for leaving a component called a Proxy Backup is the server having the only task is to receive and process the data backup ( including work to compress and dedup) when such data result from the backup proxy is the data backup will be stored in the Backup Repository.
This component is implemented only for window server (physical or virtual) in your virtual environment. To optimize performance for much more than backup local time then the design out many proxy back-ups is absolutely necessary. In this case, the Backup server will coordinate "workload" are out of the proxy to enhance performance.
4 Backup Repository
About Backup Repository has several categories as follows:
Window server with local storage
Linux server with local or mount NFS
CIFS (SMB) share
The determination of servers (window or Linux) as the backup repository, the backup server will automatically deploy agents needed down servers that control the storage of all data backups and other features.
5 Veeam Backup Enterprise Manager
As an extension to the consolidated tasked to manage backup jobs from all servers on Veeam Backup system through an administration interface from the web browser.
6 Veeam Backup Search
As part extended search support file data file in the data backup window only support.
7 U-AIR Wizards
Enhanced data recovery capabilities for application-specific data such as Exchange Server, Active Directory
The simple solution is to just and small businesses
This program contains only a physical or virtual server on the deployment of veeam backup Server (backup is the Management Agency (backup), direct receiving and processing backup including data processing and compression, but he did up) Is the role of a task is backup library storage and storage backup data connection.
This solution results in solving the consolidated information backup between sites in a large-scale system (Multi-Site). Now a new component appears Veeam Backup Enterprise Manager responsible only provide a web interface centralized management of all backup jobs on the system are dispersed geographically while it processes the backup operation still be managed and executed at the site Detached à enhance the ability to focus on large-scale models.
Overview Veeam Backup & Replication solution v6
Overall portfolio compared with the first part as follows:
I Introduction
II. Overview
1. The active ingredient
2. The standard model designed for Veeam Backup & Replication solution
3. The backup in VBR mode
4. The method of backup storage in VBR
3. The backup mode in VBR
With Veeam Backup as the backup solution for virtual infrastructure will be completely different from the traditional. With traditional data regardless of the backup is the file, the data of "apps" also for infrastructure virtualization applications, guestOS is the concept that the backup software later no longer interested anymore, but our main concern is the set of virtual machine files (.vmdk, .VMX, snapshots ...). Therefore it should produce a number of ways to back up specific differentiation for infrastructure virtualization:
Network Mode
Virtual Appliance Mode
Direct San Access Mode
+ Network Mode
Network Mode is the basic model for determining the environment ethernet the environmental transmission of data backup. With this method there are some precautions:
Workload weighing on both the Host ESXi is hosted VM and Backup Proxy due to receive and process the data backup (compression, dedup) before storage in the repository
Easily causing traffic congestion management of ESXi by IP interaction with the host is IP used as a management
processing speed backup for this method is the slowest compared to other methods
image
process work Network modes:
The initial backup server will manage backup jobs and decide the backup proxy and backup repository will assume the role of proxy and the repo list is available (by default). Then the backup process will take place closed as follows:
1. Backup the selected Proxy sends requests to ESXi hosts needed to confirm the location on the VM datastore (line 1)
2. The host is hosted VM will start the VM snapshot and copy the data and send them to block proxy backup processed through ethernet line (line 3.4)
3. Backup Proxy after finishing its processing tasks will data transfer required for Backup storage repository (5)
4. Remove the snapshot on the VM
+ Virtual Appliance Mode
This is a special mode only for environmental concept and server virtualization Backup Proxy role is a "virtual machine" on the environment with the need to backup VMs. This mode based on the ability to hot-add the SCSI device's virtual ESXi to mount the disks of the VM to the backup to the proxy server and then directly reading the block data through the communication port SAN ESXi hosts rather than through network as step 2.4 of the Network Mode as its main advantages advantage of the performance of the SAN environment brings than go through the network mode network management influence. However storing backup data would also like line 5 of network mode is via ethernet (for NFS, CIFS, iSCSI) and SANs continue if applicable based RDM, Virtual Disks ...
Note one detail: Backup Proxy forced to lie on the Host to be configured "see" all the VMs on SAN system files. Because the VMDK file only sees the new ESXi mount them on the backup proxy.
The working process of the virtual appliance model:
1. The position information of the backup server of VM was confirmed to lock the snapshot files in your vmdk VMS by datastore backup agent to send a request
2. Mount vmdk file on the backup agent to confirm (automatic or user-defined forum administrator.
3. Through communication, virtual machine backup proxy host ESXi st read data block processing and return backup repo
4. Finally, all of the files and delete detach vmk from VM snapshot snapshot
St + direct access
This is a special model completely changed the thinking mode in virtual environment backup. This model than the other "sugar" data as we will see below, now here's the data directly from the backup proxy information on the St. Through the processing of network environment. Three, with the repo server.
This process operation is through the data line will be five or six "relay station" mode, and another wasted too much "relay station":
Network mode: St - esxi > > > backup repo backup agent
Appliance mode: St - > "stack esxi" - > backup - > backup repo agent
ST: direct access backup - > backup repo agent in St.
Note: this method requires backup is equipped with a special agent to see all in the Saint (only supports all three blocks as big as a football club or level of iSCSI does not support NFS)
Workflow:
1. Backup Server determines the information of the backup VMs should then proceed through snapshot VM Backup proxy.
2. Backup Proxy SAN environment through direct access to the VM Files lying on the SAN and backed up, processed and taken to the Backup repo
3. Remove snapshot VM
4. The method of storing backups in VBR
This item we I will learn VBR support how storing backup data of VM how through two mechanisms:
Reversed incremental backup
Forward incremental backups
also, VBR also supports two optional backup support for the other two :
Synthetic Full
Active Full backup
+ incremental backup Reversed
True to its name, as well as storage similar to the way traditional backup methods will only backup data changes ie changes in the VM's VMDK. Determining the change is support directly from VMware through a technology called Change Block Tracking (similar bits in Windows), this technology will allow "marked" change data of the VMDK file in during use as compared with the previous backup. Returning to Reversed incremental backups we will start the sequence as follows:
Times first backup using this method will create a full backup (note in VBR without defining a method full backup individually that would be an option in the incremental backups), so backup first time will require the use of the full backup option. Then save with filed .vbk
The following backup times using incremental backup method (just backup the data block different from previous backups). The results will give a combination of the new data block.
The "New Data Block" after receiving would be combined with the previous full backup files .vbk to create full backups with the latest state data. Also besides the system will automatically generate incremental file backups .vrb reversed version contains the "old data block" has been replaced by "the new data block". So we will always have a new backup and the most recent full backup status. And this entire process will repeat a backup lifecycle.
This method completely brings the reliability and savings for users with the ability incremental forever and save disk space when only contains a full backup on the backup system as well as ensuring that the coexistence of reverse incremental allow users to restore back each time desired.
+ Forward incremental backup
Similarly, a method in this method will also issue support backup change data blocks but with the way, storage is completely different and closer to more traditional:
The first time will be a full backup and how on
The next time the same will backup the "block new data" but instead recombine into a full version is simpler this way the time the backup after the backup first just back up "block new data" and include them in .vib file
image
+ Synthetic Full
Synthetic full options are applied specifically for incremental backup Forward nature because of its backup storage. The special thing here is that "life cycle" exists for the backup. All backup solutions are needed lifecycle certain backup storage for 1 week, 1 month, 1 year ... VBR also need to support this, but due to the special nature of the forward incremental backup should the turning cycle is not easy because it is incremental forever archives only recently changed to use the block while the full version is the first backup should always exist this was against the rules lifecycle backup.
Therefore Synthetic full launch of this feature solves the irregularities of the full version by allowing the cycle defined recombine synthetic full backups that fit your backup storage lifecycle "enterprise"
Examples of this in backup incremental will always be performed every day except Thursday, a week before the full version from backup incremental, a combination of full text.
Also, choose to use the complete synthetic backup also brought another option allows creating a complete version of the new version of the full version of backup, before switching to the opposite incremental open. Vrb so there will always be she A complete backup system allows to save hard disk space.
Like a wallet for the fifth day to create a basically complete, from Sunday to Thursday will switch to the opposite is incremental. Vbr file format
+ Active Full Backup
is optional to give some businesses wishing to perform full backup under certain cycle directly from the virtual environment, not through the mechanism combining full version are with the incremental to ie create synthetic full backups Synthetic full backup.
