NetWorker 9.1 Virtual Edition disk space requirements

Can anyone answer this question?

I guess not many run NWVE on this forum so your best bet is via support.

You cannot simply expand the disk if needed more spacing

Changing the storage disk configuration

Perform the following steps to configure the NVE to support higher performing and

larger capacity datastores.

Procedure

1. From the virtual machine console of the NVE appliance, perform the following

configuration tasks:

a. Use the su command to change to the root account.

b. Stop the NetWorker and NMC daemons:

Maintenance

Modifying passwords 35

/etc/init.d/networker stop/etc/init.d/gstd stop

c. Confirm that the NetWorker daemons are not running:

/etc/init.d/networker statusnsr_shutdown: There are

currently no running NetWorker

processes.

d. Disable NetWorker:

chkconfig gst off networker off

2. In the Vsphere Web Client, perform the following configuration tasks:

a. Right-click the appliance and select Edit Settings.

b. From the New Device list, select New Hard Disk, and then click Add.

c. Expand the New Hard disk option.

d. In the size field, type the size of the disk.

e. In the Disk Provisioning field, leave the option Thick provision lazy zero.

f. In the Disk Mode list, select Independent - Persistent.

g. Click OK.

3. From the virtual machine console of the NVE appliance, perform the following

configuration tasks:

a. Rescan the SCSI devices:

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

b. Verify that the new disk /dev/sdc appears on the system:

ls /dev/sd*

Output similar to the following appears:

/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/

sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sdb /dev/

sdb1 /dev/sdc

c. Partition the new disk.

For example:

parted -a minimal -s -- /dev/sdc mklabel msdos mkpart p ext3

1s -1s

d. Rescan the partition table:

partprobe

e. Confirm that the new disk partition /dev/sdc1 appears:

ls /dev/sd*

Output similar to the following appears:

dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/

sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sdb /dev/

sdb1 /dev/sdc /dev/sdc1

f. Create a file system on the partition/dev/sdc1:

mkfs.ext3 /dev/sdc1

Maintenance

36 EMC NetWorker 9.1 Virtual Edition Deployment Guide

g. Mount /dev/sdc1:

mkdir /tmpmnt mount/dev/sdc1 /tmpmnt

h. Stop the avinstaller:

avinstaller.pl --stop

i. Copy the contents from the old disk to the new disk:

cp -rfp /data01/* /tmpmnt/

j. Relabel the old and new disks:

e2label /dev/sdb1 dataolde2label /dev/sdc1 data01

k. Power off the NVE:

poweroff

4. After the NVE power off completes, use the vSphere Web Client to perform the

following configuration tasks:

a. Right-click the appliance and select Edit Settings.

b. Hover over Hard disk 2 and click the X button, do not select Delete files from

datastore. Click OK.

The following figure provides an example of the Edit Settings screen, when

deleting the disk device.

Figure 12 Deleting a disk device

5. Right-click the virtual machine and select Power > Power On.

6. From the VM console of the NVE appliance, perform the following configuration

tasks:

a. Type mount and verify that disk /dev/sdc1 is mounted on /data01.

For example, the mount output would include the following line:

/dev/sdc1 on /data01 type ext3 (rw,noatime)

b. Confirm that the avinstaller is started:

avinstaller.pl --test

Output similar to the following appears when the avinstaller has started:

Avistart process: 3311

c. Enable NetWorker and NMC:

chkconfig networker onchkconfig gst on

d. Start the NetWorker and NMC daemons:

/etc/init.d/networker start/etc/init.d/gstd start

e. Confirm that the NetWorker daemons have started, by typing the following

command:

Note

Before running this command, wait several minutes for the daemons to start.

For a NetWorker server, the nsrctld daemon starts. The nsrctld

daemon starts other processes that the NetWorker server requires. Output

similar to the following appears when the daemons are started:

+--o nsrctld (29021)

+--o epmd (29029)

+--o rabbitmq-server (29034)

+--o beam (29038)

+--o inet_gethost (29144)

+--o inet_gethost (29145)

+--o jsvc (29108)

+--o jsvc (29114)

+--o nsrd (29123)

+--o java (29135)

+--o nsrmmdbd (29828)

+--o nsrindexd (29842)

+--o nsrdispd (29853)

+--o nsrjobd (29860)

+--o nsrvmwsd (29968)

+--o connectemc (29131)

+--o eventservice.ru (29154)

+--o jsvc (29158)

+--o jsvc (29159)

+--o java (29838)

+--o node-linux-x64- (29885)

+--o nsrexecd (29004)

+--o nsrlogd (29899)

+--o nsrsnmd (30038)

7. Perform a backup and recovery operation. If NetWorker operations succeed,

use the vSphere Web Client to delete the old VMDK file:

a. Browse to the datastore that contains the VM files and expand the NVE

folder.

b. Select the VMDK file VM_name_2.vmdk, and then click the X button.

The following figure provides an example of the expanded NVE folder with

the old VMDK file selected.