You just became the resident expert.
Can you summarize the steps to do it successfully and what to watch out for?
Bobby Williams
2205 Peterson Drive
Chattanooga, Tennessee 37421
423-296-8200
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Collins,
Glen
Daryl
Well this should work, because it sounds almost identical to what my file
based cluster setup was (NBU software was installed as PHYSICAL name,
storage unit was Physical name, but policy was the virtual name!)
Have you added the servers to the permissions to access your master box?
I have a long running backup (expected to take 5 days) running
from a Windows 6.0 Windows client. The master server is Solaris 6.0MP3
and the backup is being staged to a Solaris media server (also version
6.0 MP3). I have a ticke open for on another Windows client which
support wants me to
This might be of some use for you.
It is recommended to have all NetBackup (NB) master, media, client, and
database extensions on the same release and at the same patch level. In
larger environments it is not possible to update all servers and clients
simultaneously. With versions of
I have seen both.
I have seen the latest client (at the time) 6.0MP3 running with a 6.0MP2
Oracle Agent because the MP3 was not out at the time, only the client, no
issues.
Its probably best to have them at the same revision though.
On Fri, 30 Mar 2007, Wolters, Keith wrote:
Another
The device host should be the master, but the tape path (or No rewind
device) should be filer-name:nrst3am, or whatever your device
Must be a dedicated tape drive, either direct connected, or zoned only
to the tape HBA of the filer.
Paul
--
-Original Message-
From:
don't create any STU's on it.
if you policies specify specific STUs, don't specify the STU on teh new
server?
--
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hindle,
Greg
Sent: March 29, 2007 10:46 AM
To: NB
From what I understand, the issue is Here:
We then setup a policy for Exchange DB backups using the Exchange
Virtual Server Name (Difffernt Hostname/IP than the NBu Virtual Name) as
the client the NBU Virtual Server Name for the Media Server in the
Storage Unit and configuring the policy to use
Edit
/usr/openv/netbackup/db/class/CLASS_NAME/schedule/SCHED_NAME/info
file and put 1800 for the field FREQUENCY.
It is the number of seconds, after you save that file,
dont open that policy with GUI.
Mike
--- Bob Stump [EMAIL PROTECTED] wrote:
No problems in this post. I am just sharing a
I need to find the chart that has all client version and what OS they
support. I need to know what the latest clients version are for HP UX,
Solaris 8.x, 9.x and Wintel servers. I cant seem to find this chart
anymore on the Symantec website.
Greg
This e-mail and any attachments are
http://seer.entsupport.symantec.com/docs/NBUESVR_digest.htm
--
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hindle,
Greg
Sent: March 30, 2007 2:02 PM
To: NB List Mail
Subject: [Veritas-bu] Compatibility
This is usually readily available in the digests.
for 6.0 and 5.x hardware AND OS compatibility
http://seer.support.veritas.com/docs/NBUESVR_digest.htm
Hindle, Greg [EMAIL PROTECTED] 3/30/2007 2:01 PM
I need to find the chart that has all client version and what OS they
support. I need
Thanks to all who responded!
Greg
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Stump
Sent: Friday, March 30, 2007 2:27 PM
To: Hindle, Greg; NB List Mail
Subject: Re: [Veritas-bu] Compatibility chart
This is usually readily available in
Symantec (Veritas) tightened some of the license
checking features in NBU6.0. SAN media license
checking is probably one of these.
--- WEAVER, Simon (external)
[EMAIL PROTECTED] wrote:
Daryl
Well this should work, because it sounds almost
identical to what my file
based cluster setup was
On Fri, 30 Mar 2007, Marion Hakanson wrote:
[EMAIL PROTECTED] said:
The case notes state there is no x86_64 6.0 clients yet FYI.
If you're talking about the regular NBU client, this is incorrect. The
x86_64 6.0 client came out as a client+patch release in 6.0 MP2. There
was no CD-ROM
15 matches
Mail list logo
