NetBackup installation drive is almost full
Hi Experts,
Good day!
I would like to ask for your recommendation on how to reclaim disk space to my C: Drive which is the NetBackup Installation Drive. There's some issues prompting on our NetBackup Master Server.
We are looking to expand the C: Drive since it is VM, are you agree with that strategy?
Hoping for replies.
Thank you and best regards!
Jonas
It is possible to move parts of the catalog database to another volume (by leaving a pointer behind) but then you may have to extend the new volume too someday. Instead, I agree with you, these days with VMs the notion of separate volumes just isn't that relevant anymore, and so I'd take the easy option and just expand the C: volume.
if [installation_path]/netbackup/db/ is located on C drive, then it is expected to consume space as time go, becuase Netbackup records backup information in that location.
If free space go below a certain percentage, Netbackup will stop working in order to protect the EMM database.
So, yes, I agree. Extend the C drive.
Its a Virtual Machine right, so take a snapshot or an export beforehand...
Andrew
Another option would be to move NBU image catalog to another drive.
See this TN for instructions: https://www.veritas.com/support/en_US/article.100037920You need stop NBU for this.
Using SCVMM 2016 for cluster of Hyper-V 2012 R2 with test guest VM of Windows 2012 R2, gen2, thin vhdx.
I have just sucessfully tested expanding (in Hyper-V) and then extending (inside guest) both C: and another volume, live, on-line - without having to shutdown.
Also, was then able to reduce size of both C: and another volume, live on-line inside the same guest - but SCVMM is not able to shrink, and so I had to use Failover Cluster Manager (not Hyper-V Manager) to shrink the VHDX provisioned sizes back down - again without having to shutdown the guest VM.
A bit late for this system, but I wouldn't install any appliacations (well, big ones) on C:\
NBU should really go on <some other > drive and arguably, I'd seperate out the logs and catalog / NBDB as well.
When using a proper operating system ;0) , I would do something like this as sepearate file systems
/usr/openv/
/usr/openv/logs/
/usr/openv/netbackup/logs/
/usr/openv/db
/usr/openv/netbackup/db/images
I would also consider which disks are underneath the filesystems - you don't want everything on the same disk as the OS ...
