NetWorker Virtual Edition: How to Increase "data01" Partition Size

/dev/sdb1 on /data01 type xfs (rw,noatime,attr2,inode64,noquota)

Prerequisites:

1. Create a server bootstrap backup:
   1. From the NetWorker Management Console (NMC) or NetWorker Web User Interface (NWUI), perform a Server Protection backup job.
   2. Open an admin SSH session on the NVE and collect the bootstrap save set details: mminfo -B
   3. If bootstrap email notifications are not configured, copy the mminfo output off of the NVE and save in a file. Email notifications can be configured by following: NetWorker: How To Configure Policy Email Notifications
2. Stop all running NetWorker server services: nsr_shutdown
3. Disable NetWorker from starting up on the next OS boot: systemctl disable networker
4. From VMware, shut down the NVE Virtual Machine (VM) and Increase the Hard Disk 2 from the VM's settings.

5. Create a VMware snapshot of the NVE, then power it up.

Process:

1. Once the VM has started, open an SSH session to the NVE VM as admin.
2. Switch to the root user by running: sudo su -
3. Rescan the devices: echo 1 > /sys/block/sdb/device/rescan
4. Run fdisk against /dev/sdb this should show the current size and the size added in step 1:

nve:~ # fdisk -l /dev/sdb
GPT PMBR size mismatch (524287999 != 629145599) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/sdb: 300 GiB, 322122547200 bytes, 629145600 sectors
Disk model: Virtual disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 3C1FF651-B360-4218-9106-DE80B690EA2C

Device     Start       End   Sectors  Size Type
/dev/sdb1   2048 524285951 524283904  250G Microsoft basic data

5. Increase the /data01 partition by typing: growpart /dev/sdb 1

nve:~ # growpart /dev/sdb 1
CHANGED: partition=1 start=2048 old: size=524283904 end=524285952 new: size=629143519 end=629145567

6. Verify the file system by typing: xfs_growfs -d /data01
7. The partition should now show the expanded size: df -Th | grep "/data01"

nve:~ # df -Th | grep "/data01"
/dev/sdb1                                   xfs       300G  4.8G  296G   2% /data01

8. Start NetWorker server services: systemctl start networker
9. Re-enable automatic NetWorker service startup: systemctl enable networker

Some additional steps that can be followed to reduce disk usage used by log files.

Jobsdb retention

The jobsdb is a NetWorker database which holds a record of policy completion statuses, it also determines how long the /nsr/logs/policy/ and /nsr/logs/recover logs are retained. The default window is 72 hours. After 72 hours have passed for a given job, its jobdsb entries are removed and any associated log files are deleted. The jobsdb retention can be seen in nsradmin:

nve:~ # nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> show Jobsdb retention in hours
nsradmin> print type: nsr
   Jobsdb retention in hours: 72;

nsradmin> . type: nsr
Current query set
nsradmin> update Jobsdb retention in hours: 72
   Jobsdb retention in hours: 72;
Update? y
updated resource id 3.0.207.103.0.0.0.0.98.242.218.92.192.168.25.12(1489)

NMC:

Server and NMC logs

# NetWorker log files
/nsr/logs/daemon.log {
    rotate 5
    weekly
    create
    missingok
    compress
}

/nsr/logs/daemon.raw {
    rotate 5
    weekly
    create
    missingok
    compress
    delaycompress
}

/opt/lgtonmc/logs/gstd.log {
    rotate 5
    weekly
    create
    missingok
    compress
}

/opt/lgtonmc/logs/gstd.raw {
    rotate 5
    weekly
    create
    missingok
    compress
    delaycompress
}

• weekly this is the log rotation period; the logs are rotated every week. Other possible values are daily and monthly.
• rotate 5 indicates that only five rotated logs should be kept. The oldest file is removed on the subsequent run.
• missingok If the log file is missing, go on to the next one without issuing an error message.
• compress all rotated logs should be compressed.
• delaycompress can be used when some program cannot be told to close its logfile and thus might continue writing to the previous log file for some time
• Other options can be found in the logrotate man page. https://linux.die.net/man/8/logrotate