Comprehensive data protection for all workloads
Post Reply
mdm
Lurker
Posts: 2
Liked: never
Joined: Jun 24, 2009 3:45 am
Full Name: Douglas Munn
Contact:

Connecting to NAS as a LINUX server rather than through NFS

Post by mdm » Jun 24, 2009 4:32 am

I have a Thecus N8800 that I would like to connect to as an "Other" Linux server so that I can use FastSCP agents for my backups/restores. I've been using NFS but have problems with it disconnecting at times.

I have used FastSCP with Openfiler connecting to it as a Linux server very nicely, but the Thecus N8800 is being stubborn.

I like the N8800 (we are getting a second one) but Thecus want's it treated as a closed system. It appears to be a stripped down Debian distro. It doesn't have SSHD or Perl, so I installed modules on it that had SSHD and Perl 5.8.8. I also had to modify the path to add Perl in by default but that went well and works fine. I even used the Putty SCP client to load the Veeam modules to the to the Perl lib directories.

Still, when I try to connect to the N8800 it will sit for a while and then give me an error that it can't run Perl. I've gone through the .tar file for the agent and actually modified the script so that it points to the proper binary location in the shebang line, still I get an error that appears to be a command error.

Is there somebody who has experience with the code for the FastSCP agent install routine who could assist me with connecting to the the Thecus N8800 (both the PERL and the command line script - which I can't find). I'll send logs from my office in the morning.

BTW, I know that adding an SSH module and getting into the N8800 voids the warranty. :lol: It still is fun.

The Thecus is a very nice box, it would be nice to connect to it. They have at least three different models that are based on the same architecture and use virtually the same code.

Many thanks for anyone who can help.

Doug Munn

Gostev
SVP, Product Management
Posts: 24302
Liked: 3332 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Connecting to NAS as a LINUX server rather than through NFS

Post by Gostev » Jun 24, 2009 11:45 am

Doug, I really like what you are attempting to do :D

Can you please send us more information:
1. Veeam agent logs from /tmp/veeam_error* (something like this)
2. Shell logs
3. Kernel version

Thanks

mdmunn
Lurker
Posts: 1
Liked: never
Joined: Jun 02, 2009 3:07 pm
Full Name: Douglas Munn
Contact:

Re: Connecting to NAS as a LINUX server rather than through NFS

Post by mdmunn » Jun 24, 2009 11:36 pm

This is from the shell log.

[24.06.2009 15:16:25] <01> Info ------- Started new session of Veeam Shell -------
[24.06.2009 15:16:25] <01> Info Sql parameters: (local); VEEAM; VeeamBackup
[24.06.2009 15:16:26] <01> Info Current DB version is 62
[24.06.2009 15:16:26] <01> Info Trying to find update script in C:\Program Files\Veeam\Backup and FastSCP\DBUpdate.sql
[24.06.2009 15:16:26] <01> Info Update version is 62
[24.06.2009 15:16:27] <01> Info Expanding node: 'Backup' (6938fc8c-7450-4c9e-8760-baf3b8dbb0cc)
[24.06.2009 15:16:27] <01> Info Expanding node: 'Servers' ()
[24.06.2009 15:16:27] <01> Info Selected node: 'Backup' (6938fc8c-7450-4c9e-8760-baf3b8dbb0cc)
[24.06.2009 15:17:16] <01> Info Selected node: 'N8800' (N8800)
[24.06.2009 15:17:19] <01> Info Expanding node: 'N8800' (N8800)
[24.06.2009 15:17:19] <01> Info [Ssh] Creating new connection 'N8800:22:sys:False:False:1'.
[24.06.2009 15:17:19] <01> Info [Ssh] logon, host "N8800", port 22, user "sys", elevation to root "no", autoSudo no
[24.06.2009 15:17:19] <01> Info Starting perlSoap protocol to "N8800"
[24.06.2009 15:17:19] <01> Info Installing perlsoap library to /tmp/vee45c90d4c-3f7c-4555-82c6-564c5f15a293
[24.06.2009 15:17:19] <01> Info Reading "veeam_soap.tar" from directory "C:\Program Files\Veeam\Backup and FastSCP\"
[24.06.2009 15:17:26] <01> Info Answer to installation: :
[24.06.2009 15:17:26] <04> Info PerlSoap Channel closed
[24.06.2009 15:19:06] <01> Error Timed out waiting for operation "(cd /tmp && perl veeam_soap45c90d4c-3f7c-4555-82c6-564c5f15a293.pl -d -c -l lib45c90d4c-3f7c-4555-82c6-564c5f15a293 -e /tmp/veeam_error45c90d4c-3f7c-4555-82c6-564c5f15a293 2>> /tmp/veeam_error45c90d4c-3f7c-4555-82c6-564c5f15a293) || cat /tmp/veeam_error45c90d4c-3f7c-4555-82c6-564c5f15a293 2>&1" at VeeamSSH.PerlSoapProtocol.WaitReady()
[24.06.2009 15:19:06] <01> Error at VeeamSSH.LibFactory.StartSoapProtocol()
[24.06.2009 15:19:06] <01> Error at Veeam.Backup.CSshServiceConsoleViewItem.RefreshContent()
[24.06.2009 15:19:06] <01> Error at Veeam.Backup.CSshServiceConsoleViewItem.GetContent(List`1 containers, List`1 items)
[24.06.2009 15:19:06] <01> Error at Veeam.Backup.CServerViewItem.GetContent(List`1 containers, List`1 items)
[24.06.2009 15:19:06] <01> Error at Veeam.Backup.FormMain.AddViewContainers(TreeNode node)
[24.06.2009 15:19:06] <01> Error at Veeam.Backup.FormMain.treeMain_BeforeExpand(Object sender, TreeViewCancelEventArgs e)


The error file only has a single line in it:

sh: perl: command not found

However PERL is in the $PATH

The Thecus uses a custom linux kernel based on the source from linuxkernel.net

My current version is listed by the system as Linux version 2.6.23N7700 (root@WIG_devel) (gcc version 3.3.6) #2 Wed Apr 22 01:20:18 CST 2009

I changed the beginning of veeam_soap.pl as follows and put it back in the tar file.
---------------------------------------------------------------------------
#!/raid/data/module/PERL/perl/bin

use strict;
use warnings;

use Getopt::Std;

use constant DEFAULT_LIB_DIR=>'/raid/data/module/PERL/perl/lib';
use constant SUDO_BOOTSTRAP=>'sudo_bootstrap.sh';

------------------------------------------------------------------------------------


Hope this helps.


Doug

mdm
Lurker
Posts: 2
Liked: never
Joined: Jun 24, 2009 3:45 am
Full Name: Douglas Munn
Contact:

Re: Connecting to NAS as a LINUX server rather than through NFS

Post by mdm » Jun 25, 2009 3:18 am

From home:

I'd better add that I cut the line:

perl veeam_soap45c90d4c-3f7c-4555-82c6-564c5f15a293.pl -d -c -l lib45c90d4c-3f7c-4555-82c6-564c5f15a293 -e /tmp/veeam_error45c90d4c-3f7c-4555-82c6-564c5f15a293 2>> /tmp/veeam_error45c90d4c-3f7c-4555-82c6-564c5f15a293

from the log file and ran it on the command line of the Thecus while logged in as sys.

The script DID run - I didn't get the "perl not found" error - although I got a mess of errors returned from the script. I'll try to run it with a capture file and send along the errors tomorrow.

Doug Munn

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 7 guests