Could you run df -h?
It'll output something like this
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/systemvg-root 209G 167G 34G 84% /
udev 12G 4.0K 12G 1% /dev
tmpfs 2.4G 292K 2.4G 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 12G 0 12G 0% /run/shm
/dev/sda1 228M 49M 167M 23% /boot
then in /usr/local/Enterasys_Networks/NetSight/backup/ run ls -lah
It'll output something like this:
/usr/local/Enterasys_Networks/NetSight/backup$ ls -lah
total 45G
drwxr-xr-x 8 root root 4.0K Apr 22 00:51 ./
drwxr-xr-x 17 root root 4.0K Mar 6 13:29 ../
drwxr-xr-x 2 root root 4.0K Jul 23 2012 backup/
drwxr-xr-x 5 root root 4.0K Apr 22 00:51 InventoryMgr/
-rw-r--r-- 1 root root 439M Apr 19 00:00 netsight_19042015.sql
-rw-r--r-- 1 root root 22G Apr 19 00:48 netsight_19042015.sql.rpt
-rw-r--r-- 1 root root 441M Apr 22 00:00 netsight_22042015.sql
-rw-r--r-- 1 root root 22G Apr 22 00:51 netsight_22042015.sql.rpt
drwxr-xr-x 2 root root 4.0K Dec 17 00:11 OneView/
drwxr-xr-x 2 root root 4.0K Dec 17 00:00 Purview/
So as shown, our reporting database is 22 gigs, when copying the database, the netsight server needs generally wants about double the space in addition to an extra few gigs of spare space, the database is constantly being written to and no space available may result in a crash.