Docu59612 Backup and Recovery Manager 1.3 Sizing and Configuration Guide

EMC Backup & Recovery Manager
Version 1.3
Sizing and Configuration Guide

302-002-004
REV 02
Copyright © 2015-2017 Dell Inc. or its subsidiaries. All rights reserved.
Published August 2017
Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND
WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED
IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.
Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners.
Published in the USA.
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
2 EMC Backup & Recovery Manager 1.3 Sizing and Configuration Guide
CONTENTS
Preface 5
Chapter 1 Considerations and recommendations 9

Backup & Recovery Manager deployment sizing recommendations............10
Requirements.............................................................................................. 11
Backup & Recovery Manager server software requirements.......... 11
Backup & Recovery Manager server installation requirements....... 11
System requirements..................................................................... 13
Considerations for the Backup & Recovery Manager server ...................... 13
Factors for future capacity planning .......................................................... 13
Chapter 2 Sizing, Performance and Best Practices 15

CPU, memory and database augmentation for the Backup & Recovery
Manager server........................................................................................... 16
Configuring the Backup & Recovery Manager VM...................................... 16
Configuring memory.......................................................................16
Configuring CPU............................................................................ 17
Configuring the virtual hard disk for Backup & Recovery Manager
server MongoDB ............................................................................17
EMC Backup & Recovery Manager 1.3 Sizing and Configuration Guide 3
CONTENTS
Preface
As part of an effort to improve product lines, periodic revisions of software and

hardware are released. Therefore, all versions of the software or hardware currently in
use might not support some functions that are described in this document. The
product release notes provide the most up-to-date information on product features.
If a product does not function correctly or does not function as described in this
document, contact a technical support professional.
Note
This document was accurate at publication time. To ensure that you are using the
latest version of this document, go to the Support website at https://
support.emc.com.
Purpose
This document describes how to configure and administer Backup & Recovery
Manager.
Audience
This document is intended for the host system administrator, system programmer, or
operator that manages Backup & Recovery Manager for Avamar or NetWorker
deployments.
Revision history
The following table presents the revision history of this document.
Table 1 Revision history
Revision Date Description

02 August 11, 2017 Updated formatting in the following topic:
Expand the Mongo database space on page 18
01 June 15, 2014 Initial release of the Backup & Recovery Manager Sizing
and Configuration Guide.
Related documentation
The following EMC publications provide additional information:
l EMC Backup & Recovery Manager Release Notes
Contains information on new features and changes, fixed problems, known
limitations, environment and system requirements for the latest Backup &
Recovery Manager software release.
l EMC Backup & Recovery Manager User Guide
Contains information on new features and changes, fixed problems, known
limitations, environment and system requirements for the latest Backup &
Recovery Manager software release.
l EMC Avamar Online Compatibility and Interoperability Matrix
l EMC NetWorker Online Software Compatibility Guide
Preface
You can access the Online Software Compatibility Guides on the EMC Online
Support site at https://support.emc.com. From the Support by Product pages,
search for NetWorker using "Find a Product".
l EMC Avamar documentation
l EMC NetWorker documentation
Special notice conventions that are used in this document
The following conventions are used for special notices:
NOTICE
Identifies content that warns of potential business or data loss.
Note
Contains information that is incidental, but not essential, to the topic.
Typographical conventions
The following type style conventions are used in this document:
Table 2 Style conventions
Bold Used for interface elements that a user specifically selects or clicks,
for example, names of buttons, fields, tab names, and menu paths.
Also used for the name of a dialog box, page, pane, screen area with
title, table label, and window.
Italic Used for full titles of publications that are referenced in text.
Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, file names, file name extensions, prompts, and
syntax
l Commands and options
Monospace italic Used for variables.

Monospace bold Used for user input.
[] Square brackets enclose optional values.
| Vertical line indicates alternate selections. The vertical line means or

for the alternate selections.
{} Braces enclose content that the user must specify, such as x, y, or z.
... Ellipses indicate non-essential information that is omitted from the

example.
You can use the following resources to find more information about this product,
obtain support, and provide feedback.
Where to find product documentation
l https://support.emc.com
l https://community.emc.com
Preface
Where to get support

The Support website at https://support.emc.com provides access to licensing
information, product documentation, advisories, and downloads, as well as how-to and
troubleshooting information. This information may enable you to resolve a product
issue before you contact Support.
To access a product specific Support page:
1. Go to https://support.emc.com/products.
2. In the Find a Product by Name box, type a product name, and then select the
product from the list that appears.
3. Click the following button:
4. (Optional) To add the product to My Saved Products, in the product specific

page, click Add to My Saved Products.
Knowledgebase
The Knowledgebase contains applicable solutions that you can search for by solution
number, for example, 123456, or by keyword.
To search the Knowledgebase:
1. Go to https://support.emc.com.
2. Click Advanced Search.
The screen refreshes and filter options appear.
3. In the Search Support or Find Service Request by Number box, type a solution
number or keywords.
4. (Optional) To limit the search to specific products, type a product name in the
Scope by product box, and then select the product from the list that appears.
5. In the Scope by resource list box, select Knowledgebase.
The Knowledgebase Advanced Search panel appears.
6. (Optional) Specify other filters or advanced options.
7. Click the following button:
Live chat
To participate in a live interactive chat with a support agent:
2. Click Chat with a Support Agent.
Service requests
To obtain in-depth help from Support, submit a service request. To submit a service
request:
2. Click Create a Service Request.
Note
To create a service request, you must have a valid support agreement. Contact a sales
representative for details about obtaining a valid support agreement or with questions
about an account.
To review an open service request:
Preface
2. Click Manage service requests.
Online communities
Go to the Community Network at https://community.emc.com for peer contacts,
conversations, and content on product support and solutions. Interactively engage
online with customers, partners, and certified professionals for all products.
How to provide feedback
Feedback helps to improve the accuracy, organization, and overall quality of
publications. You can send feedback to DPAD.Doc.Feedback@emc.com.
CHAPTER 1
Considerations and recommendations
This section provides the test details and the resulting suggestions, considerations and
recommendations for sizing your Backup & Recovery Manager environment.
l Backup & Recovery Manager deployment sizing recommendations................... 10

l Requirements...................................................................................................... 11
l Considerations for the Backup & Recovery Manager server .............................. 13
l Factors for future capacity planning .................................................................. 13
Considerations and recommendations 9

Backup & Recovery Manager deployment sizing

recommendations
Based on numerous performance tests and the considerations of different aspects of
long and short backup activities, 8 to 12 hours versus 24 hours backup and replication
windows, there are two levels for deployment.
Note
The performance tests were executed in a simulated environment and results might
vary based on individual customer environments. Also, the test data points used are
exclusive of network latency (WAN).
The following table lists the recommendations for Level 1 and Level 2 Backup &
Recovery Manager deployments.
Table 3 Backup & Recovery Manager deployment recommendations
Total number
of Avamar/ Maximum
Deployment Database Retention
Networker CPU Memory network
level size period
backups per usage
day
Level 1 Up to 100,000 4 8 GB 1 TB 1 year 17 Mbps
Level 2 Up to 200,000 8 16 GB 2 TB 1 year 35 Mbps
l At the Level-1 deployment, the number of virtual CPU cores and memory
allocations are at the default configurations. They need to be set as Reserved after
the BRM ova is deployed. The Mongo database needs to be augmented to 1 TB in
order to retain the data in the database for a length of one year. This can be done
either through the virtual disk extension or through adding a new virtual disk and
then going through the procedures of partition etc to make it an integral part of
the mongo database.
l At Level-2 deployment, the number of the virtual CPU cores and the memory need
to be increased to the level depicted in the above table. The Mongo database
needs to be augmented to 2 TB in order to retain the data in the database for a
length of one year. This can be done either through the virtual disk extension or
through adding a new virtual disk and then going through the procedures of
partition etc to make it an integral part of the mongo database.
l When daily backups and replications reach the 200,000, deploying the second
Level-2 BRM systems is recommended to split the load of backup and replication
activities.
Details on how to expand the Mongo database to 1TB or 2 TB, and how to increase the
number of CPUs, and the amount of memory allocated is available in Sizing
performance and best practices.
Requirements
There are minimum hardware and software requirements that must be met to
successfully deploy and install the Backup & Recovery Manager software.
Ensure that all current operating system patches or updates are installed.
Backup & Recovery Manager server software requirements

The Backup & Recovery Manager server can be installed on both a virtual host (vApp)
and a physical host by using the SLES native installer.
l Minimum required versions for the Virtual Application (vApp):
n ESXi
n ESX 5.1, 5.5 and 6.0
n VCenter Server 5.0 and 6.0
n VSphere Client 5.0 and 5.1
l Native installer for SLES Linux:
n The bootable .iso image requires a minimum of 3.3 GB free space on a DVD.
n Two disks (operating system and MongoDB disks)
n A minimum of 4 CPUs
n A minimum 8 GB of RAM
n A minimum 110 GB Disk
n A DHCP server must be available on the network on which the server is running
for a Backup & Recovery manager deployment
Backup & Recovery Manager server installation requirements

The Backup & Recovery Manager server (OVA) raw database is a temporary buffer
for storing messages until they are processed.
Near the end of a Hyper_V or physical installation using ISO, the Backup & Recovery
Manager server post installation script displays a premature login prompt.
The following four post-install scripts run:
l 01_OS_post_script.sh
l 02_BRM_UPGRADER_post_script.sh
l 03_BRM_INSTALLER_post_script.sh
l 04_CLEANUP_post_script.sh
While the 3rd script (03_BRM_INSTALLER_post_script) is running, the security
patch installation of the new OS kernel displays a login prompt while the last of the
updates are applied. When the post-install scripts complete, a reboot occurs.
Disregard the login prompt and wait for the process to complete and reboot rather
than attempting to login at the prompt.
The following table provides Backup & Recovery Manager server memory
requirements.
Requirements 11
Table 4 Data storage requirements
Component Memory per component (disk space)

Memory 8 GB
Hardware requirements for the Hyper_V virtual machine provides the minimum disk
recommendations for the Backup & Recovery Manager server.
Hardware Requirements for the Hyper-V virtual machine

There are memory and storage requirements specific to the Backup & Recovery
Manager server installation in Hyper-V virtualization.
The following table lists the memory and storage requirements for the Hyper-V
machine.
Table 5 Hyper-V virtual machine requirements
Component Requirement
Operating System platforms Windows 2008 R2, Windows 2012, Windows 2012 R2.
Memory The Backup & Recovery Manager server requires a minimum

of 8200 MB of memory for Hyper-V configuration. However,
it is recommended to provide 8700 MB of memory for the
virtual machine to accommodate virtualization overhead.
Server storage l Provision the virtual machine with 2 IDE controllers (In
Hyper-V it is not possible to boot from a SCSI controller).
l Provision two hard drives to attach to Controller 0:
n Hard Drive 1 (operating system) requires a minimum
of 40 GB
n Hard Drive 2 (Mongodb) requires a minimum of 70 GB
l Connect the ISO image with Backup & Recovery Manager
to a CD drive on Controller 1.
BIOS Map the ISO image to the DVD drive on Controller 1. List CD
first in the Startup Order section in the BIOS tab for the
virtual machine by using the up/down arrows to adjust the
order. If this is set incorrectly, the virtual machine does not
find the ISO boot image to begin installation.
Network l A DHCP server must be available on the network on which

the Hyper-V server is running for a Backup & Recovery
Manager deployment.
l Ensure that the Enable virtual LAN identification option is
not checked (enabled) in the Network Adapter tab for the
virtual machine. If this option is enabled, it interferes with
the virtual machine’s ability to correctly use DHCP
protocols.
System requirements
The following table lists the recommended and minimum required memory, CPU, and
disk for the Backup & Recovery Manager server components.
Table 6 Non-clustered memory, CPU, and disk
Memory CPU Disk

Recommended 8 GB 4 core, 2 GHz 1 TB
Minimum required 8 GB 4 core, 2 GHz 500 GB
Thin provisioning is an alternative for storage capacity for virtual disk allocation.
The following lists the available formats in which to store the virtual disk:
l Thick Provision Lazy Zeroed: (recommended) - Lazy Zero can take some time to
initialize, although not as long as Eager Zero. The storage capacity for the entire
virtual disk is allocated on the datastore at virtual disk create time if thick
provisioning is selected. Thick provisioning does not fill the whole drive unless
eager zeroed is selected.
l Thick Provision Eager Zeroed: Eager Zero yields the best performance, but also
takes the most time to initialize. Pre-zeros all blocks on of the virtual disk on the
datastore in advance.
l Thin Provision: Thin provisioning means that the capacity on the datastore is
allocated to the virtual disk as required, up to the full size of the virtual disk and
only uses what it needs. This is the fastest to initially deploy, but it is possible to
over-allocate the datastore and if a co-resident VM fills up disk, space on the
datastore can be exhausted and cause the other VMs using it to be blocked until
space is released. If you choose this option make sure you do not over allocate disk
in the datastore selected.
Considerations for the Backup & Recovery Manager server

l The Backup & Recovery Manager server experiences minimal stress while it
processes messages from the Data Domain servers. The Backup & Recovery
Manager server receives alerts messages from the Data Domain server's view
SNMP mechanism.
l The recommended retention period for database data is 1 year which is also the
default setting in the server Preferences. However, if a 1 year retention period is
not required, consider reducing the setting to 6 months. Searching through less
records can significantly reduce the UI response time.
Factors for future capacity planning

There are factors available to assist with disk, network, CPU and database capacity
planning.
l With each 100,000 completed backups, the database size on the disk increased by
approximately 900 MB. This increased amount of database disk can be used to
estimate the remaining capacity of the database.
System requirements 13
l While the 100,000 backup activities are running, the maximum network usage
reached 17 mbps. This network usage observation can be used in the network
capacity planning.
l While the 200,000 backup activities are running, the maximum network usage
reached 35 mbps. This network usage observation can be used in the network
capacity planning.
l The Backup & Recovery Manager server is on the CPU intensive side while it
processing the high volume backup activity messages. Adding more CPU's can
alleviate slow UI response times.
CHAPTER 2
Sizing, Performance and Best Practices
This chapter includes the following topics:
l CPU, memory and database augmentation for the Backup & Recovery Manager
server................................................................................................................. 16
l Configuring the Backup & Recovery Manager VM..............................................16
Sizing, Performance and Best Practices 15

CPU, memory and database augmentation for the Backup &

Recovery Manager server
The procedures in this section assume that the following conditions are true for CPU,
memory and disk allocation on the following:
l ESXi
l ESX 5.1, 5.5 and 6.0
l VCenter Server 5.0 and 6.0
l VSphere Client 5.0 and 5.1
l Native installer for SLES Linux:
n Bootable ISO image requires a minimum of 3.3 GB free space on any of the
following:
– Network PXE server
– USB/DVD
n 2 disks (operating system and MongoDB disks)
n A minimum of 4 CPUs
n A minimum 8 GB of RAM
n A minimum 110 GB Disk
n A DHCP server must be available on the network on which the server is running
for a Backup & Recovery manager deployment
Configuring the Backup & Recovery Manager VM

You can create the VM for which to run the Backup & Recovery Manager server and
configure it to optimize performance and minimize resource use.
Procedure
1. Download Backup & Recovery Manager ova file.
2. Deploy the VM on the ESX by using a vCenter web client. The Backup &
Recovery Manager User Guide provides details.
3. Ensure that the Backup & Recovery Manager adaptor is capable of working on a
1 Gbps network.
4. Before starting the Backup & Recovery Manager server on the VM, configure
the following VM resources:
a. Configure memory
b. Configure the CPU
c. Configure the virtual hard disk for the MongoDB
Configuring memory
Before you begin
The Backup & Recovery Manager virtual machine must be offline before completing
this procedure.
Procedure
1. Log in to the vCenter ESX on which the Backup & Recovery Manager is hosted.
2. Right-click the Backup & Recovery Manager virtual machine.
3. Select Edit Settings > Virtual Hardware tab.
4. Click to expand Memory to set the parameters.
5. Set RAM as required in the RAM field. You can use 8192 MB, which is the
default.
6. Set Reservation to 8192 MB, and Limit to 0 to fix the RAM allocation for this
virtual machine
Note
Backup & Recovery Manager virtual machine should have a fixed RAM
allocation for Backup & Recovery Manager virtual machine. It cannot be shared.
Configuring CPU
Before you begin
The Backup & Recovery Manager virtual machine must be offline before completing
this procedure.
Procedure
2. Right-click the Backup & Recovery Manager virtual machine.
4. Click to expand CPU to set the parameters.
5. Set the required CPU number in CPU to 4. The default is 4.
6. Set Cores per socket to 2 or 4. The default is 2.
7. Set Reservation value and Limit to have a fixed CPU for this virtual machine.
To fix the CPU for this virtual machine, use the following calculation:
The number of vCPU (in this case 4x2=8) * (CPU frequency in MHz)
= Reservation value in MHz
Configuring the virtual hard disk for Backup & Recovery Manager server
MongoDB
After configuring the virtual disk for the MongoDB, more disk space can be
augmented by either extending an existing virtual disk, or adding a new virtual disk.
Before you begin
The Backup & Recovery Manager VM must be offline before completing this
procedure.
Procedure
2. Right click the Backup & Recovery Manager VM.
By default two disks will are created for Backup & Recovery Manager:
Configuring CPU 17
l 40 GB for system space

l 70 GB for database space
Expand the Mongo database space

To expand the Backup & Recovery Manager database (MongoDB) space, use the
Logical Volume Manager (LVM).
This example describes how to add a 50 GB volume to the appliance. The size of the
volume added by this method can be changed as required.
Procedure
1. Log in as root.
2. Allocate an additional LUN for Backup & Recovery Manager appliance virtual
machine, and then select Edit Settings > Hardware > Add within VMware
vsphere management wizard:
a. Allocate a new disk.
b. Create a virtual disk.
c. Set a capacity of 50 GB/Thick or Thin Provisioned/Store with the virtual
machine.
d. Continue the rest of the wizard by accepting the defaults.
e. To view the new hard disk, click Finish.
The new disk appears in bold font.
f. To make the new disk visible, restart or rescan.

3. Add the additional disk online:
a. Type the following command:
echo "- - -" > /sys/class/scsi_host/host0/scan
b. To view the new 50 GB LUN, restart.

c. To confirm that the disk is added, type the following command:
fdisk -l
4. Partition the new disk:

a. Create a partition table with a single partition using all the space on the new
disk /dev/sdc.
Note
For this example, the new disk is device /dev/sdc.
b. Set its type to be 8E (LVM):
fdisk /dev/sdc
Output that is similar to the following appears:
Device contains neither a valid DOS partition table, nor Sun,

SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0x89574522.
Changes will remain in memory only, until you decide to write
them.
After that, of course, the previous content won't be
recoverable.
The number of cylinders for this disk is set to 6527.
There is nothing wrong with that, but this is larger than
1024,and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of
LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be
corrected by w(rite)
Command (m for help): p
Disk /dev/sdc: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x89574522
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p
primary partition (1-4)
p Partition number (1-4): 1
First cylinder (1-6527, default 1):
Using default value 1
Last cylinder, +cylinders or +size{K,M,G} (1-6527, default
6527):
Using default value 6527
Command (m for help): t
Selected partition 1
Hex code (type L to list codes): 8e
Changed system type of partition 1 to 8e (Linux LVM)
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
Note
8E (LVM) is a code on the disk partition area that indicates that Linux LVM
manages the partition.
5. To make the new partition and LUN available to LVM, type the following
command:
pvcreate /dev/sdc1
No physical volume label read from /dev/sdc1 Physical volume

"/dev/sdc1" successfully created
Configuring the virtual hard disk for Backup & Recovery Manager server MongoDB 19
6. To determine the logical volume name to be expanded, type the following

command:
lvdisplay -a
--- Logical volume ---

LV Name /dev/datavg/data
VG Name datavg
LV UUID umR8l8-0Qos-qcqN-PepC-mguj-1Fo8-Oq2bav
LV Write Access read/write
LV Status available
# open 1
LV Size 69.91 GB
Current LE 2237
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 1024
Block device 253:0
Note
The LV Name contains the name of the logical volume that is provided as part of
the expanded appliance.
7. To determine the size of the logical volume name, type the following command:
vgdisplay -s
"datavg" 69.97 GB [69.91 GB used / 64.00 MB free]
8. To add the LUN to the datavg volume group, type the following command:
vgextend datavg /dev/sdc1
Volume group "datavg" successfully extended
9. To extend the logical volume containing the file system to include the new LUN,
type the following command:
lvextend /dev/datavg/data /dev/sdc1
Extending logical volume data to 119.88 GB Logical volume data

successfully resized
10. To grow the XFS file system containing the database, type the following
command:
/usr/sbin/xfs_growfs /data01
meta-data=/dev/mapper/datavg-data isize=256 agcount=4,

agsize=4581376 blks = sectsz=512 attr=2 data = bsize =4096
blocks=18325504, imaxpct=25 = sunit=0 swidth=0 blks naming =
version 2 bsize=4096 ascii-ci=0 log =internal bsize=4096
blocks=8948, version=2 = sectsz=512 sunit=0 blks, lazy-count=1
realtime = none extsz=4096 blocks=0, rtextents=0 data blocks
changed from 18325504 to 31424512
11. Verify that 50GB is added to the existing 70 GB file system by using the
following command:
df -h /data01
Filesystem Size Used Avail Use% Mounted on /dev/mapper/datavg-

data 120G 1.5G 119G 2% /data01
12. To add additional data retention, repeat this procedure.
Configuring the virtual hard disk for Backup & Recovery Manager server MongoDB 21

Docu59612 Backup and Recovery Manager 1.3 Sizing and Configuration Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Docu59612 Backup and Recovery Manager 1.3 Sizing and Configuration Guide

Enviado por

Direitos autorais:

Formatos disponíveis

EMC Backup & Recovery Manager

Sizing and Configuration Guide

Published August 2017

Chapter 1 Considerations and recommendations 9

Chapter 2 Sizing, Performance and Best Practices 15

As part of an effort to improve product lines, periodic revisions of software and

Revision Date Description

Expand the Mongo database space on page 18

Identifies content that warns of potential business or data loss.

Contains information that is incidental, but not essential, to the topic.

Table 2 Style conventions

Monospace italic Used for variables.

[] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means or

{} Braces enclose content that the user must specify, such as x, y, or z.

... Ellipses indicate non-essential information that is omitted from the

Where to get support

4. (Optional) To add the product to My Saved Products, in the product specific

To review an open service request:

l Backup & Recovery Manager deployment sizing recommendations................... 10

Considerations and recommendations 9

Backup & Recovery Manager deployment sizing

Table 3 Backup & Recovery Manager deployment recommendations

Level 2 Up to 200,000 8 16 GB 2 TB 1 year 35 Mbps

Backup & Recovery Manager server software requirements

Backup & Recovery Manager server installation requirements

Table 4 Data storage requirements

Component Memory per component (disk space)

Hardware Requirements for the Hyper-V virtual machine

Table 5 Hyper-V virtual machine requirements

Memory The Backup & Recovery Manager server requires a minimum

Network l A DHCP server must be available on the network on which

Table 6 Non-clustered memory, CPU, and disk

Memory CPU Disk

Minimum required 8 GB 4 core, 2 GHz 500 GB

Considerations for the Backup & Recovery Manager server

Factors for future capacity planning

This chapter includes the following topics:

Sizing, Performance and Best Practices 15

CPU, memory and database augmentation for the Backup &

Configuring the Backup & Recovery Manager VM

l 40 GB for system space

Expand the Mongo database space

f. To make the new disk visible, restart or rescan.

echo "- - -" > /sys/class/scsi_host/host0/scan

b. To view the new 50 GB LUN, restart.

4. Partition the new disk:

For this example, the new disk is device /dev/sdc.

b. Set its type to be 8E (LVM):

Output that is similar to the following appears:

Device contains neither a valid DOS partition table, nor Sun,

Output that is similar to the following appears:

No physical volume label read from /dev/sdc1 Physical volume

6. To determine the logical volume name to be expanded, type the following

Output that is similar to the following appears:

--- Logical volume ---

Output that is similar to the following appears:

"datavg" 69.97 GB [69.91 GB used / 64.00 MB free]

vgextend datavg /dev/sdc1

Output that is similar to the following appears:

Volume group "datavg" successfully extended

lvextend /dev/datavg/data /dev/sdc1

Output that is similar to the following appears:

Extending logical volume data to 119.88 GB Logical volume data