Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Some article numbers may have changed. If this isn't what you're looking for, try searching all articles. Search articles

Article Number: 000187566

NetWorker Virtual Edition: How To Expand /data01 Partition (EXT3)

Summary: This Article describes how to increase the /data01 partition size on a NetWorker Virtual Edition server when /data01 is an an ext3 partition.

This article may have been automatically translated. If you have any feedback regarding its quality, please let us know using the form at the bottom of this page.

Article Content

Instructions

NOTE: This process is not intended or appropriate for standard technical support. If you require assistance, please reach out to your Dell Site Account Manager (SAM) or Dell Site Sales Rep to engage with our Global Professional Services (PS) team.

This Article describes how to increase the /data01 partition size on a NetWorker Virtual Edition (NVE) server. Since the index database is stored on the /data01 partition, environments where clients have large file structures or long retention policies can lead to increased disk space requirements. 

To identify the file system type of the NVE run the following command from ssh session: mount
The output will list all the mountpoints but data01 will show:
/dev/sdb1 on /data01 type ext3 (rw,noatime,data=ordered)

If filesystem is XFS, see: NetWorker Virtual Edition: How to increase /data01 partition size (XFS)
NOTE: Older NVEs (19.3.x) and older deployed with EXT3 /data01 file systems, Newer NVEs (19.4.x) and later deployed with XFS /data01 file systems.
 

Process:

To increase the size of this partition on your NVE server:
  1. Increase the Hard Disk 2 disk size for your NVE VM in vCenter and snapshot the VM.
NOTE: The NVE will need to be powered off. The option to increase disk size may be greyed out if snapshots exist.
 
  1. Create a VMware snapshot of the NVE and power it up.
NOTE: This snapshot can be deleted once the disk expansion is complete and the NVE/NetWorker is in operational state.
  1. Once the VM has rebooted open an SSH session to the NVE VM
  2. Switch to the root user by running: sudo su -
  3. Run the following commands to stop NetWorker services by running:
nsr_shutdown
systemctl stop networker
 
  1. Once services have stopped, unmount the /data01 partition: umount /data01
  2. Use the YAST curses utility by running entering yast on the command line.
  3. Use Tab to change frame or menu, and arrow keys to select within a frame, and Enter to confirm: Tab to System frame, use arrows to select Partitioner and confirm with Enter.
  yast2 command line console showing Partitioner tool
  1. Partitioner frame will reflect /dev/sdb the size increase to Hard Disk 2 in VMware; /dev/sdb1 is the current size of the /data01 partition.
kA5j00000008XsrCAE_1_1
  1. Change to the Available storage on host frame and select /dev/sdb1.
yast2 showing sdb1 device settings
  1. Confirm to see a summary of the device. Change to Resize menu option and confirm.
kA5j00000008XsrCAE_1_3
  1. The default option is set to Maximum Size. This option should retrieve the newly changed size from VMware. Ensure that the Maximum Size option is selected and select OK.
yast2 sdb1 device resize 
 
The new size will appear in the summary screen:
 
yast2 showing expanded disk size in expert partitioner
  1. Confirm Finish and review the summary indicating that the partition /dev/sdb1 will be extended:
yast2 showing partitioner summary
  1. Confirm Finish when finished reviewing the summary to proceed.
  2. Once progress window completes, select Next and confirm.
  3. Select Quit and confirm at  the main YAST menu.
  4. Remount the /data01 partition: mount /data01
  5. Start NetWorker services by running:
systemctl start networker
  1. Confirm nsrd, nsrexecd,and gstd have started:
root@nve:~/#: ps -ef | grep "nsrd\|nsrexecd\|gstd\|nsrjobd\|nsrindexd"
root     11773     1  0 10:17 ?        00:00:00 /usr/sbin/nsrexecd
root     11964 11804  0 10:17 ?        00:00:02 /usr/sbin/nsrd
root     12044 11964  0 10:17 ?        00:00:00 /usr/sbin/nsrindexd
root     12048 11964  0 10:17 ?        00:00:00 /usr/sbin/nsrdispd
root     12055 11964  0 10:17 ?        00:00:00 /usr/sbin/nsrjobd
root     12621     1  0 10:20 ?        00:00:00 /opt/lgtonmc/bin/gstd
root     12761 11082  0 10:22 pts/0    00:00:00 grep nsrd\|nsrexecd\|gstd\|nsrjobd\|nsrindexd
  1. The output of df -h will reflect the increased /data01 partition size
root@nve:~/#: df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda2        16G  4.0G   12G  27% /
udev            3.9G  120K  3.9G   1% /dev
tmpfs           3.9G     0  3.9G   0% /dev/shm
/dev/sda1      1011M   63M  898M   7% /boot
/dev/sda6       7.6G  244M  6.9G   4% /var
/dev/sda8        62G  774M   58G   2% /space
/dev/sdb1        60G  840M   56G   2% /data01

Additional Information

Realtime rendering, log rollover by size, and number of copies can be modified for NetWorker's /nsr/logs/daemon.raw and the NMC's /opt/lgtonmc/gstd.raw. These settings are not enabled by default. The daemon.raw is on the NVEs disk 2 under /data01/nsr/logs. The NMC's gstd.raw is on disk 1 under the NVE's root (/) partition /opt/lgtonmc/logs.

NetWorker: How to automatically render daemon.raw to daemon.log in real time
 
NOTE: Under some troubleshooting actions, the /nsr/res/nsrladb is renamed. If the nsrladb is renamed/deleted a new one will be created during service startup. These settings will be reverted to default.

 Another method to configure log rollover, which will persist even if nsrladb is renamed is to configure logrotate settings on the NVE's operating system for the NetWorker service log files.

vi /etc/logrotate.conf

add the following lines: 
# 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 will be rotated every week. Other possible values are daily and monthly.
  • rotate 5 indicates that only 5 rotated logs should be kept. The oldest file will be 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
  • Additional options can be found in the logrotate man page. https://linux.die.net/man/8/logrotate image.png
NOTE: The above example is not a recommendation on how many rotate cycles should be set, or how often this rotation should be done. This will need to be determined by the backup/NVE administrator. If logs need to be retained for longer periods of time, consider creating a NetWorker client for the NVE to backup the /nsr/logs directory through a NetWorker Protection Policy.

Article Properties

Affected Product

NetWorker

Last Published Date

03 Oct 2023

Version

6

Article Type

How To

Back to Top