[Veritas-bu] problem with NDMP backups and drives going down.

2007-07-04 Thread Broun, Bevan
Hi All

Getting desperate here.

We have:

Netbackup 5.1MP6 (problem existed on MP2) on a windows 2K host.
We have 2 libraries attached: 

MSL5026 with SDLT drives ultra scsi 3 attached.
MSL6030 with LTO3 drives connected via fibre HBAs.

We have netapp 920C running data on tap 7.0.5

We have ndmp backups running over ethernet to the netbackup server (which
gets configured as a ndmp device as per documentation).

Under NB5.1 we need dedicated drives to ndmp and a storage unit created.

All this was/is working perfectly well when we only had the SDLT library.
NDMP backups ran fine. We brought the MLS6030 because of the capacity
issues.

We configured the MSL6030 drives and ndmp as per what we had prevoiusly
done. Backups run but the drives continually go to down state. Sometimes it
last a few days, sometimes its a few minutes. Our work around at the moment
is to up the drives and reboot the netbackup server.

The ndmp 

We have a case raised with symantec but are not getting far. We have just
raised a case with netapp so they can help. What's the bet that this forum
get us fixed first :-)

We have upgraded to MP6.
Ugraded firmware on the drives.
Using latest symantec drivers for the library and drives.
Tried using scsi cables rather than via SAN. (this seemed to make it worse)
library and drive diagnostics from HP show no prolems (hp tape tools
running on the netbackup server).


P:\>set_ndmp_attr -verify gisvof-diamond0-e5b.gi.adi-limited.com
Connecting to host "gisvof-diamond0-e5b.gi.adi-limited.com" as user
"root"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 4...
Opening session--successful with NDMP protocol version 4
host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
Host info is:
host name "gisvof-diamond0"
os type "NetApp"
os version "NetApp Release 7.0.5"
host id "0101166033"
Login was successful
Host supports LOCAL backup/restore
Host supports 3-way backup/restore


All ideas welcomed.

Thanks all.

Bevan Broun
Systems Engineer
-- 
Civil - Integration & Outsourcing Services 
Thales Australia 
Address 
Address 
T: (02) 9562 2861
F: (02) 9562 2857
M: 0407 225 492
Email : [EMAIL PROTECTED] 
www.thalesgroup.com.au  



DISCLAIMER:---
This Email may contain confidential and/or privileged information and is 
intended 
solely for the addressee(s) named. If you have received this information in 
error, or
are advised that you have been posted this Email by accident, please notify the 
sender by return Email, do not redistribute it, delete the Email and keep no 
copies.
--

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] (46) server not allowed

2007-03-18 Thread Broun, Bevan
Hi All 

we are running version 5.1. Client is windows 2000 and server is windows
2000.

Im getting (46) server not allowed when getting the client properties. I
cant restore to the system from the server.

I know about  bpclntcmd but have only used it once.

Idea's thanks
 
BB

Bevan Broun
Systems Engineer
-- 
Civil - Integration & Outsourcing Services 
Thales Australia 
Address 
Address 
T: (02) 9562 2861
F: (02) 9562 2857
M: 0407 225 492
Email : [EMAIL PROTECTED] 
www.thalesgroup.com.au  



DISCLAIMER:---
This Email may contain confidential and/or privileged information and is 
intended 
solely for the addressee(s) named. If you have received this information in 
error, or
are advised that you have been posted this Email by accident, please notify the 
sender by return Email, do not redistribute it, delete the Email and keep no 
copies.
--

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Moving media from one master to another.

2006-07-17 Thread Broun, Bevan
And also 

vmquery -assignbyid


-- 
Bevan Broun
Systems Engineer
THALES
Services Division
W: (02) 9562 2861
M: 0407 225 492
F: (02) 9562 2857


DISCLAIMER:---
This Email may contain confidential and/or privileged information and is 
intended 
solely for the addressee(s) named. If you have received this information in 
error, or
are advised that you have been posted this Email by accident, please notify the 
sender by return Email, do not redistribute it, delete the Email and keep no 
copies.
--
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Moving media from one master to another.

2006-07-17 Thread Broun, Bevan
Im a bit late in on this conversation.

Jihm

I have done move of media and catelog from one master in to a existing
different master. I moved all tapes from a solaris master into a windows
master.

I did get help from veritas support but at one stage but when some things
didnt work out another support staff said "he should not have done this
under support"

Perhaps you are best to pay for consulting services.

Below is the mail I got from veritas support on the issue. Only the name
of the veritas support staff has been removed.

Now I can hardly remember what I did:

I did manually copy over indexes for clients.
I did manually edit the pool databases file. I had no pools ID clashes and
I think that turned out to be quite critical.

I did run commands like "bpmedia -m  ADI694  -movedb -oldserver
OLDSERVERNAME -newserver NEWSERVERNAME". I had to do some set up for this
first.

I used commands like: "vmadd -m  HFG933  -mt dlt -p  17" where I got info
for the command from the output of vmquery

one gotya I had was needing to put the old server in the "restore failover"
list of the new server.

I definately had a few issues and was wishing that I had got veritas to do
it under contract.


Subject: VERITAS Support: Case ID 230-061-782
To: <[EMAIL PROTECTED]>

Hi Bevan,
=20
now fully understanding the "challenges" ahead for you :), below is some
helpful information of the various Netbackup databases you will be
attempting to merge onto the final Netbackup master server, all at the
same level of NBU 5.1.
=20
Have a read of the following and I'll await your feedback. I have
included various extracts from different internal documents as there is
no Public Technote to do what you are doing - and the official take on
it is it is a "Consulting" issue rather than a "Support" responsibility,
but I am happy to assist you where I can :)
=20
- Chris.
--
Netbackup Databases invovlved:
--
There are six main databases that need to be considered when
reconfiguring a NetBackup environment:* The image database - this is a
flat file structure held on the NetBackup master server.  In general
this database can be moved from one location to another with a simple
copy operation.  However it is important to remember that this database
contains links to the media database, which need to be kept consistent.

* The media database - the only distributed database in most NetBackup
environments.  While it is possible to manipulate this database by
various editing techniques there are no NetBackup CLI options to modify
it.  It is therefore recommended that you endeavor to keep the media
database consistent and bring the image and volume database in line with
it.

* The policy database - another flat file structure that can simply be
copied between master servers (provided, of course, that the same class
name is not in use on both servers).  Be sure to update the storage unit
information associated with classes when moving them between servers. *=20
=20
The volume database - volume database information can be extracted and
updated by using the vmquery command.  When merging two environments the
best approach is to use vmquery to extract information from one volume
database and then a combination of vmadd and vmquery -assignbyid to
create corresponding information in the other volume database.  Note
that it is not possible to carry over tape usage information from one
database to another.

* The pool database - this database usually consists of a relatively
small number of entries.  The important thing to bear in mind is that it
is the number associated with each pool record, not the name, that is
used to link to the other databases.  This means that, unless the pool
records have been added in exactly the same order in two environments,
some tapes are likely to change pools following a merger.

* The global device database - this database contains information about
all devices on all media servers in a domain.  Storage units usually
change as a result of mergers and splits so it is simpler to define the
storage units you require rather than attempting to export and import
information. You may also choose to merge the jobs and error databases
if required but this is not essential and is not covered in this
document.

=20
Merging Master Servers:

In the interests of simplifying the management of a NetBackup
installation customers often seek to combine two or more domains under a
single, more powerful master server.  In most cases this presents few
problems but it is important to ensure that there is no risk of conflict
before starting such a merge When merging master servers you are
concerned with the following aspects of the NetBackup database:=20
* Image database
* Policy database
* Client database
* Global device database

Note: the merging of the volume or pool databases have not yet been

[Veritas-bu] license question re NDMP backup

2006-07-04 Thread Broun, Bevan
Hi All

Im figure Im more likely to get the correct answer here then from
veritas/semantic.

I have a netapp filter (a cluster actually) that I currently backup using
ndmp to the tape library attached to the (windows) master server. One of
the drives is configured as an ndmp drive.

The need to have one drive configured as ndmp is kill us and I believe from
info on this group that this is still not resolved with netbackup 6 and
netapp.

So I need another soln. If I was to directly attach a tape library to one
of the netapp filer heads, would netbackup be able to control the library?
Would i need another licenses beside the license for another library based
drive?

thanks

BB
-- 
Bevan Broun
Systems Engineer
THALES
Services Division
W: (02) 9562 2861
M: 0407 225 492
F: (02) 9562 2857


DISCLAIMER:---
This Email may contain confidential and/or privileged information and is 
intended 
solely for the addressee(s) named. If you have received this information in 
error, or
are advised that you have been posted this Email by accident, please notify the 
sender by return Email, do not redistribute it, delete the Email and keep no 
copies.
--
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NetApp/NAS - Backups

2006-01-31 Thread Broun, Bevan
on Tue, Jan 31, 2006 at 10:45:46AM -0700, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
wrote:
> Just FYI: although the v6.0 feature list has shared drives for NDMP, both
> Netapp & Veritas say it doesn't work.

Hi Mark

This is very important for me. Do you know where veritas and/or netapp say
this doesnt work?

BB
-- 
Bevan Broun
Systems Engineer
THALES
Services Division
W: (02) 9562 2861
M: 0407 225 492
F: (02) 9562 2857
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


[Veritas-bu] Vmware virtual machines Netbackup client licenses.

2006-01-11 Thread Broun, Bevan
This is the info I got confirmed.

Note the "one NetBackup component for each Operating System and Database
type".

<<
MULTIPLE DOMAIN OR VIRTUAL MACHINE SYSTEMS

NetBackup components (servers, clients, and database agents) for UNIX,
Windows, NetWare, and Linux are each licensed once per physical machine.
If a physical machine runs multiple Operating Systems and Databases,
then the physical machine requires one NetBackup component for each
Operating System and Database type. Please note that this policy
supersedes previous licensing policies that were communicated before the
date of this document.

Exception: NetBackup Clients installed on IBM zSeries (OS/390) should be
licensed once per virtual machine. This is an exception to the standard
NetBackup policy of licensing clients once per physical machine.
>>


on Thu, Jan 12, 2006 at 12:47:25PM +1100, Dean <[EMAIL PROTECTED]> wrote:
> That's only if you're backing up the physical host using the Redhat client.
> 
> If you're backing up the virtual hosts (ie - you install the NBU client in
> the VM's) you still need a license per virtual client. I've had *this*
> confirmed by Veritas. (although that doesn't necessarily mean it's
> correct!).
> 
> I worked at a place that consolidated ~150 physical Windows servers to 5
> VMware servers. They still needed their 150 NBU client licenses (all
> Windows)
> 
> I worked at another place where we suspended the virtual machines and backed
> up the .vmdk images from the vmware host. They only needed one NBU client
> license (Redhat)
> 
> Dean
> 
> On 1/12/06, Broun, Bevan <[EMAIL PROTECTED]> wrote:
> >
> > Others have noted that is is doable and supported. What hasnt been said
> > yet
> > is that veritas only require 1 license (of each client) type to backup all
> > virtual machines running on a physical system. That is, veritas is
> > licensing the physical hardware.
> >
> > I have confirmed this with veritas.
> >
> > For me, this recovers the cost of vmware esx server.
> >
> > BB
> > --
> > Bevan Broun
> > Systems Engineer
> > THALES
> > Services Division
> > W: (02) 9562 2861
> > M: 0407 225 492
> > F: (02) 9562 2857
> > ___
> > Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >

-- 
Bevan Broun
Systems Engineer
THALES
Services Division
W: (02) 9562 2861
M: 0407 225 492
F: (02) 9562 2857
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] Vmware virtual machines vs Netbackup

2006-01-11 Thread Broun, Bevan
Others have noted that is is doable and supported. What hasnt been said yet
is that veritas only require 1 license (of each client) type to backup all
virtual machines running on a physical system. That is, veritas is
licensing the physical hardware.

I have confirmed this with veritas.

For me, this recovers the cost of vmware esx server.

BB
-- 
Bevan Broun
Systems Engineer
THALES
Services Division
W: (02) 9562 2861
M: 0407 225 492
F: (02) 9562 2857
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu