.
Avamar Virtual Edition runs on a SLES-based operating system. The Avamar Virtual Edition
servers are licensed by capacity. Avamar Virtual Edition servers are available in 0.5 terabyte, 1
terabyte, 2 terabyte, and 4 terabyte licenses. Each of these license capacities have their own set
of requirements for memory, I/O, and storage.
ESX versions 5.1i, 5.5i, and 6.0i and Windows 2012 and 2012 R2 are supported by the newest
versions of AVE. A single physical host server can host up to two AVE servers, as long as those
servers are either 0.5 or 1 TB. For 2 and 4 TB capacities, only one AVE per host server is allowed
servers are licensed by capacity. Avamar Virtual Edition servers are available in 0.5 terabyte, 1
terabyte, 2 terabyte, and 4 terabyte licenses. Each of these license capacities have their own set
of requirements for memory, I/O, and storage.
ESX versions 5.1i, 5.5i, and 6.0i and Windows 2012 and 2012 R2 are supported by the newest
versions of AVE. A single physical host server can host up to two AVE servers, as long as those
servers are either 0.5 or 1 TB. For 2 and 4 TB capacities, only one AVE per host server is allowed
All Avamar Virtual Edition capacity models except the 4 TB model require a minimum of two full
equivalent processors of 2 GHz available at all times. The 4 TB model requires four 2 GHz
processors. The servers should have at least a 1 GbE network connection. Integration with
VMware VMotion is supported allowing the AVE virtual machine to be migrated seamlessly
between ESX servers. Direct Attached Storage (DAS) and Storage Area Network (SAN) are
supported so that the ESX server can use both types of storage. The mapping of a the AVE’s
virtual disk to a pass-through SCSI device, known as Raw Device Mapping or Pass-Through Disks
is not supported.
equivalent processors of 2 GHz available at all times. The 4 TB model requires four 2 GHz
processors. The servers should have at least a 1 GbE network connection. Integration with
VMware VMotion is supported allowing the AVE virtual machine to be migrated seamlessly
between ESX servers. Direct Attached Storage (DAS) and Storage Area Network (SAN) are
supported so that the ESX server can use both types of storage. The mapping of a the AVE’s
virtual disk to a pass-through SCSI device, known as Raw Device Mapping or Pass-Through Disks
is not supported.
The memory, I/O, storage partition requirements for AVE 0.5 TB capacity are listed here. Please
take a moment to review them.
The Read, Write, and Seek performance numbers are gathered using the Avamar Benchmark tool.
The requirements listed do not include the memory required for hypervisor, service console, and
other applications. The users, admin, and dpn home directories and management databases are
stored on the Operating System partition
take a moment to review them.
The Read, Write, and Seek performance numbers are gathered using the Avamar Benchmark tool.
The requirements listed do not include the memory required for hypervisor, service console, and
other applications. The users, admin, and dpn home directories and management databases are
stored on the Operating System partition
On average, a file server-only environment has a 0.3% average daily change rate, while a mixed
environment has a 3% average daily change rate. These numbers can be used to estimate the
change rates of an environment based on its size. For example, an environment consisting of 1 TB
of file server data will have a change rate of about 3 GB per day.
If the average daily data added to the Avamar Virtual Edition in a file server only environment is
less than 2 GBs per day and less than 5 GBs in a mixed environment, then the half a terabyte
version would be a good fit. If the average daily data added is less than 4 GBs in a file server
environment and less than 10 GB in a mixed environment, then the 1 TB version would be a good
fit. If the average daily data added is less than 8 GBs in a file server environment and less than
20 GBs in a mixed environment, then the 2 TB version would be a good fit. If the average daily
data added is less than 20 GBs in either a file server or mixed environment, then the 4 TB version
would be a good fit.
Please remember that the actual results depend on the retention policy and the actual data
change rate.
environment has a 3% average daily change rate. These numbers can be used to estimate the
change rates of an environment based on its size. For example, an environment consisting of 1 TB
of file server data will have a change rate of about 3 GB per day.
If the average daily data added to the Avamar Virtual Edition in a file server only environment is
less than 2 GBs per day and less than 5 GBs in a mixed environment, then the half a terabyte
version would be a good fit. If the average daily data added is less than 4 GBs in a file server
environment and less than 10 GB in a mixed environment, then the 1 TB version would be a good
fit. If the average daily data added is less than 8 GBs in a file server environment and less than
20 GBs in a mixed environment, then the 2 TB version would be a good fit. If the average daily
data added is less than 20 GBs in either a file server or mixed environment, then the 4 TB version
would be a good fit.
Please remember that the actual results depend on the retention policy and the actual data
change rate.
Virtual machines use virtual disks for storage. These can be set to use either thin or thick
provisioning, also called dynamic and fixed in Hyper-V. When thin provisioning is used, a small
fraction of the total disk size is allocated on disk creation and more capacity is allocated as data is
written to the virtual disk. In contrast, when thick provisioning us used, all disk space is allocated
upon creation of the virtual disk. AVE uses thick provisioned disks.
Virtual disks can also be either eager or lazy zeroed. Eager zeroing will zero out all disk blocks at
disk creation while lazy zeroing waits until the first write to a disk block before that block is
zeroed out.
Although eager zeroing does provide better initial performance during the operation of the AVE,
creating eager zeroed disks can take hours and can lead to time-out errors during installation. As
a result, lazy zeroing is used during installation. Disks can optionally be converted to eager
zeroing afterward for better performance.
It is also recommended that the physical disks that store the virtual disk use either RAID 1 or 10
protection. These RAID levels provide the best performance for virtual machines with high disk
usage.
provisioning, also called dynamic and fixed in Hyper-V. When thin provisioning is used, a small
fraction of the total disk size is allocated on disk creation and more capacity is allocated as data is
written to the virtual disk. In contrast, when thick provisioning us used, all disk space is allocated
upon creation of the virtual disk. AVE uses thick provisioned disks.
Virtual disks can also be either eager or lazy zeroed. Eager zeroing will zero out all disk blocks at
disk creation while lazy zeroing waits until the first write to a disk block before that block is
zeroed out.
Although eager zeroing does provide better initial performance during the operation of the AVE,
creating eager zeroed disks can take hours and can lead to time-out errors during installation. As
a result, lazy zeroing is used during installation. Disks can optionally be converted to eager
zeroing afterward for better performance.
It is also recommended that the physical disks that store the virtual disk use either RAID 1 or 10
protection. These RAID levels provide the best performance for virtual machines with high disk
usage.
Useful Link
No comments:
Post a Comment