Description: If all the storage drives are ISCSI, then “Recording Not Possible” is seen on the Storage page of the desktop client. If some storage drives are local, then recording only happens to local drives, thus reduces the overall content age of the oldest available video/audio.
Remove/rename/un-install archivepi.dll (windows) or archivepi.so (linux) in the installpath/plugins folder (note if renaming, must rename to NOT .dll extension or .so on Linux)
Start exacqVision server service/daemon
Fixed Version: 21.03.107 Back patched and available in 21.03.7
The S-series come defaulted for Archiving. This article will walk you through the steps of preparing the S-series for Extended Storage and assumes you have already configured the IP address of the S-series for your network.
Extended Storage relies upon an iSCSI connection to the S-series device. If using an exacqVision Server and exacqVision S-series storage device the iSCSI initiation is handled automatically. If using third-party hardware you will need to create the iSCSI initiation manually.<br>
Steps
Within the exacqVision Client, add the S-series connection. Navigate to the Add Systems page.<br> <br><br>
Click on the New button (A) and enter the IP address (B) of the S-Series unit, as well as the Username and Password (default admin/admin256). Click Apply.<br> <br><br>
With the S-Series unit now added to the navigation tree on the left, expand your options under this server name and go to the S-Series Storage settings page.<br> <br><br>
On the Network tab is a list of the Storage Volumes contained in the S-Series. The Type will be defaulted to None. The volumes in an S-Series may be of mixed types to achieve your desired storage configuration, so some volumes may be Archiving while others are Extended.<br> <br><br>
To change existing volumes to Extended, first change the Type column on your desired volumes to None and press Apply. Give the system a few minutes to complete the change.<br> Warning: Changing volume types will erase any existing data on the storage volume.<br> <br><br>
Change the Type of the desired volumes to Extended Storage (A). In the column labeled Server Address, enter the IP address of the exacqVision recording server (B). Press Apply. It may take a few minutes for the Status to cycle through the steps needed and finally display ‘OK’. There should now be an IQN listed in the Address column (C).<br> <br><br>
Return to the recording server’s Storage page and select the Extended tab.<br> <br><br>
Under the Portals section, enter the IP address of the S-Series system. Leave the port as 3260 and click the Add button.<br> <br><br>
The S-Series will be scanned and a list of Targets will appear.<br> <br><br>
Place a check mark in the Enabled column for each Target. If using an exacqVision S-Series, you will not need to enter a Username or Password. Press the Apply button.<br> <br>* Username and Password are required for use with third-party iSCSI hosts. Exacq support cannot provide assistance in setup or troubleshooting third-party iSCSI hosts or devices.<br><br>
After pressing Apply, each of the Targets will be prepared. As they finish preparing they will appear in the Partitions panel below.<br> <br><br>
Once the Status in the Partitions panel is ‘OK’, a Mount point will also be displayed. This indicates the Target on the S-Series is now being seen on the local recording server as if it were a local drive.<br> <br><br>
Return to the Drive tab on the recording server and your new Extended Storage drives should now appear in the Drive list.<br> <br>* The above image is an example from a Linux/Ubuntu system. On a Windows system, the Drive names will appear as letters (e.g. – C, D, E, F, etc.)<br><br>
Early versions of exacqVision systems with the Windows Embedded operating system did not have support for iSCSI. These systems were manufactured in in January and early February 2014.
To determine whether a system supports iSCSI, complete the following steps:
Open the Start menu.
Right-click Computer.
Select Manage from the pop-up menu.
Double-click Services and Applications.
Double-click Services.
If Microsoft iSCSI Initiator Service is not running, start it.
Click Device Manager.
Expand the Storage Controllers node if necessary.
If you do not see Unknown Device, your system supports iSCSI.
If you do see Unknown Device, right-click it, select Properties, select Details, and select Hardware IDs. If the value is ROOT\ISCSIPRT, your system does not support iSCSI.
To enable iSCSI support on the system, complete the following steps:
Download iSCSIPack.zip from https://exacq.com/files and unzip it to a flash drive or directly to the exacqVision system.
On the exacqVision system, navigate to the directory containing the unzipped installation files.
Double-click the install.bat file.
The installer prompts for administrator rights, installs the files, and restarts the system.
When upgrading a Linux-based exacqVision server to exacqVision 5.8, the existing mount point for an active iSCSI connected drive might not be recognized. To work around this issue, complete the following steps after the upgrade is complete:
<br>
Using exacqVision Client 5.8, open the Storage page for the upgraded server.
Select the Extended tab.
Look for your iSCSI connection and corresponding mount paths. If they appear as expected, no further action is necessary. Otherwise, continue with the following step.
Note the mount paths that appear on the Extended tab. The example above shows /mnt/edvr/11/ (and three other mounts).
On the Drive tab, deselect the recording drives listed on the Extended tab. Click Apply to disable recording to those mount paths.
Ensure that the originally configured iSCSI mounts are still enabled for recording.
On the server, run sudo /etc/init.d/edvrserver stop in Terminal.
Use the mount command to determine the device name of the iSCSI mount point. The output will look similar to this: /dev/sdb1 on / type ext4 (rw,errors=remount-ro) proc on /proc type proc (rw,noexec,nosuid,nodev) /dev/sdc1 on /mnt/edvr/4 type ext4 (rw,_netdev,errors=remount-ro) /dev/sdd1 on /mnt/edvr/5 type ext4 (rw,_netdev,errors=remount-ro)
Note the /dev/sdxx device name that corresponds to the /mnt/edvr/x mount path from earlier in the procedure.
Run blkid -o value -s UUID /dev/sdc1 (substituting your device’s name for /dev/sdc1) to determine the UUID for the device.
Open the /etc/fstab file for editing. Find the entry that specifies the iSCSI UUID. Change the mount point in the entry to the pre-upgrade configuration. For example, if the UUID= entry contains /mnt/edvr/4, change the “4” to “2.”
Delete the fstab entry created for the iSCSI device before the upgrade. The file will have multiple entries for the mount point; keep the one specifying UUID, and delete the other, which will look similar to /dev/sdc1 /mnt/edvr/2 ext4 _netdev.errors=remount-ro 0 0.
Save all changes.
Continue to edit the fstab file for each iSCSI drive on the system.
Run sudo mount -a to reload the fstab file.
Open /usr/local/exacq/server and delete archivepi.xml and psfpi.xml.
Run sudo /etc/init.d/edvrserver start.
<br>
exacqVision Client should now display the correct mount paths on the Extended tab on the Storage page.
The Windows version of ExacqVision Server must record directly to drives that Windows identifies as fixed drives, such as iSCSI drives.
Network-attached storage (NAS), or mapped drives, cannot be used for direct recording because the ExacqVision system cannot detect whether the drives are being used for other purposes. Such conflicts can cause recording issues on the ExacqVision system.
However, you can archive to NAS (network-attached storage) drives. More information can be found in the ExacqVision User Manual, which can be downloaded here.
The settings for the storage device iqn.2001-04.com.example:storage.lun1 on 192.168.0.101:3260,1 are stored in the file /etc/iscsi/nodes/iqn.2001-04.com.example:storage.lun1/192.168.0.101,3260,1/default.
<br>
We need to set the username and password for the target in that file; instead of editing that file manually, we can use the iscsiadm command to do this for us:
server1:~# iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --login Logging in to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260] Login to [iface: default, target: iqn.2001-04.com.example:storage.lun1, portal: 192.168.0.101,3260]: successful server1:~#
<br>
… or by restarting the initiator:
sudo /etc/init.d/open-iscsi restart
<br>
(If you want to log out, you can run iscsiadm -m node --targetname "iqn.2001-04.com.example:storage.lun1" --portal "192.168.0.101:3260" --logout)
<br>
If your iSCSI device has already been formated, and contains data, please skip to Mounting your drive.
<br>
Continue on ONLY if your device is being set up for the first time, or you instructed to do so by tech support.
<br>
In the output of
<br>
sudo fdisk -l
<br>
you should now find a new hard drive (/dev/sdb in this example); that’s our iSCSI storage device:
<br>
server1:~# fdisk -l
Disk /dev/sda: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00031334
Device Boot Start End Blocks Id System /dev/sda1 * 1 3749 30113811 83 Linux /dev/sda2 3750 3916 1341427+ 5 Extended /dev/sda5 3750 3916 1341396 82 Linux swap / Solaris
Disk /dev/sdb: 21.4 GB, 21474836480 bytes 64 heads, 32 sectors/track, 20480 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk identifier: 0x00000000
Disk /dev/sdb doesn't contain a valid partition table server1:~#
<br>
To use that device, we must format it (replace /dev/sdX with the value obtained from the last command):
<br>
sudo fdisk /dev/sdX
<br>
server1:~# fdisk /dev/sdb Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0x882944df. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won’t be recoverable.
<br>
The number of cylinders for this disk is set to 20480. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
<br>
Command (m for help): <– m Command action a toggle a bootable flag b edit bsd disklabel c toggle the dos compatibility flag d delete a partition l list known partition types m print this menu n add a new partition o create a new empty DOS partition table p print the partition table q quit without saving changes s create a new empty Sun disklabel t change a partition’s system id u change display/entry units v verify the partition table w write table to disk and exit x extra functionality (experts only)
<br>
Command (m for help): <– n Command action e extended p primary partition (1-4) <– p Partition number (1-4): <– 1 First cylinder (1-20480, default 1): <– ENTER Using default value 1 Last cylinder or +size or +sizeM or +sizeK (1-20480, default 20480): <– ENTER Using default value 20480
<br>
Command (m for help): <– t Selected partition 1 Hex code (type L to list codes): <– L
<br>
0 Empty 1e Hidden W95 FAT1 80 Old Minix be Solaris boot 1 FAT12 24 NEC DOS 81 Minix / old Lin bf Solaris 2 XENIX root 39 Plan 9 82 Linux swap / So c1 DRDOS/sec (FAT- 3 XENIX usr 3c PartitionMagic 83 Linux c4 DRDOS/sec (FAT- 4 FAT16 <32M 40 Venix 80286 84 OS/2 hidden C: c6 DRDOS/sec (FAT- 5 Extended 41 PPC PReP Boot 85 Linux extended c7 Syrinx 6 FAT16 42 SFS 86 NTFS volume set da Non-FS data 7 HPFS/NTFS 4d QNX4.x 87 NTFS volume set db CP/M / CTOS / . 8 AIX 4e QNX4.x 2nd part 88 Linux plaintext de Dell Utility 9 AIX bootable 4f QNX4.x 3rd part 8e Linux LVM df BootIt a OS/2 Boot Manag 50 OnTrack DM 93 Amoeba e1 DOS access b W95 FAT32 51 OnTrack DM6 Aux 94 Amoeba BBT e3 DOS R/O c W95 FAT32 (LBA) 52 CP/M 9f BSD/OS e4 SpeedStor e W95 FAT16 (LBA) 53 OnTrack DM6 Aux a0 IBM Thinkpad hi eb BeOS fs f W95 Ext'd (LBA) 54 OnTrackDM6 a5 FreeBSD ee EFI GPT 10 OPUS 55 EZ-Drive a6 OpenBSD ef EFI (FAT-12/16/ 11 Hidden FAT12 56 Golden Bow a7 NeXTSTEP f0 Linux/PA-RISC b 12 Compaq diagnost 5c Priam Edisk a8 Darwin UFS f1 SpeedStor 14 Hidden FAT16 <3 61 SpeedStor a9 NetBSD f4 SpeedStor 16 Hidden FAT16 63 GNU HURD or Sys ab Darwin boot f2 DOS secondary 17 Hidden HPFS/NTF 64 Novell Netware b7 BSDI fs fd Linux raid auto 18 AST SmartSleep 65 Novell Netware b8 BSDI swap fe LANstep 1b Hidden W95 FAT3 70 DiskSecure Mult bb Boot Wizard hid ff BBT 1c Hidden W95 FAT3 75 PC/IX Hex code (type L to list codes): <-- 83
<br>
Command (m for help): <– w The partition table has been altered!
<br>
Calling ioctl() to re-read partition table. Syncing disks. server1:~#
<br>
Afterwards, the output of
<br>
sudo fdisk -l
<br>
should look as follows:
<br>
server1:~# fdisk -l
<br>
Disk /dev/sda: 32.2 GB, 32212254720 bytes 255 heads, 63 sectors/track, 3916 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00031334
<br>
Device Boot Start End Blocks Id System /dev/sda1 * 1 3749 30113811 83 Linux /dev/sda2 3750 3916 1341427+ 5 Extended /dev/sda5 3750 3916 1341396 82 Linux swap / Solaris
<br>
Disk /dev/sdb: 21.4 GB, 21474836480 bytes 64 heads, 32 sectors/track, 20480 cylinders Units = cylinders of 2048 * 512 = 1048576 bytes Disk identifier: 0x882944df
<br>
Device Boot Start End Blocks Id System /dev/sdb1 1 20480 20971504 83 Linux server1:~#
<br>
Now we create a filesystem on /dev/sdb1…
<br>
sudo mkfs.ext3 /dev/sdX1
<br>
Issue the following command, and make note of the largest number listed< /p>
<br>
ls /mnt/edvr/
<br>
server1:~# ls /mnt/edvr 0 1 server1:~#
<br>
Mount the drive with the command below, substituting Y with the the largest number returned from the previous command + 1 (2 in our example)
<br>
sudo mount /dev/sdX1 /mnt/edvr/2
<br>
You should now see the new device in the outputs of…
sudo mount
<br>
server1:~# mount /dev/sda1 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sdX1 on /mnt/edvr/2 type ext3 (rw) server1:~#
To have the device mounted automatically at boot time, e.g. in the directory /storage, we create that directory…
<br>
mkdir /storage
<br>
… and add the following line to /etc/fstab:
<br>
sudo nano /etc/fstab
<br>
For test purposes, you can now reboot the system:
<br>
sudo reboot
<br>
After the reboot, the device should be mounted:
<br>
sudo mount
<br>
server1:~# mount /dev/sda1 on / type ext3 (rw,errors=remount-ro) tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755) proc on /proc type proc (rw,noexec,nosuid,nodev) sysfs on /sys type sysfs (rw,noexec,nosuid,nodev) udev on /dev type tmpfs (rw,mode=0755) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620) /dev/sdX1 on /mnt/edvr/Y type ext3 (rw,_netdev) server1:~#
Here’s a more complete breakout, with examples from another system with two volumes (vol1-test and vol2-test), each with two connection paths, to log in to:
NOTE: This just pulls in that target (vol1-test). Further, we could add by –p 10.3.15.164 in a second operation and pull in one other connection that the above did not add, for vol2-test on an IP basis (or, if this were the first operation, it would have added one connection to each volume). To turn off automatic binding for a given connection, you would use –v manual instead of -v automatic.
<br>
Also, none of this takes effect until the iSCSI daemon is restarted.
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br><br>
<br>* Username and Password are required for use with third-party iSCSI hosts. Exacq support cannot provide assistance in setup or troubleshooting third-party iSCSI hosts or devices.<br><br>
<br><br>
<br><br>
<br>* The above image is an example from a Linux/Ubuntu system. On a Windows system, the Drive names will appear as letters (e.g. – C, D, E, F, etc.)<br><br>
