RE: [Veritas-bu] Resource requirements for NBU 6?

2005-11-18 Thread Piszcz, Justin
I realize that, but I was wondering how it stored the lists in the
database by default, as it is not a plain text OR flat file anymore.

-Original Message-
From: Greenberg, Katherine A [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 9:06 AM
To: Piszcz, Justin; Ed Wilts; List Veritas List
Subject: RE: [Veritas-bu] Resource requirements for NBU 6?

You can compress the images catalog in the same manner that you could in
previous versions.

Is that what you're asking?

~Kate

-Original Message-
From: Piszcz, Justin [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 8:22 AM
To: Greenberg, Katherine A; Ed Wilts; List Veritas List
Subject: RE: [Veritas-bu] Resource requirements for NBU 6?


Does NBU 6 use compression on the databases (vs. flat files) - I have a
box with 50,000,000+ files, the flatfiles are huge.  Anyone know?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greenberg,
Katherine A
Sent: Friday, November 18, 2005 7:04 AM
To: Ed Wilts; List Veritas List
Subject: RE: [Veritas-bu] Resource requirements for NBU 6?

From everything I've heard/read, the memory requirements are higher, but
not sure about CPU. Since all of the Media Manager stuff is running on
the Master and all the db info for the device and media side of things
will be housed only on the master in a Sybase DB, the new req's are
based on that. Obviously it requires more system resources to run a real
relational database as opposed to the old NBU flat file method.

~Kate


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts
Sent: Thursday, November 17, 2005 3:57 PM
To: List Veritas List
Subject: [Veritas-bu] Resource requirements for NBU 6?


I've heard that NetBackup 6 takes a fair bit more memory than 5.  Has
anyone seen any Veritas documentation that supports this?  How about CPU
requirements?

Thanks,
.../Ed
-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED] ___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-
This e-mail may contain confidential or privileged information.  If you
think you have received this e-mail in error, please advise the sender
by reply e-mail and then delete this e-mail immediately.  Thank you.
Aetna


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

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


RE: [Veritas-bu] Resource requirements for NBU 6?

2005-11-18 Thread Greenberg, Katherine A
You can compress the images catalog in the same manner that you could in
previous versions.

Is that what you're asking?

~Kate

-Original Message-
From: Piszcz, Justin [mailto:[EMAIL PROTECTED] 
Sent: Friday, November 18, 2005 8:22 AM
To: Greenberg, Katherine A; Ed Wilts; List Veritas List
Subject: RE: [Veritas-bu] Resource requirements for NBU 6?


Does NBU 6 use compression on the databases (vs. flat files) - I have a
box with 50,000,000+ files, the flatfiles are huge.  Anyone know?

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Greenberg,
Katherine A
Sent: Friday, November 18, 2005 7:04 AM
To: Ed Wilts; List Veritas List
Subject: RE: [Veritas-bu] Resource requirements for NBU 6?

From everything I've heard/read, the memory requirements are higher, but
not sure about CPU. Since all of the Media Manager stuff is running on
the Master and all the db info for the device and media side of things
will be housed only on the master in a Sybase DB, the new req's are
based on that. Obviously it requires more system resources to run a real
relational database as opposed to the old NBU flat file method.

~Kate


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts
Sent: Thursday, November 17, 2005 3:57 PM
To: List Veritas List
Subject: [Veritas-bu] Resource requirements for NBU 6?


I've heard that NetBackup 6 takes a fair bit more memory than 5.  Has
anyone seen any Veritas documentation that supports this?  How about CPU
requirements?

Thanks,
.../Ed
-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED] ___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

-
This e-mail may contain confidential or privileged information.  If you
think you have received this e-mail in error, please advise the sender
by reply e-mail and then delete this e-mail immediately.  Thank you.
Aetna


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

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


RE: [Veritas-bu] migration to a new server - Followup question

2005-11-18 Thread Jim Peppas
All Policy, schedule and client info as well as images are all in the 
/usr/openv/netbackup/db dir. /usr/openv/volmgr/database holds info regarding 
the volume pools.

Dont forget the change the bp.conf file on all clients/media servers to reflect 
the new master server. 
Remember first line is supposed to be :
SERVER = master server

Regards, 
Jim Peppas



  ---Original Message---
  From: Dan Dobbs [EMAIL PROTECTED]
  Subject: RE: [Veritas-bu] migration to a new server - Followup question
  Sent: 18 Nov '05 23:11
  
  So, the procedure would be to install NetBackup on the new server, and
  then tar them on the old box, move them over, and unzip these files into
  their proper directories?
  
  How about schedules, clients, all that? Is that encompassed in this
  plan, or is that a different file system that needs to come over as
  well?
  
  Thanks again!
  
  -dd
  
   stefanos [EMAIL PROTECTED] 11/7/2005 3:09:38 AM 
  No , there is no way to do this.
  Always the request will be from the real  server name. That's why you
  must
  put both virtual and real server name to the server list of all
  netbackup
  clients (and media servers). As I write this is what the cluster aware
  installation of netbackup doing. Don't forget the cluster_name in the
  vm.conf.
  
  
  Stefanos
  
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of
  Williams,
  Kristopher L
  Sent: Sunday, November 06, 2005 8:29 PM
  To: [EMAIL PROTECTED]; Dan Dobbs; Veritas-bu@mailman.eng.auburn.edu
  Subject: RE: [Veritas-bu] migration to a new server - Followup
  question
  
  Stefanos and others,
  
  Quick followup question to your last tip.
  
  This might be a dumb question, but does anyone know on Windows how to
  make
  the requests coming from netbackup come from a virtual name. So if
  my
  master servers real name is server1.domain.com and I create a virtual
  name
  in DNS of nbmaster.domain.com (with a different ip address of course)
  how
  can I make sure netbackup is going out using nbmaster.domain.com and
  not
  server1.domain.com? Both IP's are bound to the same network card on
  the
  server.
  
  I've tried to figure this out by just adding in the virtual name to one
  of
  my media managers. When looking in the logs all I see if the access
  denied
  message for server server1.domain.com.
  
  Thanks guys!
  
  
  Kris
  
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of stefanos
  Sent: Sunday, November 06, 2005 3:58 AM
  To: 'Dan Dobbs'; Veritas-bu@mailman.eng.auburn.edu
  Subject: RE: [Veritas-bu] migration to a new server
  
  Well we have install linux master server to a lot of our customers.
  Both for
  small and big installations. The bigest is an isp with more than 200
  network
  clients, 1master and 1 media server. We had problems with 4.5 but with
  5.x
  no problem at all.But this is more personal (and customer) decision.
  
  For the migration, don't go through importing. Just copy the
  /netbackup/db
  and /volmgr/database directories (exclude the ltidevs robotic_def and
  globdb) Also DON'T copy the var folder (the license keys are bundle
  with the
  server name so if you copy the var folder netbackup will not come up).
  Take
  care for any link you may have inside the db folder (images
  perhaps) and any disk storage unit you may have (for space reasons).
  Run the ./volmgr/bin/vmglob -set_gdbhost $newmastername And the device
  configuration wizard only for the master server. Restart netbackup.
  Any
  other media server you may have will register the drives himself after
  some
  time. (but will be ready for backups immediately) Then run the command
  bpmedia -newserve $newmastername -oldserver $oldmastername After that
  the
  new master server is ready for use.
  
  Tip. Install the new master server  with a virtual name and a different
  ip
  than the server name and ip. This will help any migration in the
  future. If
  you do this you must put the original server name to the netbackup
  server
  list of all systems and to put the cluster_name = $virtualname to
  the
  vm.conf file of the master server (This is equivalent to one node
  cluster
  installation and helps to migrate muster server between systems
  eliminating
  the  name problem)
  
  stefanos
  
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED] On Behalf Of Dan
  Dobbs
  Sent: Saturday, November 05, 2005 12:30 AM
  To: Veritas-bu@mailman.eng.auburn.edu
  Subject: [Veritas-bu] migration to a new server
  
  Greetings, all.
  
  Currently, we are running 5.1 on an HP-UX L-class box, with a couple
  'bots
  (one old Surestore juke with (4) DLT4000s, one Neo juke with a DLT220).
  It
  seems to work reasonably well. We have a few hundred tapes 'in
  circulation'.
  So, we're probably one of the smaller sites that visit this list. :)
  
  We're taking the plunge, and planning a migration of our backup