Re: [Veritas-bu] Frequency Based Schedules
Hi Steve, If the backup windows for the Weekly and Monthly schedules are different, then NetBackup will run both. If they are the same, NetBackup will skip the Weekly when the Monthly is scheduled for the same day. -- Kathy -- Message: 4 Date: Tue, 2 Jun 2009 10:22:25 -0400 From: Hudson, Steve steve.hud...@ironmountain.com Subject: [Veritas-bu] Frequency Based Schedules To: veritas-bu@mailman.eng.auburn.edu Message-ID: fa3c55f57d950e43b7142645b629655e06fc2...@numevp05.na.imtn.com Content-Type: text/plain; charset=us-ascii Hello Guru's ... We are struggling with this scenario. We are a Netbackup 6.5.3.1 shop and recently discovered that using Frequency Based Schedules that a Monthly Full backup and a Weekly Full backup for the same client will run on the same weekend. What are we doing Wrong?? I know if we used Calendar based Schedules for the Monthlys and excluded these dates from the Weeklys it would solve the problem but surely there must be a better way. Thanks in advance... Steve Hudson Enterprise Storage Iron Mountain 745 Atlantic Ave Boston, MA 02111 Phone: (617) 535-2849 steve.hud...@ironmountain.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NB 6.5.3 slow response for administrative tasks
Hi William, We already have the bp.conf entry, but I don't have the Performance Tuning Guide. Do you have a link for it? -- kathy Do you have an entry: CONNECT_OPTIONS = localhost 1 0 2 in the bp.conf on your Master Server? See page 50/51 of the Performance Tuning Guide. It does refer to when the server is busy, which yours is not. As I read it, this causes internal connections not to be funnelled through vnetd but to use nonreserved ports and the traditional port numbers. It doesn't sound hopeful but may be worth a try. I'd also suggest that if the server is new you try and move to 6.5.4 as soon as you can before the environment grows too much. If you are not on the FA programme you may have to wait for GA but that must be very soon. Also, absolutely vital is that all the servers are online and IP lookup etc works. You can configure not to require reverse lookups etc. Any problems like that will cause very long pauses. William D L Brown Kathryn Hemness kfhemn...@ucdavis.edu Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 29-May-2009 00:59 To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] NB 6.5.3 slow response for administrative tasks Greetings, I'm having some performance issues with various administrative tasks in NetBackup 6.5.3.1 on a new master server and fewer than 20 active backup policies. My master server is a Dell PE2950 server with 16GB memory running Redhat 4 update 7. What I'm seeing is really poor response when adding or changing backup policy specifications. Sometimes to update the backup windows via the Admin console, it takes longer than 2 minutes - even when there is no other activity. I've also seen significant pauses when activating/deactivating policies via the command line. Are there system or database parameters that can be set to optimize response? What worries me is that if I'm seeing this lousy response on an unloaded master server, what will I see when it's busy backing up a couple hundred clients? --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NB 6.5.3 slow response for administrative tasks
Greetings, I'm having some performance issues with various administrative tasks in NetBackup 6.5.3.1 on a new master server and fewer than 20 active backup policies. My master server is a Dell PE2950 server with 16GB memory running Redhat 4 update 7. What I'm seeing is really poor response when adding or changing backup policy specifications. Sometimes to update the backup windows via the Admin console, it takes longer than 2 minutes - even when there is no other activity. I've also seen significant pauses when activating/deactivating policies via the command line. Are there system or database parameters that can be set to optimize response? What worries me is that if I'm seeing this lousy response on an unloaded master server, what will I see when it's busy backing up a couple hundred clients? --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NB6.5.3.1 Admin Console doesn't display Media
Thanks Monte, It can't be that; we increased the nbj.conf memory settings to 512M and 1024M right after installation. On Wed, 27 May 2009, Ambrose, Monte wrote: Date: Wed, 27 May 2009 16:12:37 -0700 From: Ambrose, Monte mambr...@qualcomm.com To: Kathryn Hemness kfhemn...@ucdavis.edu, veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NB6.5.3.1 Admin Console doesn't display Media Kathy We had that problem and fixed it by tuning the Java on the master server Update file /usr/openv/java/nbj.conf (Settings we used below) Entries to change INITIAL_MEMORY=256M MAX_MEMORY=1024M Bounce NetBackup Daemons and see if that helps. - Monte -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kathryn Hemness Sent: Friday, May 22, 2009 9:36 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NB6.5.3.1 Admin Console doesn't display Media Greetings, I'm attempting to setup the remote administration java gui on a Windows XP system for NetBackup 6.5.3.1. The WinXP system is just a client and the admin gui will be for monitoring a Redhat 4 Master server backup enterprise. There are no media servers as yet and the backups are written to BasicDisk and then duplicated to tape. My problem is that from the administration gui I can do everything except display media. The error I get is the following: A connection to master server could not be established. Verify services or daemons are up and running. All daemons and services are up and running and launching the admin gui from the master server has no problems displaying anything. Is there an extra ACL for this media-display/monitor functionality? I'm a newbie at NetBackup 6.5, and currently have another NetBackup 5.1MP6 enterprise which doesn't have all of the new NetBackup databases. Any help is appreciated. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NB6.5.3.1 Admin Console doesn't display Media
Greetings, I'm attempting to setup the remote administration java gui on a Windows XP system for NetBackup 6.5.3.1. The WinXP system is just a client and the admin gui will be for monitoring a Redhat 4 Master server backup enterprise. There are no media servers as yet and the backups are written to BasicDisk and then duplicated to tape. My problem is that from the administration gui I can do everything except display media. The error I get is the following: A connection to master server could not be established. Verify services or daemons are up and running. All daemons and services are up and running and launching the admin gui from the master server has no problems displaying anything. Is there an extra ACL for this media-display/monitor functionality? I'm a newbie at NetBackup 6.5, and currently have another NetBackup 5.1MP6 enterprise which doesn't have all of the new NetBackup databases. Any help is appreciated. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Qualstar Libraries??
Hi Neil, Nope. I mean TLS. The XLS line is newer and beyond my budget. --Kathy On Wed, 20 May 2009, veritas-bu-requ...@mailman.eng.auburn.edu wrote: Date: Tue, 19 May 2009 12:01:38 -0700 From: Conner, Neil n...@mbari.org Subject: Re: [Veritas-bu] Qualstar Libraries?? To: Tschida, Tom (STP) tom.tsch...@bsci.com, Veritas List veritas-bu@mailman.eng.auburn.edu Message-ID: c6385022.1989a%n...@mbari.org Content-Type: text/plain; charset=iso-8859-1 You mean the Qualstar XLS... We?ve been using Qualstar TLS libraries since 1999 and they?re still going strong. But when it came time to purchase an LTO library in 2007, we chose an Overland Storage NEO 8000 over the Qualstar XLS because the NEO has tighter media density and a traditional rack-sized footprint. The NEO has been rock solid and the few times I?ve needed to call tech support, they?ve been good as well. Neil On 5/18/09 8:50 AM, Tschida, Tom (STP) tom.tsch...@bsci.com wrote: Hello All, We are in the middle of a Physical Tape Library selection process. We have narrowed down our choices to the Quantum Scalar series and the STK SL3000, but I came across some info on the Qualstar SLX library and it looks very intriguing. So finally to the question. Is anyone out there using the Qualstar SLX and what are your thoughts? Happy? Disappointed? How's the speed, reliability, etc? Any info is greatly appreciated. Regards, Tom Tschida Boston Scientific ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Qualstar Libraries??
Hi Tom, I've been using Qualstar libraries since 1998, first with AIT2 and currently with an LTO3/LTO4 mixed drive Qualstar TLS-88264. We've been using the TLS-88264 since spring of 2005 and have been very happy with it. Whatever library you go with, make sure all of the drives are direct-attach fiber. Drives connected via a fiber-scsi bridge are cheaper, but the bridge throttles the drive throughput significantly. --Kathy -- Message: 1 Date: Mon, 18 May 2009 15:54:43 -0500 From: rusty.ma...@sungard.com Subject: Re: [Veritas-bu] Qualstar Libraries?? To: Tschida, Tom (STP) tom.tsch...@bsci.com Cc: veritas-bu@mailman.eng.auburn.edu, veritas-bu-boun...@mailman.eng.auburn.edu Message-ID: ofa6b1183c.5d30ffdd-on852575ba.00728c73-862575ba.0072d...@sungard.com Content-Type: text/plain; charset=utf-8 Tom, sorry no experience with that library, but I have used both the Scalar i2k and the SL3000 (and SL8500 but you didn't mention that one). I think either one of those are great libraries, but I'd give the nod to the SL3000 for its optional dual longbot configuration. Rusty Major, MCSE, BCFP, VCS ? Sr. Storage Engineer ? SunGard Availability Services ? 757 N. Eldridge Suite 200, Houston TX 77079 ? 281-584-4693 Keeping People and Information Connected? ? http://availability.sungard.com/ P Think before you print CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system. Tschida, Tom (STP) tom.tsch...@bsci.com Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 05/18/2009 10:54 AM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] Qualstar Libraries?? Hello All, We are in the middle of a Physical Tape Library selection process. We have narrowed down our choices to the Quantum Scalar series and the STK SL3000, but I came across some info on the Qualstar SLX library and it looks very intriguing. So finally to the question. Is anyone out there using the Qualstar SLX and what are your thoughts? Happy? Disappointed? How's the speed, reliability, etc? Any info is greatly appreciated. Regards, Tom Tschida Boston Scientific___ 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
[Veritas-bu] Using NetBackup to backup a DPM server
Greetings - Is there anyone on this list who is successfully backing up a DPM server from a Unix or Linux NetBackup server? If so, would you mind sharing your secrets? I've read the applicable sections of the DPM manuals and it looks like work on the client side is required for a successful backup from a Unix NetBackup server. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] make_scsi_dev woes under Linux
Hi Dan and NetBackup advisors, I realize this subject is from a very old thread (Tue, 15 Aug 2006) but the situation from 2006 most closely resembles my current problem. I've been upgrading my RHEL3 (32-bit) Linux NetBackup 5.1MP6 servers to RHEL4 (64-bit). All of the servers are Sun X4200 servers. All of the upgrades on my media servers went very well. My colleague and I devised a disk-cloning mechanism for building out a set of RHEL4 disks using spare drive bays and customize them for the server we wish to upgrade. We then put the pre-built disks in the server, boot the server with the new disks. The last media server we upgraded using this process only took about 2 hours of downtime. Now all of my media servers have been upgraded and we are attempting to use the same process for upgrading my Master server. The problem we are having with this master upgrade is in NetBackup's inability to control the tape library robotic. The tape drives and the changer are all visible. We have managed to get our udev/rules.d/20-local.rules file so that it detects the tape drives and changer even if the drives have tapes mounted. The drives and changer are configured via tpconfig; the global database synchronizes without error; the robtest utility can move tapes, load and unload them. But when I tried a test restore to test NetBackup's ability to load and unload tapes, I got the following segfault: Apr 9 11:57:11 errol tldd[1432]: TLD(0) MountTape 040943 on drive 5, from slot 182 Apr 9 11:57:11 errol kernel: tldd[1869]: segfault at rip 00807f4d rsp ca20 error 6 Apr 9 11:57:11 errol tldd[1432]: DecodeMount(): TLD(0) drive 5, Actual status: Process killed by signal Apr 9 11:57:11 errol tldd[1432]: Unexpected response status (11) in DecodeMount I'd appreciate any advice at this point. Could this segfault be caused by my OS upgrade from a 32-bit to a 64-bit OS? The udev/haldaemon device handling was a huge difference between RHEL3 and RHEL4 too. Today's Topics: 6. make_scsi_dev woes under Linux (Daniel Cox) -- Message: 6 Date: Tue, 15 Aug 2006 11:31:38 -0500 From: Daniel Cox [EMAIL PROTECTED] Subject: [Veritas-bu] make_scsi_dev woes under Linux To: veritas-bu@mailman.eng.auburn.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii We've got a few media servers running NetBackup 5.1 MP5 under Linux (RedHat AS4) and we're having no end of problems with FC attached tape drive device mappings. I see when NB starts it runs make_scsi_dev, which creates the following devices: [EMAIL PROTECTED] ~ # ls -l /dev/st total 0 lrwxrwxrwx 1 root root 8 2006-08-15 12:28 h0c0t0l0 - /dev/st5 lrwxrwxrwx 1 root root 8 2006-08-15 12:28 h0c0t1l0 - /dev/st4 lrwxrwxrwx 1 root root 8 2006-08-15 12:28 h0c0t2l0 - /dev/st3 lrwxrwxrwx 1 root root 8 2006-08-15 12:28 h1c0t0l0 - /dev/st1 lrwxrwxrwx 1 root root 8 2006-08-15 12:28 h1c0t1l0 - /dev/st0 lrwxrwxrwx 1 root root 8 2006-08-15 12:28 h1c0t2l0 - /dev/st2 lrwxrwxrwx 1 root root 9 2006-08-15 12:28 nh0c0t0l0 - /dev/nst5 lrwxrwxrwx 1 root root 9 2006-08-15 12:28 nh0c0t1l0 - /dev/nst4 lrwxrwxrwx 1 root root 9 2006-08-15 12:28 nh0c0t2l0 - /dev/nst3 lrwxrwxrwx 1 root root 9 2006-08-15 12:28 nh1c0t0l0 - /dev/nst1 lrwxrwxrwx 1 root root 9 2006-08-15 12:28 nh1c0t1l0 - /dev/nst0 lrwxrwxrwx 1 root root 9 2006-08-15 12:28 nh1c0t2l0 - /dev/nst2 There seems to be 2 big problems with this. The devices as created by the OS (st*, nst*) can change due to HBA driver upgrades, PCI bus detection order changes, somebody moving an HBA around on the system or somebody moving a drive around in the SAN for various reasons (port based zoning). Another problem is if any of the previous scenarios occur then NB creates entirely different /dev/st/*, /dev/sg/* entries to represent the new host/controller/target/lun detection order. Naturally either of these scenarios results in drive and robotic library id mismatches and either netbackup refusing to start or drives going into perm DOWN state. We can use 2.6 kernel udev rules to map WWNs to OS devices and always have consistent /dev/st*, /dev/sg* device names to get around the first problem; however the NB auto-created devices can still change so we are stuck with things occasionally breaking and then we waste a fare amount of time putting it all back together again. Is there some better way of handling this? Dan- --Kathy Kathryn Hemness[EMAIL PROTECTED] Infrastructure Servicesphone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux Master Server
Hi Austin, I had been using Sun Solaris/Sparc servers until 2006 when I started doing disk-based backups and de-duplication. Neither the OS nor the hardware (a Sun V240) could handle the backup/deduplication load (The performance was dismal). I now have 4 active backup servers each of which handles 14 active backups and 2 duplications concurrently with loads less than 5. These servers are the Sun X4200 (dual-core opteron cpus) with 2 emulex fiber hbas. Each hba is connected to a 3TB Nexsan SATABoy disk array and 8 LTO drives (4 LTO4 and 4 LTO3) via Brocade Silkworm 3900 fiber switches. On Wed, 9 Apr 2008 [EMAIL PROTECTED] wrote: -- Message: 1 Date: Wed, 9 Apr 2008 16:30:53 -0400 From: Austin Murphy [EMAIL PROTECTED] Subject: [Veritas-bu] Linux Master Server To: veritas-bu@mailman.eng.auburn.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 Does anyone have a reason *not* to use NetBackup on Linux as a master/media server? I've heard that Linux makes a great media server, but how about a master? My options are Solaris/SPARC and Linux/x86_64 and I was wondering if anyone had found a concrete reason why Linux was inferior. Thanks, Austin -- --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NB5.1MP6 and LTO4
Greetings, I've got a mixed library of LTO2 and LTO3 tape drives. I'm going to replace the LTO2 with LTO4 drives but have found that NetBackup 5.1 doesn't have an HCART4 designation for LTO4 tapes and library types. If the NetBackup configurations don't actually affect actual capacity of the drives, I can probably designate the LTO4 tapes as HCART. I'm not yet ready to upgrade my servers to NetBackup 6. Is there anyone out using LTO4 with NB5.1? --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Encrypted backups of already encrypted data
Greetings, Thanks for all of the responses. Basically, they confirmed what I already believed. On Tue, 26 Jun 2007, Sesar, Steven L. wrote: Date: Tue, 26 Jun 2007 08:39:26 -0400 From: Sesar, Steven L. [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED], Jeff Lightner [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Encrypted backups of already encrypted data It will definitely apply compression algorithms, regardless of the state of the data which is being backed up. === Steven L. Sesar Lead Operating Systems Programmer/Analyst UNIX Application Services R101 The MITRE Corporation 202 Burlington Road - MS K101 Bedford, MA 01730 tel: (781) 271-7702 fax: (781) 271-2600 mobile: (617) 519-8933 email: [EMAIL PROTECTED] === -Original Message- From: [EMAIL PROTECTED] on behalf of Kathryn Hemness Sent: Mon 6/25/2007 6:12 PM To: Jeff Lightner Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Encrypted backups of already encrypted data Thanks, Jeff. My assumption was the same. I didn't think that NetBackup would bother to perform any checks to see if a file was already encrypted. My question was prompted from one of my clients. I don't have any way of knowing if any of my backup clients are encrypting their disk filesystems or partitions. I certainly hope my clients haven't purchased a NetBackup encryption license knowing their systems were already encrypting data. On Mon, 25 Jun 2007, Jeff Lightner wrote: Date: Mon, 25 Jun 2007 14:10:44 -0400 From: Jeff Lightner [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Encrypted backups of already encrypted data I'm assuming it wood. The NBU encryption method and keys would not necessarily be the same as those used for the original data. The question is if the data is already encrypted why would you want to slow down your backup by encrypting it again? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Monday, June 25, 2007 1:40 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Encrypted backups of already encrypted data Greetings, If I'm running an encrypted backup of already encrypted data, does NetBackup re-encrypt the data? --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --Kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --Kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Encrypted backups of already encrypted data
Greetings, If I'm running an encrypted backup of already encrypted data, does NetBackup re-encrypt the data? --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Encrypted backups of already encrypted data
Thanks, Jeff. My assumption was the same. I didn't think that NetBackup would bother to perform any checks to see if a file was already encrypted. My question was prompted from one of my clients. I don't have any way of knowing if any of my backup clients are encrypting their disk filesystems or partitions. I certainly hope my clients haven't purchased a NetBackup encryption license knowing their systems were already encrypting data. On Mon, 25 Jun 2007, Jeff Lightner wrote: Date: Mon, 25 Jun 2007 14:10:44 -0400 From: Jeff Lightner [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Encrypted backups of already encrypted data I'm assuming it wood. The NBU encryption method and keys would not necessarily be the same as those used for the original data. The question is if the data is already encrypted why would you want to slow down your backup by encrypting it again? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Monday, June 25, 2007 1:40 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Encrypted backups of already encrypted data Greetings, If I'm running an encrypted backup of already encrypted data, does NetBackup re-encrypt the data? --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --Kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NB51MP6 Error updating client host properties
Greetings, While attempting to update client host properties, I get a popup indicating a No such file or directory error. According to the Universal settings of the client, server file writes are allowed. Has anyone else seen this and know of a fix? Ultimately, I need to update the client properties to enable restores from the client. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NB51MP6 Error updating client host properties
Thanks Justin, I think you may be onto somethingI just checked a client exhibiting this behavior and bpcoverage shows that it's running NB51MP5. I'll keep an eye out for other client systems. On Tue, 19 Jun 2007, Justin Piszcz wrote: Date: Tue, 19 Jun 2007 17:56:32 -0400 (EDT) From: Justin Piszcz [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NB51MP6 Error updating client host properties Sounds like a bad installation/firewall/something weird, re-install the client and try again? On Tue, 19 Jun 2007, Kathryn Hemness wrote: Greetings, While attempting to update client host properties, I get a popup indicating a No such file or directory error. According to the Universal settings of the client, server file writes are allowed. Has anyone else seen this and know of a fix? Ultimately, I need to update the client properties to enable restores from the client. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Symantec Support for AFS Backups
Greetings, Symantec recently sent me a letter letting me know they are researching market demand for OpenAFS usage to determine if their decision to drop support for AFS backups should be reconsidered. Their dropping of AFS support is based on their perception that only a handful of customers use the NetBackup AFS backup capability. In my backup enterprise, I'm currently backing up about 6TB (in the full backups, but I also do daily incrementals), and the AFS usage has grown in the past year and we expect to increase the AFS storage upwards of 10TB. The Symantec representative indicated they will be finalizing findings and making recommendations within the next two weeks, so if you have plans on on implementing AFS at your organization, I would recommend contacting [EMAIL PROTECTED] Also, if you want any information on how AFS backups and restores work, I can share my experiences. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux Shared Memory Configuration
Greetings, I made the kernel parameter changes and they had no impact, so I decided to take a closer look at the errors. All of the errors were for backups and backup duplications of a single Windows client. I've been troubleshooting EXIT 14 backup failures on this client since May without any luck. For some reason, this client's EXIT 14 failures started leaving 1K disk buffer files on my media server storage unit in early September. My backup image duplication script does not check the validity of the backupid for files left in the disk storage unit path, so it attempts to duplicate a non-existent backupid. I've not yet compared my pre-change bptm/bpdm logs to see if the changes made any difference in empty buffer delays. -- Forwarded message -- Date: Tue, 19 Sep 2006 11:09:40 -0700 (PDT) From: Kathryn Hemness [EMAIL PROTECTED] To: Nardello, John [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Linux Shared Memory Configuration Greetings, Thanks to all who respondedMost of the suggestions were helpful. This is a good technote and I'm going to try adjusting my values. Regarding bob944's comments, my Linux media servers ARE running with default kernel parameters and I'm seeing shared memory errors. The files in the /usr/openv/netbackup/db/config were recommended for both Solaris and Linux. It is for these reasons that I posted my query. I'm posting my current values for the parameters and indicating the recommended minimal settings in parenthesis: kernel.msgmnb = 16384 (65536) kernel.msgmni = 16(256) kernel.msgmax = 8192 (8192) kernel.shmmni = 4096 (1024) kernel.shmall = 2097152 (nothing indicated in document) kernel.shmmax = 33554432 (16777216) - my value is already larger, so I'm keeping it. kernel.sem = 25032000 32 128 (300 1024 32 1024) semmsl, semmns, semopm, semmni) My Linux servers have 4GB of memory so I can always make upward adjustments. On Tue, 19 Sep 2006, Nardello, John wrote: Date: Tue, 19 Sep 2006 08:21:59 -0700 From: Nardello, John [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Linux Shared Memory Configuration Technote talking about Linux kernel tuning recommendations: http://support.veritas.com/docs/263755 A little old but I doubt the variables have changed any. - John Nardello -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Monday, September 18, 2006 3:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Linux Shared Memory Configuration Greetings, My backup enterprise currently consists of a Solaris 9 Sun V240 master and 3 Sun X4200 RHEL3 Linux Media Servers running NB51MP5. I've been getting the following messages for backups and duplications to storage units on my Linux media servers: problems encountered during setup of shared memory (89) I use disk storage units and a mixed LTO2/LTO3 library. I've attempted to setup my Linux media servers similar to my Solaris 9 master by using the same NUMBER/SIZE_DATA_BUFFERS files in /usr/openv/netbackup/db/config. But on my Solaris 9 master, I also had /etc/system settings for msgsys, semsys, and shmsys values. I haven't been able to find anything about needing similar /etc/system tuning on Linux (I believe the /etc/system equivalents are set via the /etc/sysctl.conf file). I'm hoping someone can tell me if all of the /etc/system parameters can be set with sysctl on Linux and if their names are the same. Here are my current Solaris /etc/system parameters: set msgsys:msginfo_msgmap=512 set msgsys:msginfo_msgmax=8192 set msgsys:msginfo_msgmnb=65536 set msgsys:msginfo_msgmni=256 set msgsys:msginfo_msgssz=16 set msgsys:msginfo_msgtql=512 set msgsys:msginfo_msgseg=8192 set semsys:seminfo_semmap=64 set semsys:seminfo_semmni=1024 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmnu=1024 set semsys:seminfo_semmsl=300 set semsys:seminfo_semopm=32 set semsys:seminfo_semume=64 set shmsys:shminfo_shmmax=536870912 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=220 set shmsys:shminfo_shmseg=100 Any help is appreciated. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux Shared Memory Configuration
Thanks Dave, I do have that too...I just short-cutted my explanation of the files in my /usr/openv/netbackup/db/config directory. On Tue, 19 Sep 2006, Clooney, David wrote: Date: Tue, 19 Sep 2006 11:56:05 +0100 From: Clooney, David [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Linux Shared Memory Configuration Not answering you question but if you media server is writing to disk you might want to check and implement SIZE_DATA_BUFFERS_DISK Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: 18 September 2006 23:59 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Linux Shared Memory Configuration Greetings, My backup enterprise currently consists of a Solaris 9 Sun V240 master and 3 Sun X4200 RHEL3 Linux Media Servers running NB51MP5. I've been getting the following messages for backups and duplications to storage units on my Linux media servers: problems encountered during setup of shared memory (89) I use disk storage units and a mixed LTO2/LTO3 library. I've attempted to setup my Linux media servers similar to my Solaris 9 master by using the same NUMBER/SIZE_DATA_BUFFERS files in /usr/openv/netbackup/db/config. But on my Solaris 9 master, I also had /etc/system settings for msgsys, semsys, and shmsys values. I haven't been able to find anything about needing similar /etc/system tuning on Linux (I believe the /etc/system equivalents are set via the /etc/sysctl.conf file). I'm hoping someone can tell me if all of the /etc/system parameters can be set with sysctl on Linux and if their names are the same. Here are my current Solaris /etc/system parameters: set msgsys:msginfo_msgmap=512 set msgsys:msginfo_msgmax=8192 set msgsys:msginfo_msgmnb=65536 set msgsys:msginfo_msgmni=256 set msgsys:msginfo_msgssz=16 set msgsys:msginfo_msgtql=512 set msgsys:msginfo_msgseg=8192 set semsys:seminfo_semmap=64 set semsys:seminfo_semmni=1024 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmnu=1024 set semsys:seminfo_semmsl=300 set semsys:seminfo_semopm=32 set semsys:seminfo_semume=64 set shmsys:shminfo_shmmax=536870912 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=220 set shmsys:shminfo_shmseg=100 Any help is appreciated. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Notice to recipient: The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity. If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Linux Shared Memory Configuration
Greetings, Thanks to all who respondedMost of the suggestions were helpful. This is a good technote and I'm going to try adjusting my values. Regarding bob944's comments, my Linux media servers ARE running with default kernel parameters and I'm seeing shared memory errors. The files in the /usr/openv/netbackup/db/config were recommended for both Solaris and Linux. It is for these reasons that I posted my query. I'm posting my current values for the parameters and indicating the recommended minimal settings in parenthesis: kernel.msgmnb = 16384 (65536) kernel.msgmni = 16(256) kernel.msgmax = 8192 (8192) kernel.shmmni = 4096 (1024) kernel.shmall = 2097152 (nothing indicated in document) kernel.shmmax = 33554432 (16777216) - my value is already larger, so I'm keeping it. kernel.sem = 25032000 32 128 (300 1024 32 1024) semmsl, semmns, semopm, semmni) My Linux servers have 4GB of memory so I can always make upward adjustments. On Tue, 19 Sep 2006, Nardello, John wrote: Date: Tue, 19 Sep 2006 08:21:59 -0700 From: Nardello, John [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Linux Shared Memory Configuration Technote talking about Linux kernel tuning recommendations: http://support.veritas.com/docs/263755 A little old but I doubt the variables have changed any. - John Nardello -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Monday, September 18, 2006 3:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Linux Shared Memory Configuration Greetings, My backup enterprise currently consists of a Solaris 9 Sun V240 master and 3 Sun X4200 RHEL3 Linux Media Servers running NB51MP5. I've been getting the following messages for backups and duplications to storage units on my Linux media servers: problems encountered during setup of shared memory (89) I use disk storage units and a mixed LTO2/LTO3 library. I've attempted to setup my Linux media servers similar to my Solaris 9 master by using the same NUMBER/SIZE_DATA_BUFFERS files in /usr/openv/netbackup/db/config. But on my Solaris 9 master, I also had /etc/system settings for msgsys, semsys, and shmsys values. I haven't been able to find anything about needing similar /etc/system tuning on Linux (I believe the /etc/system equivalents are set via the /etc/sysctl.conf file). I'm hoping someone can tell me if all of the /etc/system parameters can be set with sysctl on Linux and if their names are the same. Here are my current Solaris /etc/system parameters: set msgsys:msginfo_msgmap=512 set msgsys:msginfo_msgmax=8192 set msgsys:msginfo_msgmnb=65536 set msgsys:msginfo_msgmni=256 set msgsys:msginfo_msgssz=16 set msgsys:msginfo_msgtql=512 set msgsys:msginfo_msgseg=8192 set semsys:seminfo_semmap=64 set semsys:seminfo_semmni=1024 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmnu=1024 set semsys:seminfo_semmsl=300 set semsys:seminfo_semopm=32 set semsys:seminfo_semume=64 set shmsys:shminfo_shmmax=536870912 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=220 set shmsys:shminfo_shmseg=100 Any help is appreciated. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Linux Shared Memory Configuration
Greetings, My backup enterprise currently consists of a Solaris 9 Sun V240 master and 3 Sun X4200 RHEL3 Linux Media Servers running NB51MP5. I've been getting the following messages for backups and duplications to storage units on my Linux media servers: problems encountered during setup of shared memory (89) I use disk storage units and a mixed LTO2/LTO3 library. I've attempted to setup my Linux media servers similar to my Solaris 9 master by using the same NUMBER/SIZE_DATA_BUFFERS files in /usr/openv/netbackup/db/config. But on my Solaris 9 master, I also had /etc/system settings for msgsys, semsys, and shmsys values. I haven't been able to find anything about needing similar /etc/system tuning on Linux (I believe the /etc/system equivalents are set via the /etc/sysctl.conf file). I'm hoping someone can tell me if all of the /etc/system parameters can be set with sysctl on Linux and if their names are the same. Here are my current Solaris /etc/system parameters: set msgsys:msginfo_msgmap=512 set msgsys:msginfo_msgmax=8192 set msgsys:msginfo_msgmnb=65536 set msgsys:msginfo_msgmni=256 set msgsys:msginfo_msgssz=16 set msgsys:msginfo_msgtql=512 set msgsys:msginfo_msgseg=8192 set semsys:seminfo_semmap=64 set semsys:seminfo_semmni=1024 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmnu=1024 set semsys:seminfo_semmsl=300 set semsys:seminfo_semopm=32 set semsys:seminfo_semume=64 set shmsys:shminfo_shmmax=536870912 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=220 set shmsys:shminfo_shmseg=100 Any help is appreciated. --Kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Moving global database from master to media server
Good Morning, I want to move the global database host from the master server to a media server without losing any media database information. I have a shared storage tape library environment. I've already got the robotic control switched to the media server. Has anyone done this? --Kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disk-Based backups having empty final fragments
Thanks, Bob. The technote described my problem exactly.. I'm planning on migrating to a new server this summer, so I'll make sure I install NB5.1MP5. Upgrading to NB6.0 is too ambitious for the summer since major releases change outputs of many administrative commands I use. In the meantime, has anybody tried fooling NetBackup by creating a non-zero-sized fragment full of 0's? On Thu, 22 Jun 2006, bob944 wrote: Date: Thu, 22 Jun 2006 02:21:03 -0400 From: bob944 [EMAIL PROTECTED] To: veritas-bu@mailman.eng.auburn.edu, 'Kathryn Hemness' [EMAIL PROTECTED] Subject: RE: [Veritas-bu] Disk-Based backups having empty final fragments I'm running disk-storage-unit backups (not the disk-staging storage units) on a NB5.1MP3 Solaris 9 server. I've configured my storage units for a 2000MB fragment size. Occasionally, I run into backup images which exactly fill the fragments exactly and bpimagelist shows a final zero-sized fragment which doesn't exist on the storage unit. I haven't been able to duplicate these backups to tape. I've tried touching a file having the same name as the final fragment, but without success. I've ultimately had to expire the backup. Does anybody have a workaround for this? It seems like this is a potential problem regardless of the storage unit's fragment-size configuration. Sounds like the bug mentioned here a few postings ago: Also, what if the fragment size is 32GB and the backup is exactly 32GB? Are two fragments written or one? Yes. :-) See technote 280018 for a pre-5.1MP5 or pre-6.0MP2 bug related to this. So, check out http://seer.support.veritas.com/docs/280018.htm NetBackup 6 has a default disk STU frag size of 0.5TB (see the SAG), so a larger frag size, up to your OS's file-size limit, is also an option. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Disk-Based backups having empty final fragments
Greetings, I'm running disk-storage-unit backups (not the disk-staging storage units) on a NB5.1MP3 Solaris 9 server. I've configured my storage units for a 2000MB fragment size. Occasionally, I run into backup images which exactly fill the fragments exactly and bpimagelist shows a final zero-sized fragment which doesn't exist on the storage unit. I haven't been able to duplicate these backups to tape. I've tried touching a file having the same name as the final fragment, but without success. I've ultimately had to expire the backup. Does anybody have a workaround for this? It seems like this is a potential problem regardless of the storage unit's fragment-size configuration. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Path Restrictions for Windows Backups
Greetings, I've an issue with a large backup (200GB) of a Windows 2003 server behind a firewall. There are other large Windows 2003 servers behind the same firewall whose backups do not have issues. For the particular problem server, I've found a path whose backups consistently fail with the following errors: FTL - tar file write error (10054) media manager terminated by parent process EXIT STATUS 14 (file write failed) exited with status 14 (file write failed) These errors never occur on the same path name. When I configure the policy to backup the root directory, D:\ and exclude the problematic directory with an exclude_list, the backup still fails with the same errors. However, if I configure the policy for mult-streaming and list paths using wildcards in each stream, the backup of each stream works. At this point I'm guessing that there's something in the file/directory naming on this server which is causing problems when NetBackup is building the list of files to be backed up. The pathnames of the many files on this server are 200 characters many having filenames with 14 spaces between words. I haven't been able to find out if there are any files containing non-printing characters. Does NetBackup have a path-length limit for files to be backed-up? Or does NetBackup have a restriction on special characters or the number of consecutive spaces between words in a filename? --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Path Restrictions for Windows Backups
Greetings, I've an issue with a large backup (200GB) of a Windows 2003 server behind a firewall. There are other large Windows 2003 servers behind the same firewall whose backups do not have issues. For the particular problem server, I've found a path whose backups consistently fail with the following errors: FTL - tar file write error (10054) media manager terminated by parent process EXIT STATUS 14 (file write failed) exited with status 14 (file write failed) These errors never occur on the same path name. When I configure the policy to backup the root directory, D:\ and exclude the problematic directory with an exclude_list, the backup still fails with the same errors. However, if I configure the policy for mult-streaming and list paths using wildcards in each stream, the backup of each stream works. At this point I'm guessing that there's something in the file/directory naming on this server which is causing problems when NetBackup is building the list of files to be backed up. The pathnames of the many files on this server are 200 characters many having filenames with 14 spaces between words. I haven't been able to find out if there are any files containing non-printing characters. Does NetBackup have a path-length limit for files to be backed-up? Or does NetBackup have a restriction on special characters or the number of consecutive spaces between words in a filename? --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Path Restrictions for Windows Backups (fwd)
Please forgive my multiple postings of the same message. I got bounces on all of my attempts so I didn't realize my question actually made it. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Can't unfreeze tapes?
If the tape is expired AND frozen, then you may want to try un-expiring the tape first and then un-freezing it. The /usr/openv/netbackup/bin/admincmd/bpmedialist -summary command displays status of media-by-expiration proximity. Look in the Expired section for all of your media servers. --kathy Message: 1 Subject: RE: [Veritas-bu] Can't unfreeze tapes? Date: Thu, 4 May 2006 10:00:45 -0500 From: Sixbury, Dan [EMAIL PROTECTED] To: De Pedro, Ignacio [EMAIL PROTECTED], Justin Piszcz [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Specifying the media_server on the end does not help. I get the same error, and just to be absolutely sure, I ran the command through all media servers and the master server. I still get the following error: requested media id was not found in NB media database and/or MM volume database -Original Message- From: De Pedro, Ignacio [mailto:[EMAIL PROTECTED] Sent: Thursday, May 04, 2006 9:58 AM To: Sixbury, Dan; Justin Piszcz Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Can't unfreeze tapes? Execute bpmedia -unfreeze -m LL1189 -h media_server_assigned Regards, nacho -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Sixbury, Dan Enviado el: jueves, 04 de mayo de 2006 16:51 Para: Justin Piszcz CC: veritas-bu@mailman.eng.auburn.edu Asunto: RE: [Veritas-bu] Can't unfreeze tapes? We are on version 5.1 MP4 From the command line: bpmedia -unfreeze -m LL1189 requested media id was not found in NB media database and/or MM volume database I haven't re-inventoried the robot, yet, but will be. Dan -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Thursday, May 04, 2006 9:46 AM To: Sixbury, Dan Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Can't unfreeze tapes? Inventory the robot. What error do you get when you try to unfreeze them? What version of NB are you using? You do not provide enough background information. On 5/4/06, Sixbury, Dan [EMAIL PROTECTED] wrote: I have 2 tapes that are physically located in our tape library and show up in the netbackup GUI. The tapes are in a Frozen state right now, and I am unable to un-freeze the tapes. When I do a bpmedialist from the master/media servers, the tapes in question do not show up. It seems rather odd that the GUI would show the tapes, but that the command line would not show the tapes. Any suggestions? Thanks, Dan ___ 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
[Veritas-bu] NB51 support for Redhat 4?
Greetings, I'm going to be replacing a Solaris 9 NetBackup server with a RedHat Linux server. I need to use NB51MP5 because NB60 doesn't support AFS backups. The NB51 Release Notes indicate support for 32-Bit Redhat 3 for servers. Is there anyone running a NetBackup server on Redhat 4? If so, are you using 32- or 64-bit? --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NB51 support for Redhat 4?
Found it. Thanks. On Thu, 4 May 2006, Ed Wilts wrote: Date: Thu, 4 May 2006 15:55:15 -0500 From: Ed Wilts [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NB51 support for Redhat 4? On Thu, May 04, 2006 at 11:21:13AM -0700, Kathryn Hemness wrote: I'm going to be replacing a Solaris 9 NetBackup server with a RedHat Linux server. I need to use NB51MP5 because NB60 doesn't support AFS backups. The NB51 Release Notes indicate support for 32-Bit Redhat 3 for servers. Is there anyone running a NetBackup server on Redhat 4? If so, are you using 32- or 64-bit? According to the compatability matrix, it's currently supported. See http://seer.support.veritas.com/docs/263839.htm -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] NB51 support for Redhat 4?
I'm concerned about client-vulnerabilities down the road. Also, can NB5x clients launch the java gui to a NB60 server? On Thu, 4 May 2006, Jim Horalek wrote: Date: Thu, 4 May 2006 14:05:18 -0700 From: Jim Horalek [EMAIL PROTECTED] To: 'Ed Wilts' [EMAIL PROTECTED], 'Kathryn Hemness' [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NB51 support for Redhat 4? Also the afs limitation is for the 6.0 client only. You can still run Netbackup 6.0 server just use a 5.x client Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, May 04, 2006 1:55 PM To: Kathryn Hemness Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NB51 support for Redhat 4? On Thu, May 04, 2006 at 11:21:13AM -0700, Kathryn Hemness wrote: I'm going to be replacing a Solaris 9 NetBackup server with a RedHat Linux server. I need to use NB51MP5 because NB60 doesn't support AFS backups. The NB51 Release Notes indicate support for 32-Bit Redhat 3 for servers. Is there anyone running a NetBackup server on Redhat 4? If so, are you using 32- or 64-bit? According to the compatability matrix, it's currently supported. See http://seer.support.veritas.com/docs/263839.htm -- 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 --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Using scratch pool with mixed libraries
Hi Mark, I changed the configuration of one of my storage unit names for hcart3 and the backup duplications using LTO3 tapes worked without problems. Thanks for the great advice. --kathy On Tue, 2 May 2006 [EMAIL PROTECTED] wrote: Date: Tue, 2 May 2006 09:52:37 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Using scratch pool with mixed libraries You said you configured the duplication script to use a pool containing only LTO3 media. This isn't the way media is selected. It's all about the storage unit. You'll have to specify a destination storage unit that is defined to use LTO3 carts, then the duplication will write to the appropriate media type. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Tuesday, May 02, 2006 8:09 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Using scratch pool with mixed libraries Greetings -- All of my backups are written to disk storage units and then I use scripts to duplicate the images to tape. Originally, my libray had 4 LTO2 tapedrives and I've added 2 LTO3 drives. I can successfully duplicate backup images to LTO2 tapes with the LTO3 drives configured as HCART3, but I haven't been able to force NetBackup to use LTO3 tapes on the drives when the drives are configured as HCART3. I've configured the duplication scripts to use a pool containing only LTO3 media, but NetBackup insists on pulling tapes from the scratch pool containing LTO2 media. Is there anyone here using a scratch pool with a single library containing multiple types of tape drives and media? --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Using scratch pool with mixed libraries
Greetings -- All of my backups are written to disk storage units and then I use scripts to duplicate the images to tape. Originally, my libray had 4 LTO2 tapedrives and I've added 2 LTO3 drives. I can successfully duplicate backup images to LTO2 tapes with the LTO3 drives configured as HCART3, but I haven't been able to force NetBackup to use LTO3 tapes on the drives when the drives are configured as HCART3. I've configured the duplication scripts to use a pool containing only LTO3 media, but NetBackup insists on pulling tapes from the scratch pool containing LTO2 media. Is there anyone here using a scratch pool with a single library containing multiple types of tape drives and media? --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Using scratch pool with mixed libraries
This suggestion makes sense. I'll give it a try and let you know how it goes. On Tue, 2 May 2006 [EMAIL PROTECTED] wrote: Date: Tue, 2 May 2006 09:52:37 -0600 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Using scratch pool with mixed libraries You said you configured the duplication script to use a pool containing only LTO3 media. This isn't the way media is selected. It's all about the storage unit. You'll have to specify a destination storage unit that is defined to use LTO3 carts, then the duplication will write to the appropriate media type. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Tuesday, May 02, 2006 8:09 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Using scratch pool with mixed libraries Greetings -- All of my backups are written to disk storage units and then I use scripts to duplicate the images to tape. Originally, my libray had 4 LTO2 tapedrives and I've added 2 LTO3 drives. I can successfully duplicate backup images to LTO2 tapes with the LTO3 drives configured as HCART3, but I haven't been able to force NetBackup to use LTO3 tapes on the drives when the drives are configured as HCART3. I've configured the duplication scripts to use a pool containing only LTO3 media, but NetBackup insists on pulling tapes from the scratch pool containing LTO2 media. Is there anyone here using a scratch pool with a single library containing multiple types of tape drives and media? --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] FW: client hostname could not be found (48)
I had a client system with the same problem about a week ago. It turns out the system only had a forward DNS record (for the hostname) and needed a reverse record (for the IP address). I'm not a DNS guru, so I hope my simple explanation makes sense. --__--__-- Message: 1 From: WEAVER, Simon [EMAIL PROTECTED] To: 'Coen, Trevor' [EMAIL PROTECTED], 'veritas-bu@mailman.eng.auburn.edu' veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] FW: client hostname could not be found (48) Date: Wed, 29 Mar 2006 11:08:12 +0100 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --_=_NextPart_001_01C65318.AFE21E30 Content-Type: text/plain Are you using DNS? Can you ping by its FQDN? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Coen, Trevor [mailto:[EMAIL PROTECTED] Sent: 29 March 2006 10:29 To: 'veritas-bu@mailman.eng.auburn.edu' Subject: [Veritas-bu] FW: client hostname could not be found (48) I can ping the media server from the client but bpclntcmd -ip fails? C:\Program Files\VERITAS\NetBackup\binping eubackup1 Pinging eubackup1 [10.1.1.38] with 32 bytes of data: Reply from 10.1.1.38: bytes=32 time10ms TTL=128 Reply from 10.1.1.38: bytes=32 time10ms TTL=128 Reply from 10.1.1.38: bytes=32 time10ms TTL=128 Reply from 10.1.1.38: bytes=32 time10ms TTL=128 C:\Program Files\VERITAS\NetBackup\binbpclntcmd -ip eubackup1 host eubackup1: not found. C:\Program Files\VERITAS\NetBackup\binbpclntcmd -ip eubackup1 host eubackup1: not found. _ From: Coen, Trevor Sent: 29 March 2006 09:16 To: 'veritas-bu@mailman.eng.auburn.edu' Subject: client hostname could not be found (48) I've moved a client to a different policy, now the backup fails with client hostname could not be found (48). What should I check? Thanks TC --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] RE: on the subject of disk based backups....
Good Morning -- I'm curious about the CPU hit and overall throughput of VTL vs DSU or DSSU backups. How many concurrent backups can run from a single server? The most I can run on my servers with DSUs is 10 per server. --kathy To: Paul Keating [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] on the subject of disk based backups From: [EMAIL PROTECTED] Date: Thu, 23 Mar 2006 15:59:33 + This is a multipart message in MIME format. --=_alternative 0057D9418025713A_= Content-Type: text/plain; charset=us-ascii Yeah, for me the biggest weakness of the NBU DSSUs. Paul Keating [EMAIL PROTECTED] 23/03/2006 15:48 To: [EMAIL PROTECTED] cc: veritas-bu@mailman.eng.auburn.edu Subject:RE: [Veritas-bu] on the subject of disk based backups excellent info...Now that you mention itmy one small DSSU I have configured to offload to a specific tape pool, so I should have known that. That definately sways me in the direction of VTL then. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: March 23, 2006 8:30 AM To: Paul Keating Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] on the subject of disk based backups Hi Paul, from my experience what you say about DSSU is incorrect, a single DSSU cannot stage the data off to multiple tape tape pools - if you have a requirement to stage to different tape pools you need to have a at least one DSSU per tape pool, cheers Andy. Paul Keating [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 23/03/2006 13:05 To:veritas-bu@mailman.eng.auburn.edu cc: Subject:[Veritas-bu] on the subject of disk based backups I'm also interested in thoughts regarding VTL vs DSSU. DSSU interests me mostly because I can write multiple jobs at once without any regard for tape pool, mpx or not, retention, etc. ...then it all gets sorted out to appropriate tapes during the destaging VTL still presents itself to NBU as a tape, so each virtual tape drive must be licensed with Veritas, in additional to the physical tape drives (unless the VTL is run inline, though there could be issues there regarding estimated compression, etc.) Just a couple things off the top of my head. Just wondering who is using DSSU, adn who is using VTL, adn why you made that choiceie.what were the key requirements for your environment that made one option better than the other. Paul ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Sharing tapedrives with Linux Media servers
Thanks Austin, I knew that the make_scsi_dev command created the links; it didn't occur to me that it was the culprit that destroyed them. I'll give the disabling the execute bit a try. On Wed, 22 Mar 2006, Austin Murphy wrote: Date: Wed, 22 Mar 2006 13:59:41 -0500 From: Austin Murphy [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Sharing tapedrives with Linux Media servers I have a very similar config and the problem seems to lie in the linux command make_scsi_dev which creates and/or deletes the device links that netbackup uses. If a drive is in use, it will delete the link to it for some (dumb?) reason. make_scsi_dev gets run on every startup. Once all the links were created, I disabled the execute bit on this command. This obviously doesn't address the root cause, but it stops the problem. Austin On 3/22/06, Kathryn Hemness [EMAIL PROTECTED] wrote: Greetings, I've been fighting with sharing tapedrives with a Linux media server for about a month now and I'd really appreciate some help. My problem lies not with the sharing but with the linux device paths becoming unconfigured when the linux server is rebooted. I have 2 Solaris servers and 1 Linux server, and the drives are in an 8-drive library connected to a fiber-channel switch. When I reboot the Linux server when any of the tape drives is in use by the other servers, my Linux server won't configure any of them and ltid won't start. This behavior is unique to shared tape drives; if I configure a couple of drives in the library as dedicated to the Linux media server, then the device files persist across reboots. I've just ordered 2 more Linux boxes to replace the Solaris boxes because of their superior throughput so I have to get this issue resolve. Thanks for any help. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Sharing tapedrives with Linux Media servers
Thanks for this great tip, Austin. Rather than disabling the execution bit, I commented out the execution of the make_scsi_dev from the init.d/netbackup script. And this modification worked. I double-checked my /proc/scsi/scsi file to make sure that all of the tape drives were, indeed, detected at boot and was quite pleased to find that they were. So now I can get back to sharing the tape drives between all of my media servers. On Wed, 22 Mar 2006, Austin Murphy wrote: Date: Wed, 22 Mar 2006 13:59:41 -0500 From: Austin Murphy [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Sharing tapedrives with Linux Media servers I have a very similar config and the problem seems to lie in the linux command make_scsi_dev which creates and/or deletes the device links that netbackup uses. If a drive is in use, it will delete the link to it for some (dumb?) reason. make_scsi_dev gets run on every startup. Once all the links were created, I disabled the execute bit on this command. This obviously doesn't address the root cause, but it stops the problem. Austin On 3/22/06, Kathryn Hemness [EMAIL PROTECTED] wrote: Greetings, I've been fighting with sharing tapedrives with a Linux media server for about a month now and I'd really appreciate some help. My problem lies not with the sharing but with the linux device paths becoming unconfigured when the linux server is rebooted. I have 2 Solaris servers and 1 Linux server, and the drives are in an 8-drive library connected to a fiber-channel switch. When I reboot the Linux server when any of the tape drives is in use by the other servers, my Linux server won't configure any of them and ltid won't start. This behavior is unique to shared tape drives; if I configure a couple of drives in the library as dedicated to the Linux media server, then the device files persist across reboots. I've just ordered 2 more Linux boxes to replace the Solaris boxes because of their superior throughput so I have to get this issue resolve. Thanks for any help. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Examples of SSO vm.conf files
Jim and everyone who responded, Thanks for all of the details. Using them, I was able to configure the drives on both the master and media servers. However, to get the I/O to be split between the master and media servers, I had to create 2 separate storage units: one on the master with maxdrives=2 and the other on the media server with maxdrives=2. Then I altered my tape duplication script on the media server to reference the media server's storage unit. For brevity's sake, the only difference between the tpconfigs of the master and media servers are the DrivePath names and the defined robotics. The master server has TLD(0) with a robotic path and with a volume database host specifying itself, and the media server has TLD(0) specifying the master as both the robot control host and the volume database host. The storage unit configurations both specify Robot 0 as the robot number, but one has the master as the media server and the other has the media server. On Sat, 28 Jan 2006, Jim Peppas wrote: Date: Sat, 28 Jan 2006 21:58:30 +0200 From: Jim Peppas [EMAIL PROTECTED] To: 'Kathryn Hemness' [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Hi. I think there is a mixup here. Do you want to share all drives or just split half of the drives to each media server? SSO drives have to have the same name If you want to share all drives , you have to do the following: 1. Delete all Netbackup entries of all drives on all Master/media Servers. 2. Configure the drives on the first Media server (it might be the master, no problem) using names that refer to the Library , not the server. The simplest way is to run : /usr/openv/volmgr/bin/tpautoconf -set_gdbhost Master_server /usr/openv/volmgr/bin/tpautoconf -a 3. After you finish the configuration of the drives, by running a vmoprcmd command on that server see entries like: PENDING REQUESTS NONE DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart2 TLD- No - - 1 hcart2 TLD- No - - 2 hcart2 TLD- No - - 3 hcart2 TLD- No - - ADDITIONAL DRIVE STATUS Drv DriveNameSharedAssignedComment 0 LIBA_LTO-1 No - 1 LIBA_LTO-2 No - 2 LIBA_LTO-3 No - 3 LIBA_LTO-4 No - 4. From the Java Admin.Console do the following (Note: If you have a Window Admin Console, all this stuff is much easier, since the Windows Console allows browsing for devices, while Java does not. In Java you have to know the expact paths for the drives) Run the Device Configuration Wizard (Recommended by Veritas). In the list with the hosts there should be the first server. Add the rest of them. By clicking throuout the rest of the wizard you should, at the end, have automatically have all drives as shared on all servers. If you run vmoprcmd again the Shared status should have changed from No to Yes. Be sure to have installed an SSO key on each of your servers involved before running the wizard. From this point on you have to define storage units for each media server. If you don't want servers to use all available drive, set the Max concurrent drives option to the desired amount (If you have 4 drives and want each server to use 2, put 2). This means that the servers will use 2 drives max (Note: not 2 specific drives, any 2 drives available). It is also possible to run steps 1 and 4 only. You can try this first. Usually, the only setback you have is that Netbackup gives the Drive names. You have to change the names later on to your desired names. That why I run usually configure the drives first on the robot controller and then run the wizard Sorry for being too detailed. Regards, Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Saturday, January 28, 2006 6:04 AM To: Scott Jacobson Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Scott - Thanks for the vote of confidence, but I'm not there yet. Both the master and media servers are in each other's bp.conf file. I have a single robot with 4 drives in it. The drives are all visible on both of the servers. I've renamed the drives accessed from the media server differently from their corresponding device names on the master server. I used tpconfig on each server to assign the drives to Robot 0. In the Device Monitor in NetBackup java gui, I see 8 shared drives. All 4 drives are in use; 2
RE: [Veritas-bu] Examples of SSO vm.conf files
Thanks, Jim - The steps worked and now all 4 of my drives are shared and duplications are running. But 2 duplications are coming directly from the media server and the I/O is still going through the master according to iostat on the master. On Sat, 28 Jan 2006, Jim Peppas wrote: Date: Sat, 28 Jan 2006 21:58:30 +0200 From: Jim Peppas [EMAIL PROTECTED] To: 'Kathryn Hemness' [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Hi. I think there is a mixup here. Do you want to share all drives or just split half of the drives to each media server? SSO drives have to have the same name If you want to share all drives , you have to do the following: 1. Delete all Netbackup entries of all drives on all Master/media Servers. 2. Configure the drives on the first Media server (it might be the master, no problem) using names that refer to the Library , not the server. The simplest way is to run : /usr/openv/volmgr/bin/tpautoconf -set_gdbhost Master_server /usr/openv/volmgr/bin/tpautoconf -a 3. After you finish the configuration of the drives, by running a vmoprcmd command on that server see entries like: PENDING REQUESTS NONE DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart2 TLD- No - - 1 hcart2 TLD- No - - 2 hcart2 TLD- No - - 3 hcart2 TLD- No - - ADDITIONAL DRIVE STATUS Drv DriveNameSharedAssignedComment 0 LIBA_LTO-1 No - 1 LIBA_LTO-2 No - 2 LIBA_LTO-3 No - 3 LIBA_LTO-4 No - 4. From the Java Admin.Console do the following (Note: If you have a Window Admin Console, all this stuff is much easier, since the Windows Console allows browsing for devices, while Java does not. In Java you have to know the expact paths for the drives) Run the Device Configuration Wizard (Recommended by Veritas). In the list with the hosts there should be the first server. Add the rest of them. By clicking throuout the rest of the wizard you should, at the end, have automatically have all drives as shared on all servers. If you run vmoprcmd again the Shared status should have changed from No to Yes. Be sure to have installed an SSO key on each of your servers involved before running the wizard. From this point on you have to define storage units for each media server. If you don't want servers to use all available drive, set the Max concurrent drives option to the desired amount (If you have 4 drives and want each server to use 2, put 2). This means that the servers will use 2 drives max (Note: not 2 specific drives, any 2 drives available). It is also possible to run steps 1 and 4 only. You can try this first. Usually, the only setback you have is that Netbackup gives the Drive names. You have to change the names later on to your desired names. That why I run usually configure the drives first on the robot controller and then run the wizard Sorry for being too detailed. Regards, Jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kathryn Hemness Sent: Saturday, January 28, 2006 6:04 AM To: Scott Jacobson Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Scott - Thanks for the vote of confidence, but I'm not there yet. Both the master and media servers are in each other's bp.conf file. I have a single robot with 4 drives in it. The drives are all visible on both of the servers. I've renamed the drives accessed from the media server differently from their corresponding device names on the master server. I used tpconfig on each server to assign the drives to Robot 0. In the Device Monitor in NetBackup java gui, I see 8 shared drives. All 4 drives are in use; 2 on drives defined on the Master and the other 2 on the drives defined on the media server. Here's sort of what it looks like MasterDrive1= TLD ; MediaDrive1 = PEND-TLD MasterDrive2= DOWN-TLD ; MediaDrive2 = TLD MasterDrive3= DOWN-TLD ; MediaDrive3 = TLD MasterDrive4= TLD ; MediaDrive4 = PEND-TLD Error messages on my media server indicates RESERVATION CONFLICT for 2 scsi devices (probably the MasterDrive[23] indicated above). My duplications are running at fair speeds, but there's not been a need for a tape dismount/remount for tapes in use by my media server. The reason I had thought there might be a need for individual vm.conf files is because the NB51 Media Manager Guide indicates about 4 SSO settings
[Veritas-bu] Examples of SSO vm.conf files
Greetings - I'm trying to setup SSO for an LTO2 library shared between a Solaris 9 Master and a RHEL3 Linux Media server. Can someone give me examples of the vm.conf files on each server? Right now, I'm using an evaluation license and I can see drives on both Master and Media servers and the robotic is controlled by the Master. However, all of the traffic is still going through the Master server. The Master server has a vm.conf but my Linux media server doesn't. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Examples of SSO vm.conf files
Hi Mark -- Here are my tpconfigs on both the Master and Media servers: Master server: /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Hagrid-1 /dev/rmt/3cbnhcart2 Yes UP TLD(0) Definition DRIVE=1 1 Hagrid-2 /dev/rmt/2cbnhcart2 Yes UP TLD(0) Definition DRIVE=2 2 Hagrid-3 /dev/rmt/1cbnhcart2 Yes UP TLD(0) Definition DRIVE=3 3 Hagrid-4 /dev/rmt/0cbnhcart2 Yes UP TLD(0) Definition DRIVE=4 Currently defined robotics are: TLD(0) robotic path = /dev/sg/c0tw2001005013e00369l1, volume database host = albus.ucdavis.edu *** Media Server:# /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Hagrid-1 /dev/st/nh1c0t0l2hcart2 Yes UP TLD(0) Definition DRIVE=1 1 Hagrid-2 /dev/st/nh1c0t0l3hcart2 Yes UP TLD(0) Definition DRIVE=2 2 Hagrid-3 /dev/st/nh1c0t0l4hcart2 Yes UP TLD(0) Definition DRIVE=3 3 Hagrid-4 /dev/st/nh1c0t0l5hcart2 Yes UP TLD(0) Definition DRIVE=4 Currently defined robotics are: TLD(0) robot control host = albus.ucdavis.edu volume database host = albus.ucdavis.edu All I/O is still going through the device paths of the Master Server. On Fri, 27 Jan 2006 [EMAIL PROTECTED] wrote: Date: Fri, 27 Jan 2006 15:51:24 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files It's not vm.conf, it's tpconfig. Be sure which drives are the shared ones, ie /dev/rmt/x on server1 is /dev/rmtY on server2. Then carefully setup the drives as shared drives via tpconfig. vm.conf is plain. Really, the manual is your friend on an SSO setup. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathryn Hemness Sent: Friday, January 27, 2006 2:26 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Examples of SSO vm.conf files Greetings - I'm trying to setup SSO for an LTO2 library shared between a Solaris 9 Master and a RHEL3 Linux Media server. Can someone give me examples of the vm.conf files on each server? Right now, I'm using an evaluation license and I can see drives on both Master and Media servers and the robotic is controlled by the Master. However, all of the traffic is still going through the Master server. The Master server has a vm.conf but my Linux media server doesn't. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Examples of SSO vm.conf files
I need to create a separate storage unit for the media server even if the robotic is controlled by the master? I haven't done this yet. On Fri, 27 Jan 2006 [EMAIL PROTECTED] wrote: Date: Fri, 27 Jan 2006 17:18:45 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Did you create new storage units for your media server? Reboot? Assign your policy to the new storage unit? Make sure that your both servers have the other in their bp.conf file. Best guarantee is to have each labeled as a SERVER rather than a MEDIASERVER. Master server is listed first, of course, in both servers. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathryn Hemness Sent: Friday, January 27, 2006 4:42 PM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Hi Mark -- Here are my tpconfigs on both the Master and Media servers: Master server: /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Hagrid-1 /dev/rmt/3cbnhcart2 Yes UP TLD(0) Definition DRIVE=1 1 Hagrid-2 /dev/rmt/2cbnhcart2 Yes UP TLD(0) Definition DRIVE=2 2 Hagrid-3 /dev/rmt/1cbnhcart2 Yes UP TLD(0) Definition DRIVE=3 3 Hagrid-4 /dev/rmt/0cbnhcart2 Yes UP TLD(0) Definition DRIVE=4 Currently defined robotics are: TLD(0) robotic path = /dev/sg/c0tw2001005013e00369l1, volume database host = albus.ucdavis.edu *** Media Server:# /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Hagrid-1 /dev/st/nh1c0t0l2hcart2 Yes UP TLD(0) Definition DRIVE=1 1 Hagrid-2 /dev/st/nh1c0t0l3hcart2 Yes UP TLD(0) Definition DRIVE=2 2 Hagrid-3 /dev/st/nh1c0t0l4hcart2 Yes UP TLD(0) Definition DRIVE=3 3 Hagrid-4 /dev/st/nh1c0t0l5hcart2 Yes UP TLD(0) Definition DRIVE=4 Currently defined robotics are: TLD(0) robot control host = albus.ucdavis.edu volume database host = albus.ucdavis.edu All I/O is still going through the device paths of the Master Server. On Fri, 27 Jan 2006 [EMAIL PROTECTED] wrote: Date: Fri, 27 Jan 2006 15:51:24 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files It's not vm.conf, it's tpconfig. Be sure which drives are the shared ones, ie /dev/rmt/x on server1 is /dev/rmtY on server2. Then carefully setup the drives as shared drives via tpconfig. vm.conf is plain. Really, the manual is your friend on an SSO setup. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathryn Hemness Sent: Friday, January 27, 2006 2:26 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Examples of SSO vm.conf files Greetings - I'm trying to setup SSO for an LTO2 library shared between a Solaris 9 Master and a RHEL3 Linux Media server. Can someone give me examples of the vm.conf files on each server? Right now, I'm using an evaluation license and I can see drives on both Master and Media servers and the robotic is controlled by the Master. However, all of the traffic is still going through the Master server. The Master server has a vm.conf but my Linux media server doesn't. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax
RE: [Veritas-bu] Examples of SSO vm.conf files
Scott - Did I miss something here? Did you intend to show me the results of your vmoprcmd or a tpconfig -d? On Fri, 27 Jan 2006, Scott Jacobson wrote: Date: Fri, 27 Jan 2006 17:32:00 -0700 From: Scott Jacobson [EMAIL PROTECTED] To: [EMAIL PROTECTED], Kathryn Hemness [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Kathryn, In a SSO environment your Drive Names must be unique. In my environment for example, from the Master, run vmoprcmd. These are the names I use to keep things straight. -sj Kathryn Hemness [EMAIL PROTECTED] 1/27/2006 4:41 pm Hi Mark -- Here are my tpconfigs on both the Master and Media servers: Master server: /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Hagrid-1 /dev/rmt/3cbnhcart2 Yes UP TLD(0) Definition DRIVE=1 1 Hagrid-2 /dev/rmt/2cbnhcart2 Yes UP TLD(0) Definition DRIVE=2 2 Hagrid-3 /dev/rmt/1cbnhcart2 Yes UP TLD(0) Definition DRIVE=3 3 Hagrid-4 /dev/rmt/0cbnhcart2 Yes UP TLD(0) Definition DRIVE=4 Currently defined robotics are: TLD(0) robotic path = /dev/sg/c0tw2001005013e00369l1, volume database host = albus.ucdavis.edu *** Media Server:# /usr/openv/volmgr/bin/tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Hagrid-1 /dev/st/nh1c0t0l2hcart2 Yes UP TLD(0) Definition DRIVE=1 1 Hagrid-2 /dev/st/nh1c0t0l3hcart2 Yes UP TLD(0) Definition DRIVE=2 2 Hagrid-3 /dev/st/nh1c0t0l4hcart2 Yes UP TLD(0) Definition DRIVE=3 3 Hagrid-4 /dev/st/nh1c0t0l5hcart2 Yes UP TLD(0) Definition DRIVE=4 Currently defined robotics are: TLD(0) robot control host = albus.ucdavis.edu volume database host = albus.ucdavis.edu All I/O is still going through the device paths of the Master Server. On Fri, 27 Jan 2006 [EMAIL PROTECTED] wrote: Date: Fri, 27 Jan 2006 15:51:24 -0700 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Examples of SSO vm.conf files It's not vm.conf, it's tpconfig. Be sure which drives are the shared ones, ie /dev/rmt/x on server1 is /dev/rmtY on server2. Then carefully setup the drives as shared drives via tpconfig. vm.conf is plain. Really, the manual is your friend on an SSO setup. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Kathryn Hemness Sent: Friday, January 27, 2006 2:26 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Examples of SSO vm.conf files Greetings - I'm trying to setup SSO for an LTO2 library shared between a Solaris 9 Master and a RHEL3 Linux Media server. Can someone give me examples of the vm.conf files on each server? Right now, I'm using an evaluation license and I can see drives on both Master and Media servers and the robotic is controlled by the Master. However, all of the traffic is still going through the Master server. The Master server has a vm.conf but my Linux media server doesn't. --kathy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu --kathy === Kathryn Hemness[EMAIL PROTECTED] System Administrator phone: 530.752.6547 Campus Data Center Client Services fax: 530.752.9154 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Examples of SSO vm.conf files
Scott - Thanks for the vote of confidence, but I'm not there yet. Both the master and media servers are in each other's bp.conf file. I have a single robot with 4 drives in it. The drives are all visible on both of the servers. I've renamed the drives accessed from the media server differently from their corresponding device names on the master server. I used tpconfig on each server to assign the drives to Robot 0. In the Device Monitor in NetBackup java gui, I see 8 shared drives. All 4 drives are in use; 2 on drives defined on the Master and the other 2 on the drives defined on the media server. Here's sort of what it looks like MasterDrive1= TLD ; MediaDrive1 = PEND-TLD MasterDrive2= DOWN-TLD ; MediaDrive2 = TLD MasterDrive3= DOWN-TLD ; MediaDrive3 = TLD MasterDrive4= TLD ; MediaDrive4 = PEND-TLD Error messages on my media server indicates RESERVATION CONFLICT for 2 scsi devices (probably the MasterDrive[23] indicated above). My duplications are running at fair speeds, but there's not been a need for a tape dismount/remount for tapes in use by my media server. The reason I had thought there might be a need for individual vm.conf files is because the NB51 Media Manager Guide indicates about 4 SSO settings for the vm.conf and I was wondering about whether or not the Master and Media servers should contain the same entries, and I don't even have a vm.conf file on my Media server. Anyway, I can't do any more work on the tpconfig stuff because my peak backup windows just opened. I'll do some more tweaking tomorrow if the media server RESERVATION CONFLICTS don't down all of the drives. I'm cc'ing this back to the list in case there are others who can shed light on this subject. On Fri, 27 Jan 2006, Scott Jacobson wrote: Date: Fri, 27 Jan 2006 19:32:44 -0700 From: Scott Jacobson [EMAIL PROTECTED] To: Kathryn Hemness [EMAIL PROTECTED] Subject: RE: [Veritas-bu] Examples of SSO vm.conf files Kathryn, From a SSO standpoint you should be able to use robtest to verify you can move tapes to drives onto the media server tape drives FROM the Master Server If not, as Mark mentioned, make sure the conf files on both Master and Media Servers know of one another - very important. Storage Unit definition needs both Master and Media server host names and then applied to your Dup policy. I think your there... need to depart soon. -sj Kathryn Hemness [EMAIL PROTECTED] 1/27/2006 6:29 pm Hi Scott - I've made some changes for unique drive names. The drives on my Master server are Hagrid-* and the corresponding names on my media server are Olympe-*. I've not defined 2 robotics; I still only have 1 robot defined. This shared storage unit is for duplicating disk-staged backups only; no backup policies use it. That said, here are the results of the vmoprcmd on both my master and media servers: /usr/openv/volmgr/bin/vmoprcmd on the Master: PENDING REQUESTS NONE DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart2 TLD- No - - 1 hcart2 TLD- No - - 2 hcart2 TLD- No - - 3 hcart2 TLD- No - - ADDITIONAL DRIVE STATUS Drv DriveNameSharedAssignedComment 0 Hagrid-1 Yes - 1 Hagrid-2 Yes - 2 Hagrid-3 Yes - 3 Hagrid-4 Yes - [/] /usr/openv/volmgr/bin/vmoprcmd on the Media Server: # ./vmoprcmd PENDING REQUESTS NONE DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId 0 hcart2 TLD- No - - 1 hcart2 TLD- No - - 2 hcart2 TLD- No - - 3 hcart2 TLD- No - - ADDITIONAL DRIVE STATUS Drv DriveNameSharedAssignedComment 0 Olympe-1 Yes - 1 Olympe-2 Yes - 2 Olympe-3 Yes - 3 Olympe-4 Yes - Here's my new tpconfig on the Media server: # ./tpconfig -d Index DriveName DrivePathTypeShared Status * * ** ** ** 0 Olympe-1 /dev/st/nh1c0t0l2hcart2 Yes UP TLD(0) Definition DRIVE=1 1 Olympe-2 /dev/st/nh1c0t0l3hcart2 Yes UP TLD(0) Definition DRIVE=2 2 Olympe
