Topic: Disk ARchive won't connect to TeraStation Pro

[tarball]

Disk ARchive worked fine for me on a off-line test server and Windows XP, so I installed it on an on-line test server running 7.1.3. I'm attempting to connect and backup to a new Buffalo TeraStation Pro.

This:
[root@mail3 tmp]# mount -t smbfs -o username=backup,password=password,ip=192.168.1.xx //Ts-name/backup /mnt/dar2/test

mounts successfully, but using:

[root@mail3 dar2]# ls
dar-2.3.2-1.i386.rpm  smeserver-dar2-0.0.1-3dmay.noarch.rpm

this:

[root@mail3 tmp]# db dar2 show test
test=dar2
    Backup=etc/e-smith/templates-custom
    Compression=5
    Description=test
    Exclude=
    Expiry=2
    Mount=/mnt/dar2
    Password=password
    Prune=
    Slice=650
    Target=//Ts-name/backup
    Username=backup
    VFSType=smbfs
    Verbose=on
    backupDay=manual
    backupTime=23:30
    status=enabled

gives me this:

May 12 11:21:27 mail3 e-smith-bg: Connecting /mnt/dar2/test to //Ts-name/backup
May 12 11:21:29 mail3 e-smith-bg: 10434: Connection to Ts-name failed
May 12 11:21:29 mail3 e-smith-bg: SMB connection failed

I've recreated the job and retried it, but dar2 never connects.  Is there any difference in the way Disk ARchive connects and the way I connect on the command line that would explain this?  Another log I should be checking?

(Darrell, I'm a long-time fan of your contribs and appreciate all the great work.)

Tarball

[dmay]

[root@mail3 tmp]# mount -t smbfs -o username=backup,password=password,ip=192.168.1.xx //Ts-name/backup /mnt/dar2/test

I don't use that specific 'ip' option there as that would not permit resolution based on host name supporting dynamic ip workstations. If you require a hard coded ip, your name resolution may be failing. Test this on your SME server by issuing:

# smbclient -L //Ts-name
# smbclient -L //Ts-name -I 192.168.1.xx

If only the IP works you have a name resolution issue.

However, since I do permit the ip address to be entered in the panel target field, simply change as shown below and everything should work:

 - Target=//Ts-name/backup
 + Target=//192.168.1.xx/backup

Darrell

[tarball]

Darrell,

Thank you very much for taking the time to respond.  Here's what happened:

# smbclient -L //Ts-name    did not work.
# smbclient -L //Ts-name -I 192.168.1.xx    did work.

More importantly, the second command gave the TeraStation name in capital letters, revealing that the "1" I had typed in in the name was actually a lower case "l" (this is in the place where I wrote "name" above).  I should have double-checked this common gotcha, but since the
mount -t smbfs -o username=backup,password=password,ip=192.168.1.xx //Ts-name/backup /mnt/dar2/test
command had worked with the incorrect server name, I didn't suspect it.  It seems that samba will favor a correct IP over an incorrect server name.  

So now that dar2 is working, if I use it instead of the mondoarchive that I have on the SME6 box I'm trying to replace, the steps in case of total meltdown and bare metal restore would be something like this:

1. Install SME7.1 from CD.
2. Replace /var/cache/yum with a recent tarball of the rpms to save the download.
3. Run the upgrade yum commands to upgrade to 7.1.3.
4. Install dar2 and create a backup job with the same info as before.
5. Restore from the most recent backup.  

Wait a minute - will a fresh install of dar2 restore something it did not create?

6. signal-event post-upgrade ; signal-event reboot

Sound reasonable?  

Thank you again for your time.

Tarball