Re: [Veritas-bu] Expired media not returning to SCRATCH Vault
I suspect that there's something else at the root... (and not likely vault related) When a tape is suspended, it won't be used for any write operations until it expires. When all the images expire, cleanup operations will run and it should become un-suspended and made available for use. This differs from frozen in that frozen media require manual intervention (even after all images expire). So, the first course of action is to determine why the media isn't becoming expired. 1. When your cleanup jobs run, what is the exit status code? Zero or something else? - You can initiate a cleanup job by running 'bpimage -cleanup' 2. If you run bpexpdate -deassignempty, what happens? 3. What happens when you un-suspend the media? (bpmedia -unsuspend -m string -v [-h hostname]) 4. In either case above, what does all log entries report tell you? How about any relevant logs? (e.g. bpdbm) 5. What are the sample outputs of vmquery and nbemmcmd against the media? vmquery -m string nbemmcmd -listmedia -mediaid string Where string is the media id in question Don't forget to also provide bpmedialist and bpimmedia too. Now, if all of that is working (which I'm guessing you'll find isn't), you come back to the question of why isn't the media going to scratch. Well, the previous pool needs to have been scratch. You can see this in the nbemmcmd requested above. -Tim P.S. Do you have a support contract? Now would be a good time to call... hint, hint, nudge, nudge 2009/9/15 Jorge Fábregas jorge.fabre...@gmail.com On Tuesday 15 September 2009 03:52:26 pm Jorge Fábregas wrote: I just did that (rich-clicked it: unsuspend) and then later ran bpimage -cleanup but the tape is still on the vault volume pool (it won't go to Scratch as I expected). When I manually try to expire the tape I get this error: -- #bpexpdate -m 000248 -d 0 -force database system error - I'm doing some Google search..a couple of persons with sames issues. I will report back. Jorge ___ 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] sgscan panics new Solaris 10 media server
And have you contacted SUN? I recall an issue a long time ago (so can't remember details) where sgscan could cause a panic on a Solaris system. Seems to me it was related to HBA drivers and how they handled the scsi commands sgscan runs. There's also the 'scan' command too. It's probably doing the same things as sgscan (scsi inquiry IIRC) so would likely do the same thing, but it's at least a way to find out if it's a problem with JUST sgscan. A quick Google search found at least one TN from Symantec too: http://seer.entsupport.symantec.com/docs/206544.htm And SUN: http://sunsolve.sun.com/search/document.do?assetkey=1-21-114878-10-1 -Tim On Wed, Jul 15, 2009 at 2:49 PM, Len Boyle len.bo...@sas.com wrote: Do uou have a crash dump. If so have you looked at it? *From:* veritas-bu-boun...@mailman.eng.auburn.edu [mailto: veritas-bu-boun...@mailman.eng.auburn.edu] *On Behalf Of *Marianne Van Den Berg *Sent:* Wednesday, July 15, 2009 3:47 PM *To:* VERITAS-BU@MAILMAN.ENG.AUBURN.EDU *Subject:* [Veritas-bu] sgscan panics new Solaris 10 media server Hi Everyone NetBackup 6.5.4 server software installed on server that used to do backups over the network up to now. sgscan causes kernel panic (as well as tpautoconf -t). QLogic QLA2462 hba with Leadville driver. We have logged a Sev 1 call with Symantec - all they could suggest in the 3 hours since the call has been logged was to 'disable tcp fusion'! Any ideas will be welcome. Kind Regards Marianne ___ 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] 6.5.4 FA results
What is the reporting software? Thanks -Tim On Thu, May 28, 2009 at 6:43 AM, WALLEBROEK Bart bart.wallebr...@swift.comwrote: Message: 10 Date: Thu, 28 May 2009 11:35:37 +0200 From: Akker Henk van den h.vandenak...@wml.nl Subject: [Veritas-bu] 6.5.4 FA results To: veritas-bu@mailman.eng.auburn.edu Message-ID: a379e5c5c5edd64e909a2aa2a8a566800119c...@exchmail.wml.nl Content-Type: text/plain; charset=us-ascii Hello, I'm curious whether there are people who already upgraded to the new version? Henk van den Akker I have upgraded 2 remote production environments last week Friday (1 small environment (1 Master/Media) and a large one (clustered Master)). On NetBackup side I did not see ANY issue. The only issue we have right now is that our backup reporting software (none-NetBackup) does not recognize the version of NetBackup so it cannot update. This issue should be solved by the end of this week. I plan to upgrade 2 other remote environments (1 large and 1 small) next week and after another 2 weeks I will upgrade our 2 main environments (1 large (1 Master + 1 Media Server) and 1 very large one (clustered Master + 34 Media Servers)) Best Regards, Bart WALLEBROEK Backup Admin S.W.I.F.T. ___ 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] bpduplicate socket read failed
Supported or not, that TN is highlighting a scenario that is far from recommended! -tim On May 16, 2009, at 9:23 AM, Marianne Van Den Berg mvdb...@stortech.co.za wrote: I beg to differ, Ed. This TechNote says it’s supported: http://seer.entsupport.symantec.com/docs/270101.htm See the section under this heading: Use of multiple DSSUs on the same volume M. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu ] On Behalf Of Ed Wilts Sent: 16 May 2009 08:33 To: ss...@singnet.com.sg Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] bpduplicate socket read failed On Fri, May 15, 2009 at 11:09 PM, ssloh ss...@singnet.com.sg wrote: It happens to all bpduplicate jobs whenever I try any DSSU Manual Relocation. The DSSU is 3.5 TB on SATA disks, it was divided into different folder for daily, weekly and monthly backup Hence, I have 3 DSSU setup with S:\daily; S:\weekly and S:\monthly The DSSU is formated as NTFS This is NOT supported - you can't put multiple DSSUs on the same disk. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org This email has been scanned for viruses and malware, and automatically archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS) for business. Mimecast Unified Email Management ™ (UEM) offers email continuity, security, archiving and compliance with all current legislation. To find out more, contact S torTech. stormcid ___ 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] What to do about media stuck in the media DB (plausibly due to storage lifecycle policies)
(Reply to all this time)... Any allocations for that media id? nbrbutil -cleandump (if cleandump doesn't work, just use -dump - this was an updated option, but i don't recall the version). From there, you can use other options on nbrbutil to release that given allocation (just be sure that there really aren't any other jobs waiting for the resource) -Tim On Mon, May 11, 2009 at 12:23 PM, Rosenkoetter, Gabriel gabriel.rosenkoet...@radian.biz wrote: PS, yes, there was still a duplication job active looking for media ID 000680. After cancelling that job, however, I am still unable to nuke these images (nbstlutil list is still blank for the media ID). -- Gabriel Rosenkoetter Radian Group Inc, Senior Systems Engineer gabriel.rosenkoet...@radian.biz, 215 231 1556 -Original Message- From: Rosenkoetter, Gabriel Sent: Monday, May 11, 2009 1:03 PM To: veritas-bu@mailman.eng.auburn.edu Subject: What to do about media stuck in the media DB (plausibly due to storage lifecycle policies) There is a question down at the bottom of this (how do I actually remove a media ID that I know is unuseable and doesn't hold an unexpired images from the media DB?), but a bit on what I've done so far: I have a very old piece of 9940 media: [97] vmquery -m 000680 media ID: 000680 media type:1/2 cartridge tape 2 (14) barcode: 000680 media description: Added by Media Manager volume pool: 00_NetBackup (11) robot type:NONE - Not Robotic (0) volume group: --- vault name:--- vault sent date: --- vault return date: --- vault slot:--- vault session id: --- vault container id:- created: Tue Feb 22 15:47:00 2005 assigned: Sat Apr 18 13:00:02 2009 last mounted: Sun Apr 26 21:15:10 2009 first mount: Fri May 20 17:27:16 2005 expiration date: --- number of mounts: 626 max mounts allowed:--- status:0x0 It was frozen due to write errors (and periodically throws read errors as well) and, given its age and mount count, I concluded that it was time to pull it out of service after my SLPs had managed to get everything they could off of it and the images on it had expired, which they now have: [98] bpmedialist -m 000680 Server Host = phlmaster id rl images allocatedlast updated density kbytes restores vimages expiration last read --- STATUS --- 000680 1 40 04/18/2009 13:00 04/20/2009 20:04 hcart238214373 0 MPX 05/04/2009 20:04 04/19/2009 10:59 EXPIRED FROZEN It is, however, apparently locked in the media DB (because there's an unreadable image and SLPs are still trying to duplicate those images, I thought): [96] bpmedia -unfreeze -m 000680 requested media id is in use, cannot process request r...@pa2ibks2:/usr/openv/netbackup/vault/sessions/P472B [99] bpexpdate -m 000680 -d 0 Are you SURE you want to delete 000680 y/n (n)? y requested media id is in use, cannot process request Here are the lifecycles that are trying to read that tape (ignore what the man page says about nbstlutil list's output being just for support, it's plenty readable): [124] nbstlutil list -U -mediaid 000680 Image: Master Server: phlmaster Backup ID: pa02qrin02_1240271378 Client : pa02qrin02 Backup Time : 1240271378 (Mon Apr 20 19:49:38 2009) Policy : VM_Instances Client Type : 13 Schedule Type: 4 Storage Lifecycle Policy : Cumulatives Storage Lifecycle State : 2 (IN_PROCESS) Time In Process : 1240272689 (Mon Apr 20 20:11:29 2009) Data Classification ID : (none specified) Copy: Master Server : phlmaster Backup ID : pa02qrin02_1240271378 Copy Number : 1 Expire Time : 2147483647 (Mon Jan 18 22:14:07 2038) Try To Keep Time: 1241480978 (Mon May 4 19:49:38 2009) Residence : PHL-9940b Duplication Status : 3 (COMPLETE) Job ID : 0 Retention Type : 0 (FIXED) MPX State : 1 Fragment: Master Server : phlmaster Backup ID : pa02qrin02_1240271378 Copy Number : 1 Fragment Number : 1 Resume Count : 0 Media ID : 000680 Media Server : phlmaster Storage Server: (none specified) Media Type: 2 (RMEDIA) Media Sub-Type: 0 (DEFAULT) Fragment State: 1 (ACTIVE) Fragment Size : 0 Delete Header : 1 Fragment ID
Re: [Veritas-bu] Share the robotic arm with VTL ?
There's no need to share a robotic arm (Physical or VTL based). You have one media server be the robotic control host and then when you configure the robot on additional media servers, you point to that host as the controller. HTH -Tim On Fri, May 8, 2009 at 2:37 AM, ldrolez netbackup-fo...@backupcentral.comwrote: Hi ! Does anyone know how I could share a VTL robotic arm (falconstor) in a Media Server Pool ? Is there a trick (iscsi...) ? Best regards, Ludovic. -- http://www.geeksback.com - Secure File Backups for Geeks http://www.palmopensource.com - The PalmOS Open Source Portal +-- |This was sent by ldro...@debian.org via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Share the robotic arm with VTL ?
Currently, there's no failover option (i.e. shared robotics option). I don't think this is a new request, but telling your favorite Symantec Sales team would be a good thing to do so it gets more weight added to it. -Tim On Fri, May 8, 2009 at 10:50 AM, ldrolez netbackup-fo...@backupcentral.comwrote: Yes but if you want some kind of failover ? +-- |This was sent by ldro...@debian.org via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Problem installing 6.5.3 client on RHEL 5 server
NB_6.5.3 is the server patch. If this is a pure client only system, then you need the NB_CLT_6.5.3 patch. The error happens because the installer is looking for a /usr/openv/ netbackup/version file. That file only exists in servers. The client version is kept at /usr/openv/netbackup/bin/version. HTH -Tim On Mar 11, 2009, at 10:19 AM, brent4313 netbackup-fo...@backupcentral.com wrote: Has anyone else run into this? There is 1 pack available in /home/*: (* denotes installed pack) NB_6.5.3 Enter pack name (or q) [q]: NB_6.5.3 ERROR: No readable product version file was found, please verify the version file exists and that this pack is appropriate for this system. There is 1 pack available in /home/*: (* denotes installed pack) NB_6.5.3 Enter pack name (or q) [q]: NB_6.5.3 ERROR: No readable product version file was found, please verify the version file exists and that this pack is appropriate for this system. There is 1 pack available in /home/*: (* denotes installed pack) NB_6.5.3 Enter pack name (or q) [q]: q Exiting NB_update.install +-- |This was sent by brent.degenn...@morris.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Using Fiber Channel Drives in 6.5
What's in /proc/scsi/scsi? # cat /proc/scsi/scsi -Tim On Wed, Mar 4, 2009 at 5:18 PM, jthompson netbackup-fo...@backupcentral.com wrote: Thanks for replies. Tim- I've ran the make_scsi_dev and it did populate the /dev/sg directory with 2 robotic control files. Matt- scan returns the following: #./scan *** SDT_TAPE *** SDT_CHANGER *** SDT_OPTICAL It appears that the drivers aren't installed correctly as it only returns this and not the info for the library or the drives. +-- |This was sent by jthomp...@edmunds.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Using Fiber Channel Drives in 6.5
You don't need a SAN/SSO license unless you are sharing the devices between hosts. Have you looked through the device config guide and checked for the appropriate pass-through devices? Device Configuration Guide for UNIX, Linux, and Windows ( http://seer.entsupport.symantec.com/docs/290200.htm ) In particular, did you run the make_scsi_dev command? -Tim On Wed, Mar 4, 2009 at 2:05 PM, Thompson, Jeff jthomp...@edmunds.comwrote: We’ve recently purchased a Scaler i500 with 2 fiber channel drives. This is being connected via HBA to our RHEL 3 Master Server (running the 2.4 kernel). I have verified that the OS sees the card and drives but I can’t get them installed in NBU. I’m guessing that I’m missing a SAN license, is this correct? Thanks! ___ 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] WORM backups...
WORM media is unique in NBU. Make sure you read the SAG regarding all the specifics. All 6.5 documentation: http://seer.entsupport.symantec.com/docs/290282.htm Pull up the System Administrator's Guide for Windows, Volume 1 ( http://seer.entsupport.symantec.com/docs/290203.htm ) and start on page 589. One thing for sure, you need to create a volume pool who's name begins with WORM so NBU knows to treat the media as such. I'm afraid that if NBU thought the media in question were standard tapes, it treated them as such and in the course of operations the media may have been written in such a way that NBU can't continue to use them (i.e. an empty data block was written that NBU can normally overwrite, but now can't since it's a WORM tape). -Tim On Tue, Mar 3, 2009 at 4:13 PM, dbergen netbackup-fo...@backupcentral.comwrote: I have a backup policy that needs to use WORM tapes for archiving and I'm running into some trouble. When a backups kicks off all WORM tapes in the pool get marked as assigned and then the backup fails with status-96 no media available, if I add a regular LTO4 tape to the pool the backups run fine to that tape. Netbackup 6.5.3 on W2K. any help would be much appreciated, dj +-- |This was sent by dber...@cucbc.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Clearing DSSU's.
Here's the general process I think I would follow. First, stop directing any backups to DSSU until your maintenance is done. Run bpimmedia to see which images are on your dssu (bpimmedia -disk_stu stu label For each of those images, run bpimagelist to see how many copies there are (bpimagelist -backupid BID) For those images which don't have a copy on tape, duplicate it (kick off your de-stage job) For those images that do have multiple copies, expire the dssu copy (bpexpdate -backupid BID -d 0 -copy #) Repeat those steps until you're sure you have all your data protected. The bottom line though is to make sure that before you go deleting (expiring) anything, you've got the data protected. You don't want to accidentally erase an image that is ONLY on disk. -Tim On Mon, Jan 26, 2009 at 3:43 PM, Ed Wilts ewi...@ewilts.org wrote: On Mon, Jan 26, 2009 at 3:24 PM, Matthew Stier matthew.st...@us.fujitsu.com wrote: Background: Solaris 10 master/media server with several filesystems mounted from SAN to act as DSSU's. Backups are done using cron initiated backup scripts, which call the applicable policy. Whe the policy is completed, another script dumps each DSSU to tape. Issue: Need to rebuild the filesystems hosting the DSSU's. Since these tapes are already backed up to tape, what do I need to do to purge all the images? What you need to do is for each image on tape, verify that you have 2 copies and then expire the disk copy. It's a little bit tricky because you'll be expiring copy 1. If there is no copy 2 (say for some reason the image failed to destage), you've deleted your only copy. If all goes well, you'll have an empty DSSU in the end. You can also do a brute force rm of the disk images but that's a bit hostile since a restore will attempt to restore from disk rather than tape - you could expire the disk image if you run into this so that the tape copy is preferred, but as I said, it's ugly. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE ewi...@ewilts.org ___ 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] 6.5.3 on the FTP site
Doug, Where are you trying to download the patch containers? If it's not the Symantec FTP site, it probably wasn't ever there (i.e. the file connect site where I am occasionally sent to obtain a licensed piece of software). Here's the 6.5.3 Downloads available: http://seer.entsupport.symantec.com/docs/315028.htm Release Announcement: http://seer.entsupport.symantec.com/docs/315266.htm If you need to make use of FTP, here's the site/directory: ftp://ftp.entsupport.symantec.com/pub/support/products/NetBackup_Enterprise_Server The files are definitely there and have NOT been pulled. -Tim On Tue, Dec 2, 2008 at 2:32 PM, Preston, Doug [EMAIL PROTECTED] wrote: 6.5.3 GA has been pulled according to support @ Symantec, I called them to find out where it was on file connect and they pulled it about an hour or so after it was released. If you haven't upgraded yet I would wait till we find out what is broke. Doug Preston From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, December 02, 2008 7:01 AM To: Ed Wilts; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] 6.5.3 on the FTP site Im still focused on 6.5.2 upgrade from 5.1 MP5. Will wait a while to see if any problems or issues are reported before looking at this update. Cheers for this link Ed :-) Si From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Tuesday, December 02, 2008 2:47 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] 6.5.3 on the FTP site I heard that GA was going to be today but it appears that pieces started appearing on the FTP site yesterday. Here's the announcement: http://seer.entsupport.symantec.com/docs/315266.htm Enjoy! .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ 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] 6.5.3 on the FTP site
Ahh, now I see the confusion. You cannot get 6.5.3 as a base install. You'll have to install 6.5GA, then apply the 6.5.3 release update. HTH -Tim On Tue, Dec 2, 2008 at 3:18 PM, Preston, Doug [EMAIL PROTECTED] wrote: I don't want patch containers I want 6.5.3 to install Doug Preston Systems Engineer LandAmerica Financial Group, Inc. - 1123 South Park View DR, Covina CA 91724 Phone 626-339-5221 Ext 1104 Email [EMAIL PROTECTED] -- NOTICE: This electronic mail transmission may constitute a communication that is legally privileged. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this electronic mail transmission in error, notify the sender by reply e-mail so that our address record can be corrected, then please delete it from your system without copying it. --- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Coleman Sent: Tuesday, December 02, 2008 12:59 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 6.5.3 on the FTP site 6.5.3 patch containers are posted on the support download website. http://www.symantec.com/business/support/downloads.jsp?pid=15143 This is the preferred way to get it. It has NOT been pulled. We went generally available December 2nd. ___ 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] NBU 6.5.3
This is the First Availability program. It's limited to a small subset of customers. GA will be about 30 days later I guess. -Tim On Nov 7, 2008, at 4:13 PM, Peacock Dennis - dpeaco [EMAIL PROTECTED] wrote: I just finished a conference call on NBU puredisk and talked to one of the Symantec SEs, about the 11/12 release date. He told me he was on a conference call today with the product managers and was told it's slated for a December release; possibly January. He said if it was due out 11/12 he would have been notified about the date and he was not. Thank You, Dennis Peacock EBCA Acxiom Corporation 501-342-6232 (office) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Friday, November 07, 2008 3:48 PM To: Martin, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5.3 The Twelfth of Nover... :p -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Friday, November 07, 2008 2:57 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 6.5.3 FYI / I just got a note from Symantec that First Availability of 6.5.3 will be on Nov 12th. -Jonathan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu *** *** * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. *** *** ** ___ 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] Fwd: NBU 6.5.3
Meant this for the whole list. Begin forwarded message: From: Tim Hoke [EMAIL PROTECTED] Date: November 7, 2008 4:59:12 PM CST To: Peacock Dennis - dpeaco [EMAIL PROTECTED] Cc: Jeff Lightner [EMAIL PROTECTED], Martin, Jonathan [EMAIL PROTECTED] , VERITAS-BU@mailman.eng.auburn.edu VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5.3 This is the First Availability program. It's limited to a small subset of customers. GA will be about 30 days later I guess. -Tim On Nov 7, 2008, at 4:13 PM, Peacock Dennis - dpeaco [EMAIL PROTECTED] wrote: I just finished a conference call on NBU puredisk and talked to one of the Symantec SEs, about the 11/12 release date. He told me he was on a conference call today with the product managers and was told it's slated for a December release; possibly January. He said if it was due out 11/12 he would have been notified about the date and he was not. Thank You, Dennis Peacock EBCA Acxiom Corporation 501-342-6232 (office) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Friday, November 07, 2008 3:48 PM To: Martin, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5.3 The Twelfth of Nover... :p -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Friday, November 07, 2008 2:57 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 6.5.3 FYI / I just got a note from Symantec that First Availability of 6.5.3 will be on Nov 12th. -Jonathan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu *** *** * The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. *** *** *** *** ___ 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] Limit bandwidth
Take a look at the LIMIT_BANDWIDTH bp.conf paramater. Here's an applicable TechNote: http://seer.entsupport.symantec.com/docs/265707.htm -Tim On Tue, Oct 21, 2008 at 8:13 AM, Baumann, Kevin [EMAIL PROTECTED] wrote: All, Is there a way to limit bandwidth? I have a master server that is down and I want to backup a unix client over the WAN. But, I would like to limit that to 2 MB/sec. Thanks in advance. ___ 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] Master Server number of copies - unique setting for just one client?
Scott, That's a global parameter. -Tim On Thu, Aug 28, 2008 at 10:14 AM, Scott Jacobson [EMAIL PROTECTED]wrote: The default setting for the number copies is 2. Can a setting of say 3 be configured for just one client? I don't want to over complicate the explanation but I have a client that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ 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] What happened to NO_STANDALONE_UNLOAD / ltid -nsu?
You are looking for the nbemmcmd: /usr/openv/netbackup/bin/admincmd/nbemmcmd nbemmcmd -listsettings -machinename NAME nbemmcmd -changesetting -DO_NOT_EJECT_STANDALONE yes -machinename NAME That should get it for you. -Tim On Fri, Aug 15, 2008 at 3:23 PM, Rosenkoetter, Gabriel [EMAIL PROTECTED] wrote: http://seer.support.veritas.com/docs/193080.htm certainly doesn't mention anything later than NetBackup 4.5 FP2... and neither method listed there works under 6.5.2. I don't think I've ever really cared before, but now that I'm playing with LTO-4 drive encryption on a standalone drive it's REALLY infuriating to have to go push the tape in every time a label, write to, or read from a tape. (I guess I might care in a DR test too, come to think of it.) Is it still possible to do this through some other knob or switch somewhere? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 ___ 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] What happened to NO_STANDALONE_UNLOAD / ltid -nsu?
Keep in mind that most settings like this could have been in vm.conf. If they were, then during upgrade nbpushdata adds them to emm automatically. -Tim On Fri, Aug 15, 2008 at 3:42 PM, Rosenkoetter, Gabriel [EMAIL PROTECTED] wrote: Aha. nbemmcmd -changesetting -DO_NOT_EJECT_STANDALONE 1 -machinename whatever Because it makes sense for EMM to fail to get its initial settings from the touchfiles everybody's already used to, of course, and to do everything through a new management interface. Don't get me wrong, it IS nice not to have to bounce daemons in order to put these things into effect, but it sure seems like a lot of the EMM changes violate the law of least surprise... -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 -Original Message- From: Rosenkoetter, Gabriel Sent: Friday, August 15, 2008 4:24 PM To: veritas-bu@mailman.eng.auburn.edu Subject: What happened to NO_STANDALONE_UNLOAD / ltid -nsu? http://seer.support.veritas.com/docs/193080.htm certainly doesn't mention anything later than NetBackup 4.5 FP2... and neither method listed there works under 6.5.2. I don't think I've ever really cared before, but now that I'm playing with LTO-4 drive encryption on a standalone drive it's REALLY infuriating to have to go push the tape in every time a label, write to, or read from a tape. (I guess I might care in a DR test too, come to think of it.) Is it still possible to do this through some other knob or switch somewhere? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 ___ 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] ZFS issues resolved in 6.5.2
FYI, there was an e-mail sent out to those subscribed, there are some ZFS issues addressed in 6.5.2: -Veritas NetBackup Server / Enterprise Server: 6.5 and 6.5.1, Solaris 10 clients where Zeta file system (zfs) partitions are mounted For a description of the issue, complete details, and our recommendations, please visit the following reference document: http://entsupport.symantec.com/docs/303000 -Tim ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] MPT driver and SG
If you're at 6.5.2, there's really no point in applying 6.5.2A. The only incremental difference between the two is documented in TN 304269: http://seer.entsupport.symantec.com/docs/304269.htm So, if you haven't been affected by the STREAMS (AKA Incrementals as Fulls) problem documented there and are ALREADY at 6.5.2, there's not much point in applying 6.5.2A. On Mon, Jul 21, 2008 at 11:01 PM, Martin Ruslan [EMAIL PROTECTED] wrote: Hi Jon, I've looked to the NBU6.5 HCL, and the SL24 supported either with FC, or SCSI. Since you already upgraded to 6.5.2, and Symantec already released the 6.5.2a, why don't you try to go with it. you can check here: http://seer.entsupport.symantec.com/docs/305652.htm there's some robot issue fixed on this release version. mTz On Mon, Jul 21, 2008 at 11:13 AM, Jon Bousselot [EMAIL PROTECTED] wrote: On the Sparc Solaris 10 system: SL500 library, two LTO4 drives - fiber. L100 library, two LTO3 drives - all scsi. The L100 is currently connected to a Solaris 9 system, and is working fine, but I need to move it to the Solaris 10 T2000 system. On the x86 system: SL24, one LTO4 drive, cannot attach to the robot after 6.5.2 patch, and had a lot of problems finding the robot at 6.5. -Jon - Original Message From: Martin Ruslan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: VERITAS-BU@mailman.eng.auburn.edu Sent: Sunday, July 20, 2008 8:24:08 PM Subject: Re: [Veritas-bu] MPT driver and SG Hi Jon.. How many tape library do you have? and can you give the tape library brand and type? looks like you need to do the device mappings. And btw, if you only had one tape library, the robot only attached to one master/media server. unless you partitioned it regards, mTz On Sat, Jul 19, 2008 at 10:47 AM, Jon Bousselot [EMAIL PROTECTED] wrote: http://www.auscert.org.au/render.html?it=9490 Has anyone encountered this bug and the documented workaround did not fix the problem? I've encountered a variety of problems that I can relate to this. 1. Sun Sparc system with fiber attached tape/robot, had the bad patches but not the workaround, and sg sees the tapes and robot just fine. The sg driver worked fine at version 6.5 and 6.5.2. 2. Same Sun Sparc system with scsi card added, workaround patches applied, and sg cannot see the robot on the scsi bus, only the drives. The robot and drives on the fiber card are still there and working just fine. 3. Sun x86 system with fiber attached tape, did not have the workaround, sg sees only the tape. After the workaround, sg sees the tape and robot and I could setup the devices. After 6.5.2 patch, sg does not see the robot any more. I've done the sg.build, and run sgscan a dozen times. Reconfigure boots, devfsadm, cfgadm, luxadm probe... it seems Solaris can see all the devices down either type of controller, but SG refuses to bind to the robot. On the Sparc system, I'm moving the library off of a working 6.5.2 Solaris 9 media server that is being decommissioned, so I know the library and drives are good. The x86 system is a new install. -Jon ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Allocation Failure when doing bpimmedia NBU 5.0MP6
Check out this TechNote: http://seer.support.veritas.com/docs/273884.htm There's an internal timeout which gets hit when querying a large catalog. -Tim On Wed, Jul 16, 2008 at 2:30 PM, Jim VandeVegt [EMAIL PROTECTED] wrote: I am getting an allocation failure (only error reported) when attempting to run bpimmedia against individual media IDs. Sometimes the command reports some image data before dumping the error, sometimes it does not. It usually takes several minutes before the error dumps out. My environment is not particularly big. Images database is 16 GB as reported by du. Usually run about a 1000 jobs per night. Solaris 8 master (Sun V240) running NBU 5.0MP6. I am executing the command on the server as root. I have also received similar results when querying the same media from the Catalog section of the GUI. I did a Google search for this and all I found was a reference to a bug fixed in V3.2. The bug was bprd would reach 256MB in size during a long restore and dump the error. (Sun patch 108261) I tried right after a complete reboot ... no help. Does not seem to affect all media, which is strange. Would something under the guise of ulimit be at work here? Or maybe /etc/system entries? Some outputs: # ulimit -Ha core file size (blocks) unlimited data seg size (kbytes) unlimited file size (blocks) unlimited open files 4096 pipe size (512 bytes) 10 stack size (kbytes) unlimited cpu time (seconds) unlimited max user processes 4091 virtual memory (kbytes) unlimited # ulimit -Sa core file size (blocks) unlimited data seg size (kbytes) unlimited file size (blocks) unlimited open files 512 pipe size (512 bytes) 10 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 4091 virtual memory (kbytes) unlimited -- Jim VandeVegt VandeVegt @t yahoo.com, Jim.VandeVegt @t PhysiciansMutual.com Eliminate the IRS and put the fair consumption tax in place. Visit http://www.fairtax.org/ http://www.fairtax.org/ Quid quid latine dictum sit, altum videtur. ___ 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] Image compression algorithm or enthusiastic operator?
That's certainly not the normal NetBackup format. Normally files are in the ctime directories, have names just like the .f file and end in .f.Z. NetBackup uses the native compress on UNIX. It'd be interesting to see what's in the files you list below. I'd also be curious if a bpdbm -consistency check would report them as errors. FWIW, it looks like some of your STREAMS files have been mucked with too. Notice the old dates on some of those files. I'm pretty sure you only need the STREAMS and STREAMS.lck files. Be careful changing those, if you remove them, your next incremental may become a full (So only clean them up when your next backup is scheduled to be a full). -Tim On Wed, Jul 16, 2008 at 11:42 AM, [EMAIL PROTECTED] wrote: I found this in the netbackup/db/images/client directory for a client of mine. Did I get an enthusiastic operator compressing stuff or is this part of the catalog compression algorithm (the XXX.tar.gz) files on top? The directory is far too big for the number of files I think we're tracking here. ls -l total 16367638 -rw-r--r-- 1 root other 44146 Dec 31 2007 102.tar.gz -rw-r--r-- 1 root other 55176 Dec 31 2007 103.tar.gz -rw-r--r-- 1 root other 47607 Dec 31 2007 104.tar.gz -rw-r--r-- 1 root other 61527 Dec 31 2007 105.tar.gz -rw-r--r-- 1 root other 35792 Dec 31 2007 106.tar.gz -rw-r--r-- 1 root other1543518284 Dec 31 2007 107.tar.gz -rw-r--r-- 1 root other1446773287 Dec 31 2007 108.tar.gz -rw-r--r-- 1 root other2962613248 Dec 31 2007 109.5.tar.gz -rw-r--r-- 1 root other2426976416 Dec 31 2007 109.9.tar.gz drw-r-xr-x 3 root other 2048 Oct 8 2007 11 drw-r-xr-x 3 root other 4096 Oct 8 2007 110100 snip drw-r-xr-x 2 root root1024 Oct 8 2007 112300 drw-r-xr-x 2 root other 1024 Oct 8 2007 112400 -rw--- 1 root other309 Jul 11 07:22 STREAMS -rw-rw-rw- 1 root other 16 Jul 27 2006 STREAMS.ALT_NAME.26477 -rw--- 1 root other 4253 Jun 2 2006 STREAMS.alt -rw--- 1 root other 15 Jul 11 07:22 STREAMS.lck -rw--- 1 root other 17 Nov 16 2005 STREAMS.wl.lck -M ___ 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] Unable to determine robot type
The key is that the robot needs to report which drive number has which serial number. Are you seeing this in the scan output (along with the drives themselves showing a matching serial)? If not, then you'll either need to remedy that issue or manually figure out which drive equates to which robot drive number. I'll assume you are running the wizard for ALL the hosts at once? Such that the robot control host is being scanned along with non-robot control hosts. Or you need to configure the robot control host and then add the others later. HTH -Tim On Thu, Jul 3, 2008 at 5:21 AM, Esson, Paul [EMAIL PROTECTED] wrote: Folks, Anybody out there using EMC Disk Library as a VTL and has experienced similar? I have just installed NetBackup 6.5.2 on Solaris 10 with 2 x EMC DL 4000s and 2 x Quantum Scalar i2000s. There are 4 x Solaris 10 Media Servers that are configured to see dedicated drives from the DLs and shared drives from the i2000s. The sgscan and scan output look okay but when I attempt device configuration through the NetBackup wizard the DL based drives appear with the following limitations: Unable to determine robot type Drive is standalone or in unknown robot Robot drive number is unknown The DLs have inquiry strings EMC Disk Library 2.0 which apparently is a Symantec requirement. Regards, Paul Esson *Redstor Limited* Direct: +44 (0) 1224 595381 Mobile: +44 (0) 7766 906514 E-Mail: [EMAIL PROTECTED] Web:www.redstor.com REDSTOR LIMITED Torridon House 73-75 Regent Quay Aberdeen UK AB11 5AR Disclaimer: The information included in this e-mail is of a confidential nature and is intended only for the addressee. If you are not the intended addressee, any disclosure, copying or distribution by you is prohibited and may be unlawful. Disclosure to any party other than the addressee, whether inadvertent or otherwise is not intended to waive privilege or confidentiality. ___ 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] Netbackup 5 on solaris10
Just install it, then patch. You'll be fine. That's your only option. -Tim On Thu, Jul 3, 2008 at 7:19 AM, Dave Markham [EMAIL PROTECTED] wrote: Guys i have a bit of an issue im trying to work around. We have some NBU upgrades to do from NBU5.0MP7 to NBU6.0MP4 plus some NBU5.0MP2 to NBU6.0MP4. Please no replies about why 6 Mp4 and not 6.5 or a higher MP version of 6 its what is signed off on the customer account and i cannot change that no matter how much i have tried. We have a test bed to do these upgrades on first before they are signed off to be done on live systems. Again perhaps overkill but its out of my control. More blame culture dodging. Issue is we have a Solaris10 box which i need to install netbackup 5.0MP7 onto. From what i read NBU5 is only compatible with Sol10 at MP4 but how do i install v5.0 base to put the mp4 patch on? Reason i need to do an install and not just a client push is the Sol10 box needs to be a Media server at 5.0MP7 prior to being upgraded. I'm guessing the 5.0 install script doesnt know about sol10 and services etc so cannot install correctly. Anyone any ideas? Cheers ___ 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] Restore from Data Domain using 3 selections
That's certainly one way to do it, but Jeff's original problem is related to the difference in how bptm and bpdm perform restore operations (actually it happens when the restore is kicked off while the images are examined in the catalog). If a restore is initiated for tape, the restore jobs are mpx restore jobs and if everything falls into place, all the streams begin restoring at the same time (from one or many tapes). However, when disk is found, the mpx restore is turned off and therefore everything is restored sequentially... even if it WAS multiple streams that your underlying disk technology can support (ie, don't have multiple reads/writes from/to the same physical disk). I'd suggest an enhancement request to your favorite avenue (support, SE, etc). -Tim On Mon, Jun 9, 2008 at 3:27 PM, Mark Glazerman [EMAIL PROTECTED] wrote: Jeff, The way that Data Domain restores is down to how you submit the restore jobs from the backup and restore console in NBU. If you want to restore root, usr and var you could click on root, uncheck the mountpoints you don't want to restore and kick off the restore. That will restore everything in 1 job. If you drill down and only select the individual mountpoints you want and kick each one off as an individual restore, Data Domain will send data to multiple restore jobs. As an FYI we found that we were able to restore our biggest database (Exchange) quicker in a single stream than in multiple streams. A single stream allowed us to restore approximately 100GB per hour. *Mark Glazerman* Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Jeff Lightner *Sent:* Monday, June 09, 2008 2:34 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Restore from Data Domain using 3 selections For the second time I've noticed that a backup we created that had 3 simultaneous selections going to Data Domain (as it previously did to tape) on restore is only doing a single selection. When we did this to tape it would restore 3 different selections simultaneously just as it had backed them up. Is there something I need to tell bprestore to force it to do this when the 3 selections were all going to the same location like a Data Domain? If not would starting 3 separate restores of only the files in the specific selections cause it to run concurrently? -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ 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] NDMP Incremental backup
I sure know that my pst file is updated a lot every day. I'm sure that is the cause of your issue. -tim On Jun 3, 2008, at 5:35 PM, PGerard netbackup- [EMAIL PROTECTED] wrote: No...all of the other policies for the other file systems are built the exact same way and they are fine. This particular one has outlook PST files in it, which are likely quite large, and I doubt they are ALL changing, so I suspect the time stamp gets modified when the users open it up with outlook...i guess it's possible they have some automatic archiving too and the minute even a single new email message makes it into the PST it is deemed as having changed and will get picked up by an incremental. We are running differentials all the time with only Monthly backupswe have 30TB of Celerra and only 6 tape drives to back it all up, so doing it every week would be extremely tedious. I thought maybe the ctime thing was causing this but the more I think about it, the more I think the files are just being modified on a daily basis. Thanks +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ 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] (no subject)
Michael, The unable to lock media message has to do with bptm selecting media. Without the log, my guess is that you'll see bptm is attempting to obtain a piece of media for a backup. One part of that process is going through it's local mediaDB to see if it fan find a match for what it needs (correct volume pool, retention, etc). If a particular tape is in use, then you'll see the unable to lock media message. I don't think this is related to the problem you originally posted. BTW, what patch level? -Tim On Tue, May 6, 2008 at 8:47 AM, [EMAIL PROTECTED] wrote: Folks, Not sure whether anyone can help or give a workaround solution? We're having issues in NBU 5.1 environment with HP-UX media servers and jobs not going to end writing. This is a fairly irregular occurrence but always tends to occur with logical logs in the middle of the night (oh joy!). This isn't a scheduler issue as everything else chugs along nicely. We're using ACSLS 7.1.0. From bptm logs I can see lots of occurences of 12:08:30.310 [27067] 2 db_lock_media: unable to lock media at offset 14' . Which could mean the media is in use by another host, but I know it isn't. My guess is theres a communication error between Media server and ACSLS. So my question is, what can I do to kickstart this? Sometimes I can go into the Activity Monitor and end job, and it miraculously finishes. Other times when on-bar processes go, then it's a Master server restart. Regards Mike K * This message and any attachments (the message) are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or falsified. If you are not the intended addressee of this message, please cancel it immediately and inform the sender. ___ 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] Upgrade of windows clients
Windows clients with what kind of master? Any Windows media servers? -Tim ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Weird error 54/41
I would not suggest increasing the CLIENT_CONNECT_TIMEOUT. Think about it, how long *should* it take to establish a connection between hosts? Essentially, this is equivalent to how long does it take to establish a telnet session between two hosts? If it takes you two hours, there's something wrong. I can see that if you are bouncing your connection over multiple satelite connections, maybe you'd need to be worried about it, but in general, NetBackup's default of 300 seconds is MORE than generous. As for your status 54/41, what changed 3 weeks ago? Can you establish connections between the client/servers involved? Ie, can you telnet between them all, etc? Is name resolution still working? (Run bpclntcmd on each host with the peer hostname and ip). -Tim On 2/12/08, Michael Graff Andersen [EMAIL PROTECTED] wrote: Hi Marianne I have had luck with raising the CLIENT_CONNECT_TIMEOUT CLIENT_READ_TIMEOUT settings with this kind of errors before Can see you already have raised CLIENT_READ_TIMEOUT, will suggest that you raise CLIENT_CONNECT_TIMEOUT to the same Regards Michael 2008/2/12, Marianne Van Den Berg [EMAIL PROTECTED]: Hi Simon I appreciate every bit of advice at this point in time. I have used NOSM in the past where the media server is backing up itself. In this case the client (Linux) is backed up over the network to a media server (Solaris). Kind regards *Marianne * -- *From:* WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] *Sent:* 12 February 2008 13:05 *To:* Marianne Van Den Berg; veritas-bu@mailman.eng.auburn.edu *Subject:* RE: [Veritas-bu] Weird error 54/41 Hi Marianne Not sure if this helps... http://seer.support.veritas.com/docs/186016.htm Pretty sure the creation of a NOSHM file helped. S. -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Marianne Van Den Berg *Sent:* Tuesday, February 12, 2008 10:47 AM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Weird error 54/41 Hi all We have Oracle rman backups failing with Network Connect Timeout. Filesystem backups are working fine. Weird thing is we can see in Job details 'Connecting, Connected': 02/12/2008 10:32:29 - *connecting* 02/12/2008 10:32:40 - *connected*; connect time: 0:00:00 02/12/2008 10:32:40 - begin writing 02/12/2008 11:32:41 - end writing; write time: 1:00:01 *network connection timed out* (41) Handshaking in bpcd on client and bpbrm on media server is successful. I have now increased Client Read Timeout to 7200. Backup 'Active' for 1 hr 54 minutes already – still not a single byte written…. Backups on this client have been successful till about 3 weeks ago. NetBackup 6.0 MP4 on server and client. RMAN backups on the client to local disk start writing almost immediately. RMAN log on client : ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: Communication with the server has not been initiated or the server status has not been retrieved from the server. PLEASE HELP!! Regards *Marianne * This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VXSS Feature
Abhishek, NetBackup ultimately relies upon system calls like gethostbyname() and gethostbyaddr(). So if those system level calls work, then NetBackup shouldn't have a problem either. I'm not sure what you mean by nslookup is deactivated, but I'll assume you mean it's not working because you don't have a DNS server (since that's what nslookup uses). You can use the NetBackup provided bpclntcmd (/usr/openv/netbackup/bin/bpclntcmd) to check that name resolution is working: bpclntcmd: -sv bpclntcmd: -pn bpclntcmd: -self bpclntcmd: -hn hostname bpclntcmd: -server NBU master bpclntcmd: -ip ipaddress bpclntcmd: -gethostname bpclntcmd: -is_local_host hostname bpclntcmd: -check_vxss bpclntcmd: -check_vxss_with_host hostname bpclntcmd: -get_pbx_port [hostname] bpclntcmd: -get_remote_host_version hostname These are all documented in the commands manual, but I'd start with things like -hn hostname and -ip ipaddress to see if name resolution is working for NetBackup. HTH -Tim On 2/11/08, Abhishek Dhingra1 [EMAIL PROTECTED] wrote: Hi Tim, If my /etc/hosts file is resolving the hosts, but nslookup is deactivated and is not working , is it possible to configure .i am running on AIX , and i have checked the /etc/netsvc.conf file, it is showing the file first Abhishek Dhingra IBM Global Services, Delhi, Email : [EMAIL PROTECTED] Mobile : +91-9818675370 *Tim Hoke [EMAIL PROTECTED]* 09/02/08 08:10 PM To Abhishek Dhingra1/India/[EMAIL PROTECTED] cc veritas-bu@mailman.eng.auburn.edu Subject Re: [Veritas-bu] VXSS Feature NetBackup (and therfore VxSS) rely on host configure name services to be accurate. As long as your nsswitch.conf has hosts listed and hosts are correct, NetBackup will function fine. HTH -Tim ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VXSS Feature
NetBackup (and therfore VxSS) rely on host configure name services to be accurate. As long as your nsswitch.conf has hosts listed and hosts are correct, NetBackup will function fine. HTH -Tim ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Status 174 in NB.
Here's a doc from Veritas/Symantec: http://support.veritas.com/docs/266276 Looks like 4.5 FP6 will help out in this case: The solution to this problem is to install a supported version of NetBackup on the clients. Currently 4.5 FP6 is the minimum supported version for these operating systems. HTH -Tim On 1/29/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am taking a backup of Red Hat Linux 2.4 using NB 4.5. My backup ends with the status 174. The logs say [from client es4:Incorrectly built binary which accesses error or h_errorno directly.Need to be fixed] I checked on client for binaries (as sugggested by status code solution). When I run /usr/openv/netbackup/bin/bpcd on client I got the same error message *:* Incorrectly built binary which accesses error or h_errorno directly.Need to be fixed. I reinstalled the NB client software and again tried to take backup,but getting the same error. What should I do ??? Thanks Regards, Vinayak D.Vaijwade *P** Please do not print this email unless it is absolutely necessary. Spread environmental awareness.* The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com ___ 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] Anyone know how to remove a host name from GUI loginscreen?
On UNIX, for the Java GUI, you'll need to look in ~/.java/.userPrefs/vrts/nbe/NBELoginLists/vrts-nbe-AdminConsole/prefs.xml -Tim On 1/25/08, Johnson, Eric [EMAIL PROTECTED] wrote: On Windows, this info is in the registry: HKEY_CURRENT_USER\Software\JavaSoft\Prefs\vrts\nbe\/N/B/E/Login/Lists\vrts-nbe-/Admin/Console (yes, they actually used forward slashes in the names..) There is a key called host/List that contains the list. Eric -- *From:* Bobby Williams [mailto:[EMAIL PROTECTED] *Sent:* Friday, January 25, 2008 10:07 AM *To:* 'veritas-bu' *Subject:* [Veritas-bu] Anyone know how to remove a host name from GUI loginscreen? We have retired some servers and I would like the host name from showing up as an option in the Java GUI login screen. Anyone know where that info is stored? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 ___ 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] Getting a list of files from a failed backup
Jeff, You won't be able to get a file list in the method you have attempted. Once the backup fails, NBU removes the information from the catalog. A couple of items for you... 1. You may want to enable the checkpoint restart feature (at the policy) so that you could resume the backup from the point at which it failed. 2. There is a way to run bpbkar on the client to see if it's a problem just reading the files. /usr/openv/netbackup/bin/bpbkar -nocont path /dev/null 2output file eg: bpbkar -nocont / /dev/null 2/tmp/file_list.txt Then examine the file_list.txt to see the file names. 3. There's also a way to enable the logging of files at the client when the backup occurs. a. Make sure you have the /usr/openv/netbackup/logs/bpbkar directory in place. b. touch /usr/openv/netbackup/bpbkar_path_tr c. perform backup d. examine the log.mmddyy file created in the above dir CAUTION... if there are a large number of files (as you indicate i likely), it's possible that this log file or output file could grow REALLY large... If that's a problem, just run the bpbkar command and don't redirect stderr (omit the 2file) Point 2 and 3 come from my notes and I don't readily find references on the Symantec web-site, but I'm sure they are there. HTH -Tim On 1/4/08, Jeff Cleverley [EMAIL PROTECTED] wrote: Greetings, I have a file system that has started to fail full backups on a regular basis. The incremental backups run fine. This file system is on a hpux 11.11 server, There is only 228 gig of used data, but it does have ~5.5m inodes in use. The backup fails with a status 41. This server has other file systems on it with more used inodes and more used space, and they don't have this problem. I've run the backup at various times when I know the network and file system load is low, but it doesn't change. The current backup environment is 5.1 mp2. It was supposed to be retired by now which is why it hasn't been upgraded. The reason I want to see what files it is backing up before it fails is that all of the backups seem to backup just over 195 gig before they fail. The file counts vary quite a bit. I'm expecting that I may have a very poorly laid out structure with hundreds of thousands of files in one directory that is causing this problem. This may also be caused by some timeout if it does hit this, but I haven't been able to find it in any of the log files. I was able to recovery an image from the tape listing by running bpmedialist -mcontents -m bk7159. That returns image massey_1199305335. I've tried doing the following bpflist command and get the no entity found bpflist -backupid massey_1199305335 -d 01/02/2008 -e 01/03/2008 -client massey I also tried running the bpflist this way and get no entity found again. This format works when I give it a different client name and pattern, so I know I have the syntax correct. bpflist -client massey -st FULL -d 01/02/2008 00:00:00 -rl 1 -pattern /mnt/wizard I'm guessing some of this isn't working because the backup did not complete and there isn't a valid image for it. Any help you can provide that will show me where the backup is failing would be greatly appreciated. Thanks, Jeff -- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611 [EMAIL PROTECTED] ___ 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] New tape drives not appearing in /dev/rmt.
My guess is that you need to add the WWN to the st.conf... Something like this: name=st class=scsi target=c0tw500308c00189780al1; Do that for each drive and then reload the st driver... modinfo -i |grep st modunload -i (number of st driver) devfsadm -i st That ought to clear it up. One other possibility is to run the /usr/openv/volmgr/bin/sg.build command and have it build the sg.conf entries. Then, just change the 'name=sg' to be name=st and put that in st.conf. -Tim On 12/24/07, Vines, Peter (psv2b) [EMAIL PROTECTED] wrote: Adding the entry to st.conf followed by a boot -r did NOT fix my problem. The missing /dev/rmt entries are still missing. I've opened another issue with SUN. The original six drvies in the L700 are still there and usable. The new four drives in the Scalar i2000 do not exist in /dev/rmt, yet are shown in cfgadm. -Original Message- From: [EMAIL PROTECTED] on behalf of Peter Vines Sent: Wed 12/12/2007 7:13 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu _http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu_ -- next part -- An HTML attachment was scrubbed... URL: _http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071210/637ebd20/attachment-0001.htm_ -- - Peter Vines : [EMAIL PROTECTED] : (434) 924-4644 ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Tapes not staying in Volume pools (NBU6.5)
You may want to investigate the RETURN_UNASSIGNED_MEDIA_TO_SCRATCH_POOL parameter (vm.conf in pre-6.x and set via nbemmcmd on 6.x). It's a yes/no thing and will NOT return media to scratch if that's not where they came from. But this (along with having or not having a scratch pool) is an all or nothing proposition (it can't be set for a particular pool or set of tapes or fill in the blank for you you'd like to slice and dice). -Tim On 12/19/07, Paul Keating [EMAIL PROTECTED] wrote: if a tape is assigned to a pool from scratch, then when the backup images on that tape expire, the tape goes back to scratch. if you do not have a scratch pool defined, this will not happen, if I understand correctly. Paul -- -Original Message- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Keating, John *Sent:* December 19, 2007 12:16 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Tapes not staying in Volume pools (NBU6.5) Hello all; I'm currently having an issue with tapes that aren't staying in their assigned volume pools. We have 4 weekly pools with 14 tapes in each. Each week it seems I have re-assign tapes to their pools from the scratch pool. Does anyone know of a way to stop or lock them into the pools that they're assigned to? Thanks for the help. John La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ 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] How to change the retention level of a tape (not the images)?
Two things... 1. NBU will not reduce the retention period of a media. That is to say that the expiration date of a media (data portion, not the physical useful life span) will never be made to be a date which is closer in time to today. 2. NBU will not change the retention level. That is to say in your case, there's no way to change the retention level of the media from 12 to 4 (regardless of if the images expire sooner rather than later now). So, I think you'll be left with poking into the DB... But I wouldn't recommend it in case something goes awry. HTH -Tim On Nov 29, 2007, at 5:30 PM, [EMAIL PROTECTED] wrote: Hi all, In our NBU 6.0 environment, we have a number of tapes (about 60) that we want to change the retention level of. From retention level 12 to retention level 4. I've already written a solid script (on Solaris) that recalculates the expiry (via retention level) for each of the images on each tape, and this is working fine. The tape attributes themselves though still have the original retention level (level 12). I'd like to adjust the retention level of each tape to match the images on it (from 12 to 4), so that tapes which aren't yet full can receive further backup data. Was expecting something like vmchange would work, but no luck there. Hoping I don't have to manipulate catalog data directly. (I have a fairly strong SQL background, but still...) Regards and best wishes, Justin Clift ___ 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] Netbackup Policy Schedule
You could also try /usr/openv/netbackup/bin/admincmd/bpplsched policy_name [-L|-l|-U] -Tim On 11/27/07, shaharul ismail [EMAIL PROTECTED] wrote: hi kg morten, u can try #/usr/openv/netbackup/bin/admincmd/bppllist -allpolicies -L -U regards, shaharul On Nov 28, 2007 11:43 AM, kg_morten [EMAIL PROTECTED] wrote: Hi, using bplist, I got list of all policies configures but I don't know the schedule and backup window for each policy. Kindly help on how to get the schedule and backup windows for each policy. Thanks -Kamarul +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Need some help
You know, I think there's some nbemmcmd -renamehost or something like that. Seems to me that will get things squared away. Devices, media and all. -Tim On 10/23/07, Tharp, Trey [EMAIL PROTECTED] wrote: Here's what you need to do to resolve this from the customer side. On the master that you are running the 'bpmedia -movedb' command create a host entry for the old_server name and put the IP address of that as the master. What you need to do is have bpmedia able to talk to a NBU host, it doesn't actually do anything but want to verify connectivity. At that point the 'bpmedia -movedb' should work and then once all the media is no longer assigned to that server you can run 'nbemmcmd -deletehost' and get rid of it. The alternative is to have Support write a sql script to update the database references for the old media server, but they aren't always willing to do this for all customers I don't think. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cruice, Daniel (US - Glen Mills) Sent: Wednesday, October 17, 2007 2:26 PM To: Justin Piszcz Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Need some help Well...my issue is not resolved, I have gone to the extent of building a new box with the same old media server name, and that STILL did not do the trick. Symantec is recommending I install MP5 on the Master node. As they have seen this issue with other customers and MP5 seemed to have done the trick. So now I turn to my fella NBU friends are there any gotcha's or issues with MP5 and does anyone know how long it has been out? Thanks Dan -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, October 15, 2007 3:20 PM To: Cruice, Daniel (US - Glen Mills) Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Need some help That sounds right, do a test restore to make sure it works! Justin. On Mon, 15 Oct 2007, Cruice, Daniel (US - Glen Mills) wrote: Old one back in is not an option. Where do I put the Force_Restore_media_Server = OLD_Retiree new_server. Remember...Master server is a W2K3 box. If it goes in via the GUI of Host Properties of the Master...General Server...Media host override, then I did already enter them. Thanks Dan -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: Monday, October 15, 2007 3:04 PM To: Cruice, Daniel (US - Glen Mills) Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Need some help Hm.. Put the old one back and do it properly OR.. Use: (workaround) FORCE_RESTORE_MEDIA_SERVER = old_retiree new_server Hmm, there are probably more options but those are the ones that immediately come to mind. On Mon, 15 Oct 2007, Cruice, Daniel (US - Glen Mills) wrote: I rebuilt two media servers and renamed one. And no like a dope I did not following the retiring the media server whitepaper that Veritas so gracefully wrote. So now I have an issue. My entire Master / media servers are Windows 2003 6.0 MP4. The issue I am having is getting all the media changed to the new media servers. I've tried the: Bpmedia -movedb -ev media_ID -oldserver old_server newserver new_server command and it seems to run fine, but when I do a bpmedialist the media is still assigned to the old media server name. Anyone have an ideas? I've gone as far as changing the display name on the new media server to read the old server name, modified my host files so the old name points to the new server's IP address and simply can not get this figured out. The caveat is I have to retain all the images on all these tapes. UG Dan Cruice This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. ___ 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 maillist -
Re: [Veritas-bu] sso question
This is a perfectly good configuration. You've just uncovered a limitation of using robtest where the robotic control host can't see the drives. In an L700, I'd be surprised if you actually needed to issue the unload command (lots of libraries can now accomplish the unload automagically while doing a move). Did you try a move without unload? If that doesn't work, then you've already found your appropriate solution. HTH -Tim On 10/9/07, Dave Markham [EMAIL PROTECTED] wrote: guys i have master server running sol8 connected to L700. L700 has 7 drives in it. Master can see 6 of them through fiber Med1 can see first 3 drives shared Med2 can see first 3 drives shared Med3 just added has access to drives 5,6,7 and can see them fine. I have just loaded a tape on the master server ( robot control ) and put a taper into drive 7. When i came to do an unload d7 so i could move the tape back (m d7 s6) it wouldn't do it. I then realized thats because it does unloads on rmt paths and i haven't added drive 7 to the master server. Didnt add for 2 reasons. 1. its recommended to have only 3 drives per 2gb HBA ( which is why it has 6 drives in total ). Plus if i added drive 7 i would need another shared license i guess. Question:- Is there something wrong with my setup then. Should the master have device paths set up for every drive in the robot. I know it can put tapes in but it cant take them out. What i was able to do was a mt -f /dev/rmt/2 offline from Med3 and then moved it using robtest from the master. Cheers ___ 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] Change retention in all tapes in a policy
You're also just changing a reference in the imageDB. Once your image/tape cleanup runs, the images will be removed and the tapes will be moved to scratch if they are now empty and actually came from scratch. HTH -Tim On 10/1/07, Bobby Williams [EMAIL PROTECTED] wrote: You are changing the retention based on the policy. You may have backups from other policies on the tape with the 2 year retention. You may also want to ensure that the tapes came from the scratch pool. They may be showing as not assigned in a pool other than scratch. Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of osonder Sent: Monday, October 01, 2007 8:37 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Change retention in all tapes in a policy Hello I have a policy with name Users. I now want to change retention to all tapes in this policy from 2, to 1 year. (I have a custom retention for 2 years as retention level 6) I used the command: bpexpdate -policy Users -recalculate -ret 8 Then I get a warning: Are you SURE you want to recalculate expiration dates on all images that meet the following criteria: policy Users retention will be changed to 8(1 year) Continue?(y/n) I answers Yes, and the system seems to process for some minutes. After this I check if this have moved tapes to Scratch, but no. Beacuse this should have realeased a lot of tapes, and moved it to scratch pool. Is it something I missing here? Do I have to manually change retention on every tape? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backup exit notify
I'm not sure my previous message made it through. To avoid an 'su', try the following: In most cases, you can change the 'mail -s...' command to be 'mailx -r reply-to-address -s...' and you'll now get an e-mail which looks like it came from a non-root user. From 'man mailx': -r address Use address as the return address when invoking the delivery program. All tilde commands are disabled. This option and its argument is passed to the delivery program. HTH -Tim On 9/28/07, Clooney, David [EMAIL PROTECTED] wrote: Thanks Carl Yep I understand all this, and the below is when incorporated into one of the exit notify scripts, however I am not utiliding any of these. If you turn on the SERVER to send mail on all clients, somewhere in the NBU binaries mails are being sent. Have just learned that from the library /opt/openv/lib/libVbp.so the *mail *program is being used so will endeavour to check the servers mail.cr to possibly masquerade.** * * *Dave* -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *Sent:* 28 September 2007 16:26 *To:* Clooney, David *Cc:* veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] *Subject:* RE: [Veritas-bu] Backup exit notify Here is what I did. I added the sendmail call in my script and have the script su to the allowed user before calling sendmail. Something like this: su $EMAILUSER -c cat $RPT_DESTN_DIR/some_report.txt|/usr/lib/sendmail -f $SENDER_EMAIL -t $RECIPIENT_LIST Notice that sendmail had the -f parameter, this changed the from and $SENDER_EMAIL could be your [EMAIL PROTECTED] $EMAILUSER is the non-root user that has a valid account on the system. $RECIPIENT_LIST is the e-mail addresses to send the message to. Hope this helps = Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] *Clooney, David [EMAIL PROTECTED]* 09/28/2007 10:52 AM To [EMAIL PROTECTED] cc veritas-bu@mailman.eng.auburn.edu , [EMAIL PROTECTED] Subject RE: [Veritas-bu] Backup exit notify Thanks everyone Just did a bit of digging around as I am quite aware of the exit notify scripts and have now totally bypassed them i.e I have removed all notify scripts from the bin directory. Settings on the CLIENT USEMAIL = [EMAIL PROTECTED] SERVER_SENDS_MAIL = YES Upon the completion of a backup I still get a confirmation email from [EMAIL PROTECTED] . I am convinced this is incorporated into a binary somewhere and as NBU runs as root when the mail is sent it picks up the user, this I need to change somehow Am I going mad ? Dave -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] * Sent:* 28 September 2007 14:41* To:* Clooney, David* Cc:* veritas-bu@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject:* Re: [Veritas-bu] Backup exit notify We set up a special account that is allowed to send e-mail from the server being backed up, and su-ed to that user before calling sendmail. = Carl Stehman IT Distributed Services Team Pepco Holdings, Inc. 202-331-6619 Pager 301-765-2703 [EMAIL PROTECTED] *Clooney, David [EMAIL PROTECTED]* Sent by: [EMAIL PROTECTED] 09/28/2007 04:28 AM To veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] Backup exit notify All Solaris 8 Does anyone know how to change the senders address when backup notify is executed on the master server? i.e. at the moment we get [EMAIL PROTECTED] Need to change it to adhere to policy Thanks Dave -- * 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. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This Email message and any attachment may contain information that is
Re: [Veritas-bu] Backup exit notify
In most cases, you can change the 'mail -s...' command to be 'mailx -r reply-to-address -s...' and you'll now get an e-mail which looks like it came from a non-root user. From 'man mailx': -r address Use address as the return address when invoking the delivery program. All tilde commands are disabled. This option and its argument is passed to the delivery program. HTH -Tim On 9/28/07, Clooney, David [EMAIL PROTECTED] wrote: All Solaris 8 Does anyone know how to change the senders address when backup notify is executed on the master server? i.e. at the moment we get [EMAIL PROTECTED] Need to change it to adhere to policy Thanks Dave -- *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. -- ___ 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] Netbackup upgrade 6 or 6.5
Hmmm... Solaris 8, 9 and 10 all appear to be supported on 6.x as Client OR Server according to this link: http://seer.entsupport.symantec.com/docs/278064.htm As for continued support, Symantec supports one major revision back. So, currently with 6.x (6.0 and 6.5), 5.x is also supported. There's an updated support statement which you can find here: http://seer.entsupport.symantec.com/docs/290017.htm I couldn't put my finger on anything that talked about 6.0/6.5 end of support life, but would expect such a statement after the next major release. -Tim On 9/20/07, Dave Markham [EMAIL PROTECTED] wrote: Thanks Im just reading through documentation and apparently Solaris 8 as a client isnt supported under NBU 6.5 so that rules that out as the infrastructure is still ruinning Sol8. Bit harsh me thinks. Thing is unless we go to 6.5 the customer will be paying lots for 6 and then in a years time when 7 comes out 6 will be no longer supported as i beleive NBU only goes 1 level back for support? Dave Justin Piszcz wrote: On Thu, 20 Sep 2007, Dave Markham wrote: Has anyone got 6.5 yet? We are running NBU 5.0 MP7 on a predomintatly solaris platform. We are due to upgrade h/w and s/w and i was wondering was it worth going for 6.0 which seems to be used quite a bit by people now, or do we go to new 6.5 ? Also we have around 20 servers including a 2 node Sun Cluster ( attached to T3 arrays ) running oracle10g. Is there anything special which can be done with 6.5 or is it just worth still doing filesystem backups direct to Tape Thanks ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu I'd recommend 6.0MP4 as I have not done any testing with 6.5 yet. Justin. ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] scsi_pkt.us_reason = 3
Vladimir, I think both of the support folks you've engaged are likely to be both correct and incorrect. You need to look specifically at the hardware layer. If Sun is your provider, then start there. Otherwise, engage your hardware support vendor. As a start to help you out, here's some information to examine... Take a look at where the scsi_pkt.us_reason messages come from: /usr/include/sys/scsi/scsi_pkt.h /* * Definitions for the pkt_reason field. */ /* * Following defines are generic. */ #define CMD_CMPLT 0 /* no transport errors- normal completion */ #define CMD_INCOMPLETE 1 /* transport stopped with not normal state */ #define CMD_DMA_DERR 2 /* dma direction error occurred */ #define CMD_TRAN_ERR 3 /* unspecified transport error */ #define CMD_RESET 4 /* Target completed hard reset sequence */ #define CMD_ABORTED 5 /* Command transport aborted on request */ #define CMD_TERMINATED 22 /* Command transport terminated on request */ #define CMD_TIMEOUT 6 /* Command timed out */ #define CMD_DATA_OVR 7 /* Data Overrun */ #define CMD_CMD_OVR 8 /* Command Overrun */ #define CMD_STS_OVR 9 /* Status Overrun */ As you can see, 3 is in fact CMD_TRAN_ERR or unspecified transport error. This is definitely something below the application (NetBackup) and bptm is just nice enough to post this message for you. So, you need to look at the lower layers... HBA, Fabric, Switches, Bridges, etc. Check out all the drivers and configs to make sure they're correct (not necessilarily the latest) and make sure there aren't any errors happening elsewhere. It might be useful to examine the bptm log for each of those PIDs to see what operation was happening. That may help narrow a particular command or device (drive) which is having a problem. Then, you can focus your efforts there. HTH -Tim On 9/14/07, Vladimir Taleiko [EMAIL PROTECTED] wrote: Hi, all I have Solaris 9 server with latest microcode/patches installed NetBackup 6.0 MP4 L180 (IBM LTO2 - 5AT0) Brocade 3800 (v3.2.1b, dual fabric) c4 fc-fabricconnectedconfigured unknown c4::500104f0006e4931,0 med-changer connectedconfigured unknown c4::5005076300615978,0 tape connectedconfigured unknown c4::500507630061605e,0 tape connectedconfigured unknown c5 fc-fabricconnectedconfigured unknown c5::5005076300615b41,0 tape connectedconfigured unknown c5::5005076300615d9b,0 tape connectedconfigured unknown c8 fc-fabricconnectedconfigured unknown c8::500507630061556a,0 tape connectedconfigured unknown c8::5005076300615aaa,0 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::5005076300615937,0 tape connectedconfigured unknown c9::5005076300615ba3,0 tape connectedconfigured unknown and the following errors: Jul 28 03:13:04 ni5nrp2 bptm[26639]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 28 07:11:25 ni5nrp2 bptm[27999]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 28 07:13:32 ni5nrp2 bptm[27983]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 28 08:42:36 ni5nrp2 bptm[15693]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 29 09:21:34 ni5nrp2 bptm[18406]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 29 10:51:12 ni5nrp2 bptm[5955]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 30 00:42:07 ni5nrp2 bptm[27613]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 30 00:52:03 ni5nrp2 bptm[27614]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 Jul 30 01:11:55 ni5nrp2 bptm[27620]: [ID 832037 daemon.error] scsi command failed, may be timeout, scsi_pkt.us_reason = 3 bptm logs doesn't show any issues. I've opened two cases in Sun and Symantec. Sun guys said There is no errors from scsi layer, call Symantec Symantec support said these errors are being received by the bptm process, and not being generated by it, please involve SUN I'm slightly confused. What is the cause of this errors? -- Vladimir ___ 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] Need help with FAILOVER_RESTORE_MEDIA_SERVERS
Justin, I think you are misinterpreting the parameter. It has nothing to do with how busy a server is... It's if the server is totally not available (offline). From the SAG: Specifies automatic failover to another NetBackup server if a server is temporarily inaccessible for a restore. The key word is inaccessible. If you need a temporary solution, look at bpmedia -movedb... you can move the server so that you can complete the restore, then move back. I though I heard at one point that this whole media ownership thing was going to go away. I just don't know when. That way, if you kick off a restore, it sounds like it would try to use the original host, else, find one that is available so I can just get the restore done... In the short term, bpmedia is your bet option. -Tim On 9/14/07, Justin Piszcz [EMAIL PROTECTED] wrote: Anyone here use FAILOVER RESTORE media servers? Justin. On Fri, 14 Sep 2007, Justin Piszcz wrote: I have a user-initiated restore in a library with 20 tape drives. More than 15 of them are free, the one it is trying to use for the restore is completely utilized (all 4 drives are in use): 09/14/2007 01:21:11 - begin Restore 09/14/2007 01:21:19 - number of images required: 1 09/14/2007 01:21:20 - media needed: C00498 09/14/2007 01:21:57 - restoring from image the_client_hostname_1189167024 09/14/2007 01:21:59 - connecting 09/14/2007 01:22:00 - connected; connect time: 0:00:00 09/14/2007 01:21:59 - requesting resource C00498 09/14/2007 01:22:00 - awaiting resource C00498. Waiting for resources. Reason: Drives are in use, Media server: media_server_2, Robot Type(Number): ACS(0), Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A FAILOVER_RESTORE_MEDIA_SERVERS is NOT WORKING. If media_server_2 is busy, it should failover to one of the other media servers with free drives! media_server_2$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl . ReqId 0 hcart3 ACS Yes C00202 C00202 Yes Yes0 1 hcart3 ACS Yes C00200 C00200 Yes Yes0 2 hcart3 ACS Yes C02392 C02392 Yes Yes0 3 hcart3 ACS Yes C00197 C00197 Yes Yes0 media_server_2$ logout media_server_3$ sudo /usr/openv/volmgr/bin/vmoprcmd -d ds DRIVE STATUS Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl . ReqId 0 hcart3 ACS Yes C00697 C00697 Yes Yes0 1 hcart3 ACS- No - 0 2 hcart3 ACS- No - 0 3 hcart3 ACS- No - 0 media_server_3$ My bp.conf file: # new config FAILOVER_RESTORE_MEDIA_SERVERS = media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_4 media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_5 media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_6 media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_7 media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 FAILOVER_RESTORE_MEDIA_SERVERS = media_server_8 media_server_1 media_server_2 media_server_3 media_server_4 media_server_5 media_server_6 media_server_7 # COMMENT: I used to use FORCE_RESTORE_MEDIA_SERVER but the problem with that is you can only force it to an alternate media server, I want to make the most use of the available capacity in the robot, how can I do this if failover restore media server does not work? Justin. ___ 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] Backing up SharePoint
According to the compatibility guide (264318), SharePoint Server 2003 is supported via the SQL server agent. See 264854 for more details. http://seer.support.veritas.com/docs/264318.htm http://seer.support.veritas.com/docs/264854.htm On 9/11/07, Leidy, Jason D [EMAIL PROTECTED] wrote: The version of MS SharePoint is 2007 Jason Leidy Con-way Enterprise Services Windows Server Group 503-450-3958 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leidy, Jason D Sent: Tuesday, September 11, 2007 7:40 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Backing up SharePoint We use NetBackup 5.1 MP6. We'd like to start backing up out SharePoint servers via NetBackup…….can this be done with an agent, similar to SQL and Exchange (I've got a call into Veritas)? Jason Leidy Con-way Enterprise Services Windows Server Group 503-450-3958 ___ 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] Media Changer Utility for Solaris
More specifically, use the appropriate *test utility and pipe the commands to it... for a tld type robot you might do the following to move slot 1 to drive 1: echo m s1 d1 | tldtest -r /dev/sg/robotic_device I'm not at my system right now, but I seem to recall that being the usage. HTH -Tim On 9/9/07, Justin Piszcz [EMAIL PROTECTED] wrote: On Sun, 9 Sep 2007, selwyn wrote: I had written a script to match locations of robotic drives with their device path for HP-UX. I used the mc utility to move a tape from one drive to the next and then used mt to find out which device path matched the physical drive path. I would like to do create a script for solaris to do the same task, but there is no mc utility native to Solaris. Can anyone point me a solaris equivalent for the HP-UX mc utility? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Why not just use robtest? ___ 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] NetBackup 6.5 VTL direct to tape
The reason this is a feature in 6.5 is the OpenStorage functionality. With OpenStorage, the hardware vendor (EMC, FalconStor, etc) will implement some way (OpenStorage API) of being a disk front end with the tape offload on the back end. So, it's not really a VTL at that point, but a disk-disk-tape solution where the tape portion is automated by the hardware vendor. Once the data is on tape, the OpenStorage functionality will allow NetBackup to know where the data is. And NetBackup won't have had to even been involved in the duplication to tape. Wish I could point to more information, but I wasn't able to find anything on OpenStorage on the Symantec website except for manual references. HTH -Tim On 8/30/07, drpaine10 [EMAIL PROTECTED] wrote: My suspicion was that they would have me line up the virtual and physical media id's. I'm not sure why this is listed as a feature in netbackup 6.5 since we could do this in any previous version. any ideas? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ 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] MP5: Cannot decompress .Z file...
As for platforms affected, it's only UNIX. Windows uses built in API calls to the native file system compression. Just call support, they ought to had it out no problem. -Tim On 8/22/07, crhea [EMAIL PROTECTED] wrote: Sorry, but the terms of support state that I cannot redistribute the code. If you reference my case number (290-841-020), Support should be able to quickly find the code they sent to me. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ 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] Netbackup 5.1 and checkpoints
Hi Mitch, The retry will use the last checkpoint. If there isn't one, it'll start from the beginning. -Tim On Feb 21, 2006, at 4:06 PM, Lien, Mitch wrote: We are using Netbackup 5.1 MP4 and have enabled checkpoints for our Standard (Unix) and Windows-based backups. The checkpoints are occurring every 30 minutes I need to know if a backup job fails during the 1st attempt (example: status 84) will the 2nd attempt (retry) continue from the 1st attempt last checkpoint or start all over? Thanks for the help. Mitch ___ 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] Unable to process request because the server resources are busy
The status 134 means there aren't enough tape drives to handle all the requests. In particular, this looks like a duplication right? If you run backups and duplications at the same time, the scheduler (pre-6.0) isn't fully aware of duplications and also, doesn't track the drive usage in a real-time fashion. Therefore, the scheduler can end up oversubscribing the resources (tape drives). The end result is that the media server will figure this out, give the message below, and requeue the job. -Tim On Wed, 8 Feb 2006, Asiye Yiğit wrote: Hi Gurus... What do you think the cause of the problem presented as the following... 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 INF - Duplicate of backup id sokrates_113881 failed, unable to process request because the se rver resources are busy (134). 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 INF - Duplicating policy Sistem_State_2003 schedule gunluk backup id diogenes_1138833346 copy 1 c reated on 02/02/2006 00:35:46 on source path D:\diskeyedek 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 INF - host yedeklemesrv backupid diogenes_1138833346 write failed, unable to process request beca use the server resources are busy (134). 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 INF - Duplicate of backup id diogenes_1138833346 failed, unable to process request because the se rver resources are busy (134). 02:52:40.498 [3696.444] 2 ds_dup: read from job 1 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - Duplicating policy Sistem_State_2003 schedule gunluk backup id yedeklemesrv_1138833488 copy 1 created on 02/02/2006 00:38:08 on source path D:\diskeyedek 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - host yedeklemesrv backupid yedeklemesrv_1138833488 write failed, unable to process request because the server resources are busy (134). 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - Duplicate of backup id yedeklemesrv_1138833488 failed, unable to process request because th e server resources are busy (134). 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - Duplicating policy Sistem_State_2003 schedule gunluk backup id hercules_1138833519 copy 1 created on 02/02/2006 00:38:39 on source path D:\diskeyedek 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - host yedeklemesrv backupid hercules_1138833519 write failed, unable to process request because the server resources are busy (134). 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - Duplicate of backup id hercules_1138833519 failed, unable to process request because the server resources are busy (134). 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 02:53:25.999 [3696.444] 2 ds_dup: read from job 1 INF - Duplicating policy Sistem_State_2003 schedule gunluk backup id fwmngt_1138833672 copy 1 cre ated on 02/02/2006 00:41:12 on source path D:\diskeyedek --More--(19%) Asiye Yigit Software Support Manager Gantek Technologies Direct : +90 0216 538 80 94 Fax: +90 0216 322 04 43 Gsm: +90 0532 409 80 46 Adress: Adres: Cumhuriyet Cad. Yeni Parseller Sk. No: 20 B Blok Kat:4-5 34805 Kavacik / İstanbul [EMAIL PROTECTED] www.gantek.com http://www.gantek.com/ This message and attachments are confidential and intended solely for the individual(s) stated in this message. If you received this message although you are not the addressee you are responsible to keep the message confidential. The sender has no responsibility for the accuracy or correctness of the information in the message and its attachments. Our company shall have no liability for any changes or late receiving, loss of integrity and confidentiality, viruses and any damagescaused in anyway to your computer system. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Restricting tapes to a single stream
Well, there's no setting of this kind, so you'll need other workarounds... As you mentioned, single stream backup. Not very desirable, so that's out. The only other item I can think of is to suspend the tapes which were used when each stream is done. This will prevent any subsequent backups from selecting it again. You'd have to script this and I'm sure someone has an example you could work from. Essentially, this is a backup exit script which will determine the tape which was used, then issue a bpmedia -suspend command.Î HTH. -Tim On Jan 31, 2006, at 9:53 AM, Jeff Lightner wrote: To forestall further answer of this kind: I am NOT looking for assistance in resolving the 52 error on the backup. This problem would be caused if the issue had been any other issue that caused a retry so wouldn’t be restricted to a status 52 exit in any event. I am NOT looking for “better” methods of doing a refresh. What IS being asked is if there is a way to prevent a single backup from using the same tape on two different streams given that the backup in question has multiple streams (e.g. please do not respond that I could prevent it by doing the backup as a single stream). From: Greenberg, Katherine A [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 31, 2006 10:22 AM To: Jeff Lightner; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Restricting tapes to a single stream Why don't you try to identify and repair what is causing the 52 errors? There are a few technotes and fixes for that specific error code, as it is fairly common. ~Kate -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Tuesday, January 31, 2006 9:20 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Restricting tapes to a single stream Is it possible to setup a policy in such a way that any stream will not use a tape previously used within another stream of the same backup? Background: We run our Production DB backup using 3 streams. This backup is used for doing refreshes to test and training databases. On occasion during the original backup we’ll see a status 52 forces one of the streams to timeout and do a new try which is successful. Unfortunately the new try on that stream may occur after one of the other 2 streams has finished with a tape so it grabs that tape for this stream. This is OK but on restore it won’t even schedule the 3rd stream until after the stream that originally used the tape has finished restoring so of course it causes a long delay in refresh. I didn’t see a setting in the policy definition so I’m wondering if there is a bp.conf or other setting that would prevent the use of the same tape within two different streams of the same backup? Jeffrey C. Lightner Unix Systems Administrator DS Waters of North America 678-486-3516 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
Re: [Veritas-bu] Catalog backups on Solaris
Andrew, This is very normal and it's ok. Basically as long as the last value in the path IS NOT a link, netbackup will backup the path properly. So, if you have say your db dir mounted to some really big fs as /nbu_db and it's linked to /usr/openv/netbacup/db, don't specify /usr/openv/netbackup/db as the path to backup, else you'll end up with just the link backed up and not the data. You'd want to specify /nbu_db as the path instead. But the default uses a middle link and NBU is able to figure that one out and backup the real data. The tricky part comes in during a recover. You need to make sure all the links exist else you could fill a fs pretty easily. Best practices would suggest that you backup based on host name:real path... For example hostname:/opt/openv/netbackup/db etc, etc.. HTH -Tim If you just list On Jan 19, 2006, at 1:35 PM, Andrew Stueve wrote: I ran into something odd. I may be suffering from lack of sleep, but Solaris actually installed NetBackup in /opt/openv and creates a symlink /usr/openv. The backup catalog all specify /usr/openv/x. There won't be a problem with the symlink, will there? Since the directories underneath are specified (ex /usr/openv/netbackup/db ), we should be good. Yes? Personally, I haven't had to do a recovery from tape on Solaris. I have only done it on Windows. -- Andrew Stueve [EMAIL PROTECTED] 571-437-5754 ___ 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] Netbackup w/ Robot WITHOUT Barcode Reader
I'd suggest that you do a vmadd (or GUI) to add all the volumes and ensure their slots are correct. Then bplabel (or right click and label from the GUI) them. Once they've all got labels, you can use vmphyinv to physically inventory the robot. If it's a large robot with lots of tapes and you'd like to skip the bplabel option, ensure all the tapes are in the right slots and then just initiate backups. NetBackup will automatically label the tape to match what it has in the volume database. But make sure that if NetBackup thinks tape ABC123 is in slot 1 and XYZ789 is in slot 2 that's where they really are. If they're swapped, you'll end up with ABC123 on the outside of the tape and XYZ789 on the inside. This scenario isn't too bad with just 2 tapes, but with lots of tapes, it's REALLY ugly. HTH -TIm On Jan 17, 2006, at 8:11 AM, Martin, Jonathan (Contractor) wrote: One of my remote sites just bought a new library with NO BARCODE READER!!! (DOH!) While I try and get this sorted out (new PO for BARCODE READER,) does anyone have any tips for configuring netbackup with such a device? Thanks, -Jonathan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Cancel a bpbackupdb - NBU 3.4 - Solaris - [Summary]
yep, that's correct, 3.4 bpdbjobs won't show the catalog backups. however, I'm pretty sure vmoprcmd -d would have shown the pending request. Then you can also use vmoprcmd -deny # to deny the tape mount. Additionally, you may want to set the media mount timeout value so that if the catalog tape isn't available in the future, scheduled backups won't be held up too long. If you do choose to set the mmto value, don't set it to anything less than 30 minutes. I've seen too many times where 30 minutes has caused problems for tapes which did take that long to mount (think DLT type media). HTH -Tim On Dec 29, 2005, at 8:17 AM, Francisco Puente wrote: Hi, I've ended up killing the bpbackupdb and bpdbm directly from the OS. Bpdbjobs didn't show the processes since they are catalog backups jobs. Thanks, Francisco -Original Message- From: Tim Hoke [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 28, 2005 6:38 PM To: [EMAIL PROTECTED] Cc: Francisco Puente; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Cancel a bpbackupdb - NBU 3.4 - Solaris I'm not sure if this will apply in 3.4 or not, but since bptm appears to have requested the load of a tape, does a pending request for the tape show up? If so, deny the pending request and the job will terminate nicely. Use vmoprcmd to check for and also deny the pending request. HTH -Tim On Dec 28, 2005, at 12:14 PM, [EMAIL PROTECTED] wrote: Got to start whacking the processes directly. v3.4 didn't integrate the catalog backups into the bpjobs database until v4.x. So, your cmd line is simply kill -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Francisco Puente Sent: Wednesday, December 28, 2005 10:59 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Cancel a bpbackupdb - NBU 3.4 - Solaris Hi List, What is the _command line_ option, if any, to cancel/kill a job that is trying to use a non-existing tape for the DBBACKUP? # bpps -a NB Processes root 8716 8715 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/admincmd/bpbackupdb -seq 1 root 8710 295 0 Dec 27 ?0:00 bpcd root 8816 5431 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/bpsched root 5431 1 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/bprd root 5528 1 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/bpsched -mainempty root 5436 1 0 Dec 27 ?0:02 /usr/openv/netbackup/bin/bpdbm root 8718 8716 0 Dec 27 ?0:00 bptm -load -ev TAPE214 -den 15 -sync -v TAPE214 is not longer in the robot, and the dbbackup is waiting for it I assume. I just changed the NBU configuration to use another media ID for the DBBACKUP, but I can't get rid of this process from the command line, I don't have GUI access. Any help will be very welcome! Thanks in advance, Francisco ___ 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 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] Cancel a bpbackupdb - NBU 3.4 - Solaris
I'm not sure if this will apply in 3.4 or not, but since bptm appears to have requested the load of a tape, does a pending request for the tape show up? If so, deny the pending request and the job will terminate nicely. Use vmoprcmd to check for and also deny the pending request. HTH -Tim On Dec 28, 2005, at 12:14 PM, [EMAIL PROTECTED] wrote: Got to start whacking the processes directly. v3.4 didn't integrate the catalog backups into the bpjobs database until v4.x. So, your cmd line is simply kill -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Francisco Puente Sent: Wednesday, December 28, 2005 10:59 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Cancel a bpbackupdb - NBU 3.4 - Solaris Hi List, What is the _command line_ option, if any, to cancel/kill a job that is trying to use a non-existing tape for the DBBACKUP? # bpps -a NB Processes root 8716 8715 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/admincmd/bpbackupdb -seq 1 root 8710 295 0 Dec 27 ?0:00 bpcd root 8816 5431 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/bpsched root 5431 1 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/bprd root 5528 1 0 Dec 27 ?0:00 /usr/openv/netbackup/bin/bpsched -mainempty root 5436 1 0 Dec 27 ?0:02 /usr/openv/netbackup/bin/bpdbm root 8718 8716 0 Dec 27 ?0:00 bptm -load -ev TAPE214 -den 15 -sync -v TAPE214 is not longer in the robot, and the dbbackup is waiting for it I assume. I just changed the NBU configuration to use another media ID for the DBBACKUP, but I can't get rid of this process from the command line, I don't have GUI access. Any help will be very welcome! Thanks in advance, Francisco ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] 5.1 MP4
Take a look at the following TechNote for a really good write-up on this subject... http://support.veritas.com/docs/280398 Also this one for 6.0: http://support.veritas.com/docs/280067 -Tim On Dec 16, 2005, at 5:53 PM, Geyer, Gregory wrote: John, GREAT INFORMATION! Now, to investigate whether MAX_STAGING_JOBS is per DSSU or altogether (ie, if DSSU#1 kicks off first and grabs all the jobs, what does DSSU#2 do?) Thanks again, the list rocks. G. -Original Message- From: Nardello, John [mailto:[EMAIL PROTECTED] Sent: Friday, December 16, 2005 4:26 PM To: Geyer, Gregory Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] 5.1 MP4 From the MP4 readme: Etrack Incident = ET313352 Description: Disk staging only submits one duplication job at a time so it was unable to make use of idle tape drives. Additional Notes: Up to four bpduplicate jobs are submitted at a time. The duplication jobs contain images grouped into jobs of 25 Gigabytes. By creating files named MAX_STAGING_JOBS and STAGING_JOB_KB_LIMIT in the NetBackup directory on the master server, these defaults can be adjusted as needed. For the STAGING_JOB_KB_LIMIT, the value is in kilobytes and the default is 26214400 (25 gigabytes). A smaller value causes more jobs to be submitted, but there will only be MAX_STAGING_JOBS running at a time. It's not a bug, it's a feature. I've also seen those bid files present under 5.1 MP3a so it's nothing new anyway. I haven't seen hundreds either so I'm pretty sure NB is cleaning up after itself at some point. - John Nardello Your backups are only as good as your restores. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geyer, Gregory Sent: Friday, December 16, 2005 3:14 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 5.1 MP4 We've upgraded to 5.1 MP4 and are now experiencing issues with Disk staging. We've got a ticket open but interested to see if anyone else has experience these issues: The disk staging process now automatically takes 4 tape drives per DSSU when going off to tape. This is a problem if you have 6 DSSUs and only 15 tape drives, not to mention those drives are needed for other media servers. It is now also creating these files on the DSSU media servers in /usr/openv/netbackup: root@hostname:/usr/openv/netbackup# ll bid* -rw-rw-rw- 1 root root 1984 Dec 15 13:20 bid_file_bladestore_oracle0 -rw-rw-rw- 1 root root 530 Dec 16 13:08 bid_file_bladestore_oracle_1_15240 -rw-rw-rw- 1 root root 1219 Dec 16 13:08 bid_file_bladestore_oracle_2_15240 -rw-rw-rw- 1 root root18 Dec 16 13:08 bid_file_bladestore_oracle_3_15240 -rw-rw-rw- 1 root root 293 Jul 1 2004 bid_file_bladestore_staging_1TB0 -rw-rw-rw- 1 root root 4375 Dec 15 10:04 bid_file_bladestore_unix0 SNIP In the files are a listing of images to get backed up. ___ 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] how much space left on media
I think bpmedialist might be a better option for you. That will show how much data is on each tape (essentially your sum of all images). However, it's not very scientific since there's hardware compression involved. You can use the numbers as a rough gauge is all. HTH -Tim On Dec 4, 2005, at 3:12 AM, john hanson wrote: Dear ALL I am using bpimmedia command adding space of each image . Is there any other way to check how much space left on media . Thanks and Regards JH __ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs ___ 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] Can a cluster use a SAN media server license to backup bothe physical nodes?
yes, i believe a SAN Media Server is supposed to work. However, I do know there were some bugs which limited the functionality. Check your version number, patch up (if you haven't) and if that doesn't work, call Symantitas, they'll get it squared away. -Tim On Nov 30, 2005, at 1:43 PM, Bob Stump wrote: I think I may have to use a full media server license?? server-V = virtual server-A = physical server-B = physical I have installed a SAN media server license on server-V to backup the common drives and this works fine. However, when I try to backup the local drives on each individual physical server, I get a license use has been exceeded (code 159) Must I backup the C:\ and D:\ drives on the physical server-A and server-B as a regular client over the network to another media server? or..upgrade to a full media server license? ___ 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] yes sir, obviously insane (6.0 upgrade question)
What you refer to is a problem NetBackup runs into because of the limited kernel support for passthrough devices. Basically, for a given tape drive, NetBackup needs to be able to quickly map the data path (/dev/nst) to the passthrough path (/dev/sg) so that SCSI Reserve/Release (among other things) can happen properly. In order to do this, there's a make_scsi_dev command which will determine the mappings and create links in the appropriate /dev/st/ and /dev/sg/ dirs. In pre-2.6 kernels, this is the only way to do things and as such, since the make_scsi_dev also includes a scsi inquiry command, devices which are reserved won't be linked. In 2.6 kernels, there's native mapping which makes this processing unnecessary, but I'm not sure what it looks like if one of the devices is busy. Seems to me this is a limitation on any OS... If the drive's reserved to one host, another host can't inquire it and therefore can't determine what it is in order to configure it. HTH -Tim On Nov 30, 2005, at 5:55 PM, [EMAIL PROTECTED] wrote: In our case, we could. However, if the tape drive was reserved by another server, then it wouldn't be properly discovered built into Netbackup's config stuff. The OS could see an unassigned one just fine. -M -Original Message- From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 30, 2005 3:59 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] yes sir, obviously insane (6.0 upgrade question) Actually the problem was at the OS level. It wouldn't see tape drives through the bridges properly. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 30, 2005 2:25 PM To: Jeff Lightner; [EMAIL PROTECTED]; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] yes sir, obviously insane (6.0 upgrade question) The problems were mostly related to SSO - problems discovering devices managing scsi reserves placed by other media servers on shared tape drives. Those using one-drive-one-server architectures didn't seem to have complaints. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jeff Lightner Sent: Wednesday, November 30, 2005 12:00 PM To: Dan Dobbs; Veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] yes sir, obviously insane (6.0 upgrade question) I don't have answers to what you wrote but did want to caution you about using RH for your master. I've not been able to get RH EL AS 3 to properly recognize my SAN environment. From an earlier thread on this list it appears I wasn't the only one. Not sure if you're running SAN or direct SCSI but if the former thought it best to mention it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Dobbs Sent: Wednesday, November 30, 2005 1:21 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] yes sir, obviously insane (6.0 upgrade question) Greetings, list. Here's my situation. I have a HP-UX media/master server on 5.1 with a newer Neo SDLT bot and an ancient DLT4000 Surestore bot. We're going to be getting a shiny new Red Hat box soon to take over migrate backup services. I've just read the upgrade docs for 6.0, and I have to say that I'm a little overwhelmed. If I read it right, an upgrade to 6 requires all the clients to get the security software installed and upgraded to 6 as well before they can get backed up, something I'm not sure I can accomplish in a day. In short, I'm considering leaving my HP-UX box at 5.1, and building the new RH box on 6. My plan was to remove the Neo SDLT juke out of the 5.1 environment, plug it into my RH box,and import tapes there (as we've used less than 30 SDLT's, it shouldn't be a huge deal). This would allow me to do the icky client-side upgrades piecemeal, as I moved them to 6.0, they would then back up to the new box. Eventually, as all the clients moved over, I could then move the old jukebox and stop operations on the HP-UX box. The obvious problem is recovery; until I import every single tape, I wouldn't know what tapes had backups from the 'old' system. I guess the thrust of the matter is: 1) Is the upgrade of an in-place 5.1 server to 6 easier than it reads on paper? 1a) Do I really have to upgrade my clients to 6 before the server will talk to them? 2) If I was running 6 on the 'old' system, could I follow the previous advice, and move /usr/openv/netbackup/db and /usr/openv/volmgr/database, run the proper vmglob and bpmedia commands on the new box and be done? Thanks again for all your help! -dd ___ 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] Patch MP3A-S2
I tried this out and found that after I installed encryption, I too was getting status 9. I recycled the daemons and now it's gone. Have you tried that? -Tim On Nov 21, 2005, at 2:31 PM, WALLEBROEK Bart wrote: The readme file of the patch itself is indeed speaking about IBM Linux. We don't use Linux. Only Solaris, and Windows. The error 9 is shown when a policy (with patched clients) runs. The policy has the encryption option set. Every patched client job ends with status 9. When I remove the encryption option from the policy the backup runs fine. Best regards, Bart Wallebroek Backup Admin SWIFT -Original Message- From: Tim Hoke [mailto:[EMAIL PROTECTED] Sent: Monday, November 21, 2005 8:51 PM To: WALLEBROEK Bart Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Patch MP3A-S2 What is the note? I looked at the readme info and there's a note about Linux clients. Is that what you are referencing? Can you elaborate on where/when you get the error 9 message? Thanks -Tim On Nov 21, 2005, at 10:45 AM, WALLEBROEK Bart wrote: Last week Friday I patched all our Solaris servers with the latest NetBackup patch. Now these servers cannot be backed up anymore as the Encryption module seems to be dissappeared (error 9: an extention package is not installed). There is indeed a (small) note in the patch release that I overlooked. What is the solution to this ? Re-push the encryption software to all clients from the Master Server ? Best regards, Bart Wallebroek Backup Admin SWIFT ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcoverage // NBU 6.0
Hmmm... Seems to work for me when running on a RHEL 3 system against a RHEL 3 system. It also works for me on other various combinations. Can you give any more details? -Tim On Nov 16, 2005, at 11:07 AM, James Pattinson wrote: All, Shame to see that bpcoverage does NOT work on 6.0. It segfaults on Linux and DrWatsons on Windows. This is a very useful command but unfortunately it's not supported since it's not in the manual. Just thought I'd let you know. It might be worth mentioning this to your Veritas guys if you had found bpcoverage useful in the past for checking connectivity to clients. Cheers James -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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
