Unsolved

This post is more than 5 years old

771

February 26th, 2007 11:00

NetWorker + Solaris 10 Zones Issue(s).

Hello everyone,

Before I begin:

Client: NetWorker 7.3.2.Build.364
Server: NetWorker 7.2.Build.172

I'm having some odd issues with NetWorker + Solaris 10 Zones.

Let me begin with "Server A". Server A is a 6800 with 12 zones on it. 11 of the zones backup FINE (including the global zone). One of the zones keeps coming back with the following error:

zone12:/vol01 save: SYSTEM error: client 'zone12.blahblah.com' is not properly configured on the NetWorker Server
zone12:/vol01 save: Cannot open save session with legato1
02/26/07 10:09:27 savegrp: zone12:/vol01 will retry 0 more time(s)
02/26/07 10:10:33 nsrd: legato1:index:zone12 saving to pool 'Default' (DM2017L2)
02/26/07 10:10:34 nsrd: legato1:index:zone12 done saving to pool 'Default' (DM2017L2) 3011 KB
02/26/07 10:10:34 nsrd: savegroup alert: Test Backup completed, total 1 client(s), 0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded. (zone12 Failed)

February 26th, 2007 12:00

Ugh, i accidentally hit the submit.

Here is the full text:


Hello everyone,

Before I begin:

Client: NetWorker 7.3.2.Build.364
Server: NetWorker 7.2.Build.172

I'm having some odd issues with NetWorker + Solaris 10 Zones.

Let me begin with "Server A". Server A is a 6800 with 12 zones on it. 11 of the zones backup FINE (including the global zone). One of the zones keeps coming back with the following error:

zone12:/vol01 save: SYSTEM error: client 'zone12.blahblah.com' is not properly configured on the NetWorker Server
zone12:/vol01 save: Cannot open save session with legato1
02/26/07 10:09:27 savegrp: zone12:/vol01 will retry 0 more time(s)
02/26/07 10:10:33 nsrd: legato1:index:zone12 saving to pool 'Default' (DM2017L2)
02/26/07 10:10:34 nsrd: legato1:index:zone12 done saving to pool 'Default' (DM2017L2) 3011 KB
02/26/07 10:10:34 nsrd: savegroup alert: Test Backup completed, total 1 client(s), 0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded. (zone12 Failed)

I've deleted it's client in Legato admin, reinstalled the client numerous times. I know it's not a networking issue. Nothing has changed, and it's on the same network even (no firewalling).

In the zone, we're only backing up the file systems specifically mounted on that zone. I do this since when you backup the global, it's grabbing all the zone config/files anyway (and this is the reccomended proceedure as far as I can tell).

---

Server B, it's the same story... except it's a 440 with one zone on it. It was working fine, and then suddenly it started doing the same thing as Server A.

I'm really at my wits end here, and the logs are less than helpful. Esp. in the case of Server A, I'm lost as to why 11 zones will back up on the machine... but not that ONE.

Any insights?

6 Operator

 • 

14.4K Posts

 • 

56.2K Points

February 27th, 2007 13:00

Is zone12.blahblah.com listed as alias for zone12 client - that would be simple thing for a start.

February 28th, 2007 01:00

Hello Andrew,

I am agree with Hrvoje that the alias attribute could be the reason. Normally, that message corresponds with an alias-resolution problem.

By the way, and if you don't mind, could you give me informations about how to do backup to the global a non-global zones? I was looking for information in EMC documentation, but I could not find anything. Yo say in this post that your global a non-global zones backup works correctly. How do you do it? Do you know how to do a Disaster Recover?

Thanks in advance, and sorry to ask you this in this post.

César.
No Events found!

Top