backing up servers on differennt subnets

[buraza]

I have few servers which are on different subnet.
I registered these servers as clients in Legato Server and it's OK.
When I try to back them up I get message
savegroup alert: 'group' completed, total 1 clien(s), 0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded.

When I check the group details, it tells me
client 'west' is not properly configured in the NetWorker Server
or 'west' not in the aliases list for client 'west'

I have then added the aliases in the list and the message I get is:
Unsuccessful savesets
unknown error 1314

Can anyone help please?? I am using Legato 7.1

 

[joeunixadmin]

Hi,

Can you resolve the client and server name(s) as well as IP addresses?

-Joe

 

[buraza]

Yes, I can resolve the names.
I can ping by both ip address and the name.

I have added the aliases in the preferences tab on the client with the fqdn and in the remore tab I have added remote user.
The name resolution on this server works fine, however if I do the same on another server it fails.

But the backup still fails on both machines.
The message I get is
unsuccessful safesets
savefs: unknown error 1314(0x522)

 

[joeunixadmin]

Hi,

If I understand you correctly, you can resolve the name and IP of the server and client on both server and client. Is that correct?

Which OS is running on the client and on the server?
Can you use nwbackup on the client to statrt the backup?

-Joe

 

[buraza]

Joe,

Yes I can ping from both ends. Both client and server are on w2k3 ent. server os.
Strange thing is when I added the remote user in the remote user field in the client properties on the server I can start a backup, but then it fails giving that unknown error.
I have just tried doing backup from the client itself(Using Networker User) and command prompt from the client and I get that 'west' is not in the aliases list for client 'west'. Cannot open save session with 'server'.

I am hiting the brickwall and don't know how I can resolve this. Any help greatly appreciated.

Alma

 

[605]

make sure that name resoulution is unique from all directions (forward & reverse lookups).

Also, in a domain, make sure that short and FQDN are listed in the alias field.

The remote access field does only matter for recoveries, not for backups.

The remote user & password fields are only necessary for clients that do not know a root or system account (like Netware servers).

However, before you start the scheduled backup, may i suggest that you run a manual backup from the client.
Run "save -s server -v filenames" should tell you more.
If this does not work, try to resolve the hostnames via the hosts file.

 

[buraza]

I tried doing manual backup from the client to the server as you suggested and I still get message saying the client is not properly registered in the server and not in the aliases client list.

I have checked the server, it has the aliases list with and without FQDN.
I can ping from both ends and have added the name and the ip address of the client in the lmhost file on the server.
None of it helped!!

I am very confused now.

 

[605]

nslookup probably should tell you more. I am convinced that there is a name resolution problem somehow.

 

[buraza]

I think you were right.
I got the networking guys to check and they have made few changes, so now I can pass that stage. It is reckognising the alias name and I no longer get that message.
I now have another problem where it tells me 'no matching devices'...

I have checked the pool and the tape and the group.
That is all fine.
If I move another client to the same group which backs up to the same tape in the same pool it works fine, but for this client it fails and cannot ope save session with the server??
Any ideas...

Thank you for all your earlier applies.

Alma

 

[buraza]

Suggestions from the Legato error documents say it is a problem with storage node.
I do not have the storage node??
the message tells:
media notice; no matching devices; check storage nodes, devices or pools for save of client 'west';

has anyone come accross something similar??

 

[buraza]

if anyone is interested.
I got this problem fixed.
I have 2 servers which are on a different subnet.
When trying to back them up I first started getting messages about not having the client in the aliases list on the server (client properties on the server).
I thought it was a networking problem, but never had a problem with the pinging or name resolutions of any kind.
I have added another entry in the aliases list with the server name and the dot (.) at the end of the name.
e.g. west.
so I have west, west. and west.domain.com and this seam to have solved my problem of aliases errors and also the problem with the pool or group or the storage node..

Thank you all for all the previous replies.

rgds,
alma

 

[605]

Although it is possible AND CUSTOMERS LOVE TO DO THAT, do NOT select a device for a pool - it is not necessary.