Forum Discussion

joefreyatatado's avatar
joefreyatatado
Level 3
10 years ago

Netbackup Hyper-V Host Resource Requirements

Hi All,   I would like to ask what is the requirements of hyper-v host when we will backup a VM. like (CPU, RAM, etc) I know it will use some resources while running a backup. We will try the h...
Agent for Microsoft Hyper-V
Backing Up
Backup and Recovery
Best Practice
Compatibility
NetBackup
Not Applicable
Performance
Virtualization
  • sdo's avatar
    sdo
    10 years ago

    My advice is to start with one backup, and then slowly increase.  What I have noticed is that just running a few Hyper-V backups per Hyper-V host that the CPU and RAM are hardly touched, the issue, as ever is with disk throughput.  This is why it is quite important to have a good perfmon running, with the useful items being monitored such as read and write disk queues, read and write response times, read and write bytes per second, read and write average transaction (IO) size.  Don't choose the combined stats (i.e. the stats which are the combined read plus write) as you won'tbe able to distinguish the read traffic from the write traffic.

    Will your Hyper-V hosts be purely clients?  i.e. not performing the backup write to disk or tape storage, i.e. not what might be termed SAN media servers?   Are they what would be termed 'Enterprise Client' i.e. purely forming the backup and sending over the LAN to a media server or storage server?  If your Hyper-V hosts will also be acting as media server and doing the backup storage writes, then you will notice more CPU and RAM consumption.

    Pay careful attention to the fact that a Hyper-V VM backup with file indexing (i.e. allow individual file restore) will consume more NetBackup catalog space.

sdo's avatar
sdo
Moderator
10 years ago

My advice is to start with one backup, and then slowly increase.  What I have noticed is that just running a few Hyper-V backups per Hyper-V host that the CPU and RAM are hardly touched, the issue, as ever is with disk throughput.  This is why it is quite important to have a good perfmon running, with the useful items being monitored such as read and write disk queues, read and write response times, read and write bytes per second, read and write average transaction (IO) size.  Don't choose the combined stats (i.e. the stats which are the combined read plus write) as you won'tbe able to distinguish the read traffic from the write traffic.

Will your Hyper-V hosts be purely clients?  i.e. not performing the backup write to disk or tape storage, i.e. not what might be termed SAN media servers?   Are they what would be termed 'Enterprise Client' i.e. purely forming the backup and sending over the LAN to a media server or storage server?  If your Hyper-V hosts will also be acting as media server and doing the backup storage writes, then you will notice more CPU and RAM consumption.

Pay careful attention to the fact that a Hyper-V VM backup with file indexing (i.e. allow individual file restore) will consume more NetBackup catalog space.