This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!



I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!

Allow iSCSI extents with "NA" size

Post/Debate your Suggestions & Requests of XigmaNAS here. This ONLY pertains to XigmaNAS.
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
The1stImmortal
NewUser
NewUser
Posts: 1
Joined: 16 Jul 2012 01:04
Status: Offline

Allow iSCSI extents with "NA" size

Post by The1stImmortal »

Hi Folks,

We've been using NAS4Free in virtualized environments to pass tape drives through to backup servers - we configure either a physical box with a tape drive or pass a SAS/SCSI card through to a virtual NAS4Free instance, then configure iSCSI and add the tape device through manual config file editing to the UI. The (virtual) backup server then mounts the iSCSI tape device and away it goes.

Works brilliantly, actually.

The only downside is that by default NAS4Free ignores configured "disk" devices with size NA, which means you can't by default add the tape drives as extents through the web GUI.

We've been using a basic hack to get around this:

in /usr/local/www/services_iscsitarget_extent_edit.php
change lines 74 & 96 like so:

Code: Select all

              if (strcmp($size, "NA") == 0) continue;
to

Code: Select all

//              if (strcmp($size, "NA") == 0) continue;
If you could see your way to doing something like this in the stock code, or changing the "NA" size test to not apply to "sa" sequential access type devices, something like

Code: Select all

if ((preg_match("/^sa[0-9]/", $name)==0) && (strcmp($size, "NA") == 0)) continue;
, we'd much appreciate it.

Milkwerm
NewUser
NewUser
Posts: 1
Joined: 12 Nov 2012 03:49
Status: Offline

Re: Allow iSCSI extents with "NA" size

Post by Milkwerm »

Done the above and can see the tape drive (HP ultrium 3) how ever it always fails on verify (and restores) even if it claims to finish the backup successfully.
Definatley falls victim to the SPOUT/SPIN issues with Symantec Backup Exec.

Post Reply

Return to “Suggestions & Requests”