The installation of Video Surveillance Operations Manager (VSOM) is very easy. You can use the OVF for VMWare.
How are you gonna add some extra harddisk space when you need it ? You can resize the VM Harddisk but it my case it gave the error :
So I added just an extra Harddisk in VMWare. Now you will have to login at the console of the VSOM (or SSH to it) with the localadmin account.
Let’s see if the partition was automaticly created :
[localadmin@VSM7 ~]$ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 8263884 1688776 6155320 22% / tmpfs 5582004 76 5581928 1% /dev/shm /dev/sda8 55388556 1318408 51256504 3% /mysql/data /dev/sda6 8263884 4785396 3058700 62% /usr/BWhttpd /dev/sda4 33026928 952332 30396824 4% /var /dev/sdb1 1572720640 1486254348 86466292 95% /media1
Nope. I don’t see the new partition.
[localadmin@VSM7 ~]$ mount /dev/sda2 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda8 on /mysql/data type ext3 (rw) /dev/sda6 on /usr/BWhttpd type ext3 (rw) /dev/sda4 on /var type ext3 (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) /dev/sdb1 on /media1 type xfs (rw,_netdev,noatime,nodiratime,logbufs=2) An of course it's not mounted either. [localadmin@VSM7 ~]$ ls /dev/sd* /dev/sda /dev/sda10 /dev/sda3 /dev/sda5 /dev/sda7 /dev/sda9 /dev/sdb1 /dev/sda1 /dev/sda2 /dev/sda4 /dev/sda6 /dev/sda8 /dev/sdb /dev/sdc
I do see the new harddisk. Hooray.. It’s a start. Start fdisk and create a new partition.
[localadmin@VSM7 ~]$ sudo fdisk /dev/sdc
Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First cylinder (1-200512, default 1): Using default value 1 Last cylinder, +cylinders or +size{K,M,G} (1-200512, default 200512): Using default value 200512
Let's verify the partition : Command (m for help): p
Disk /dev/sdc: 1649.3 GB, 1649267441664 bytes 255 heads, 63 sectors/track, 200512 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/sdc1 1 200512 1610612608+ 83 Linux
Command (m for help): w The partition table has been altered!
Calling ioctl() to re-read partition table. Syncing disks.
Let’s make a xfs filesystem on the partition :
[localadmin@VSM7 ~]$ sudo mkfs.xfs -f /dev/sdc1 meta-data=/dev/sdc1 isize=256 agcount=4, agsize=100663288 blks = sectsz=512 attr=2, projid32bit=0 data = bsize=4096 blocks=402653152, imaxpct=5 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal log bsize=4096 blocks=196607, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0
Make a directory to point to for the mount of the partition. [localadmin@VSM7 ~]$ sudo mkdir /media2
I changed to rights of the directory the same as /media1 (nobody:nobody)
[localadmin@VSM7 /]$ sudo chown nobody:nobody media2
Let’s mount the new harddisk :
[localadmin@VSM7 /]$ sudo mount -t xfs /dev/sdc1 /media2
This step is just to verify that it’s working.
No I wanted to edit /etc/fstab with the UUID… But how do you get the UUID of de partition :
[localadmin@VSM7 /]$ sudo blkid
/dev/sda2: UUID=”b23baf54-126b-4290-adbb-e24439983532″ TYPE=”ext3″
/dev/sda4: UUID=”f2a13152-e1c8-4d24-a3d5-ff6d23b9aea0″ TYPE=”ext3″
/dev/sda5: UUID=”7ef8ea0e-e5eb-415d-92d0-6f250ce1fd2c” TYPE=”swap”
/dev/sda6: UUID=”3462b125-9c6f-49bf-bbbb-76161a795efa” TYPE=”ext3″
/dev/sda8: UUID=”f53bcdf9-9e60-4b15-843d-a7051adb614c” TYPE=”ext3″
/dev/sdb1: UUID=”2364fb0a-1d05-4395-8768-3c8167bb18c7″ TYPE=”xfs”
/dev/sdc1: UUID=”15d1f6ee-4127-4c0e-bdcd-57fcfea6d64a” TYPE=”xfs”
After this information I edited the /etc/fstab with the same parameters like /media1
UUID=2364fb0a-1d05-4395-8768-3c8167bb18c7 /media1 xfs rw,noatime,
nodiratime,_netdev,logbufs=2 0 0
UUID=15d1f6ee-4127-4c0e-bdcd-57fcfea6d64a /media2 xfs rw,noatime,nodir
atime,_netdev,logbufs=2 0 0
And after a restart I noticed that my 2nd virtual harddrive is added to the total amount of free space for the recordings :
And VSOM is using the /mediax directory equally for the recordings. This is only for new recordings that are added after the expansion of the harddisk.
An easier approach is :
[localadmin@vsm-server ~]$ sudo su –
[root@vsm-server ~]# /usr/BWhttpd/bin/setup_media_storage
installation guide for VSOM 7.7 ova :
Thank you for this guide. It was very helpful for my situation.