I have many clients that are running 4.5FP6 that perform user initiated
backups and archives (Oracle unix servers) to both a 4.5FP8 Master server
and a 5.1MP2 Master server.
No problems with pulling a restore or pushing restores from the Master. DR
test was conducted in Mid August of this year and no problems were
encountered.
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Piszcz,
Justin
Sent: Monday, September 26, 2005 1:02 PM
To: Kathryn Hemness; veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] RE: Help with connectivity problems to NetBackup
5.1MP3a and Windows 2000/3 clients
Most are running the same version now. We're currently not doing any oracle
hot backups, but wow, I will keep that in mind!
Thanks!
-----Original Message-----
From: cckat AT reality.ucdavis DOT edu [mailto:cckat AT reality.ucdavis DOT
edu] On Behalf
Of Kathryn Hemness
Sent: Monday, September 26, 2005 12:49 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Cc: Piszcz, Justin
Subject: Re: Help with connectivity problems to NetBackup 5.1MP3a and
Windows 2000/3 clients
Hi Justin --
Are your server and Windows clients running the same version of NetBackup?
To my knowledge, NetBackup 5.* and NetBackup 4.* binaries are only
compatible with regards to server-initiated operations. I find this partial
compatibility both a pain in the neck and a blessing. Because many of my
clients like the freedom to initiate their own backups and restores, it's
great incentive for them to upgrade the client.
The partial incompatibility is a curse in that I can't perform Oracle
backups between a server and a client if the NetBackup versions don't agree,
and coordinating an upgrade (which requires the participation of the dbas)
is a challenge.
If the NetBackup versions differ between the master server and the client,
then client-initiated options are restricted because of version
incompatibility.
The server can backup a client and perform restores to the client, but the
client can't initiate either.
> ________________________________
>
> Sent: Monday, September 26, 2005 9:10 AM
> To: veritas-bu
> Subject: Help with connectivity problems to NetBackup 5.1MP3a and
> Windows 2000/3 clients.
>
>
> All,
>
>
> Recently, some colleagues have upgraded a lot of servers from
NetBackup
> 4.5MP6 to NetBackup 5.1MP3a. After the last batch of upgrades, there
> are now a few problems with Windows 2000/3 servers.
>
>
> boxA: Displays "authentication failed" when trying to refresh its
status
> in the host properties -> clients menu. (win2003)
>
>
> boxB: Gets a network connection timeout (but when trying to lookup its
> own backups from the client, it shows: (win2003)
>
>
>
>
> boxC: It says the netbackup user/service cannot read the etc\services
> file (when the service is trying to start), even though this file is
> readable by everyone. (win2000)
>
>
> Any ideas how to fix any of these issues?
>
>
> I searched Google, only 3 relevant hits were returned with many
> questions but no answers. Also checked this mailing list's archive,
no
> luck there either.
>
>
> Thanks,
>
>
> Justin.
>
> --__--__--
>
> Message: 2
> Date: Mon, 26 Sep 2005 09:49:07 -0400
> From: "Piszcz, Justin" <jpiszcz AT servervault DOT com>
> To: "Piszcz, Justin" <jpiszcz AT servervault DOT com>,
> "veritas-bu" <veritas-bu AT mailman.eng.auburn DOT edu>
> Subject: [Veritas-bu] RE: Help with connectivity problems to NetBackup
5.1MP3a and Windows 2000/3 clients.
>
> This is a multi-part message in MIME format.
>
> ------_=_NextPart_001_01C5C2A1.10F2B2BE
> Content-Type: multipart/alternative;
> boundary="----_=_NextPart_002_01C5C2A1.10F2B2BE"
>
>
> ------_=_NextPart_002_01C5C2A1.10F2B2BE
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> # No methods can be used for hosts in the 123.123.56 network:
>
> #
>
> # ALL : 123.123.56.
>
> #
>
> # The default (ALL : ALL) is no methods can be used for any host.
This
>
> # means that to be used, a method and host has to be explicitly
defined
> in
>
> # methods_allow.txt.
>
> #
>
> ALL : ALL
>
>
> When this is commented out, I cannot connect to the client.
>
> Uncommenting it on the box in question for boxB fixed the problem.
>
>
>
--kathy
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
