[Veritas-bu] Purging hosts from Symantec OpsCenter
We've been running Symantec OpsCenter for some time now and we see dead clients in OpsCenter. We have 96 unique clients, OpsCenter however shows 140 unique clients. Most of the false clients are old clients, servers which we've deleted for some time now, some are existing clients but with the domain suffix added to the hostname. In OpsCenter I can easily recognise them when I go to: Monitor Hosts Client the dead clients have the value - in OS Type and Hardware All these clients have been properly removed from policies and host properties in the NetBackup Java Administration Console. There is no trace of them there, but they appear to remain forever in OpsCenter which is sabotaging our reports as filtering hosts in reports is becoming more time consuming. Is there a way to remove dead clients from OpsCenter? P.S: Examples of affected reports are the Client Dashboard Summary and the RPO report. +-- |This was sent by muzz...@hotmail.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
Re: [Veritas-bu] Purging hosts from Symantec OpsCenter
On Wed, Apr 7, 2010 at 3:34 AM, nez netbackup-fo...@backupcentral.comwrote: We've been running Symantec OpsCenter for some time now and we see dead clients in OpsCenter. We have 96 unique clients, OpsCenter however shows 140 unique clients. Most of the false clients are old clients, servers which we've deleted for some time now, some are existing clients but with the domain suffix added to the hostname. In OpsCenter I can easily recognise them when I go to: Monitor Hosts Client the dead clients have the value - in OS Type and Hardware All these clients have been properly removed from policies and host properties in the NetBackup Java Administration Console. There is no trace of them there, but they appear to remain forever in OpsCenter which is sabotaging our reports as filtering hosts in reports is becoming more time consuming. Do you still have valid images in your catalog for those clients? .../Ed ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] per-directory policies a la NetWorker?
Not quite like that. You can create an exclude list with policy name in /usr/openv/netbackup on target to tell that policy what to exclude though. For example when we backup of OS files of a server we create a policy name indicative of that such as: BARNEY-OS On server, barney, in /usr/openv/netbackup we create a file called exclude_list.BARNEY-OS that contains: /dev/odm /cdrom core /tmp/* /database /oracle That will exclude those items from the backup. You could be as specific as you want. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of David Magda Sent: Tuesday, April 06, 2010 9:22 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] per-directory policies a la NetWorker? NetWorker has a feature where you can put a .nsr file in a directory, and then during backup it's contents will be parse so that you can treat particular files or directories in a special way. An example from the man page: Having a /usr/src/.nsr file containing: +skip: errs *.o +compressasm: . would cause all files (or directories) in /usr/src named errs or *.o (and anything contained within them) to be skipped. In addition, all other files contained in /usr/src will be compressed during save and will be set up for automatic decompression on recover. http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?db=manfname=4%20 nsr http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?db=manfname=uasm Is there a similar feature in NetBackup 6.5 and above? I know there's a $HOME/bp.conf, but is there something that can be dropped in an arbitrary directory? Thanks for any info. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- 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
Re: [Veritas-bu] NDMP backups
I am trying to run NDMP backups with certain paths and I am getting error 99 in the GUI, and the error ndmp_data_start_backup failed, status = 9 (NDMP_ILLEGAL_ARGS_ERR). [...] Backup Selections: [...] /vol/vol2/data/[A-M]* [...] Unfortunately (to my knowledge), wildcards are not supported with NDMP backups. You?ll have to explicitly supply the paths. What Thanks Jonathan. That is fantastic news? Anyone know if that will change or has changed with version 7? This should be an NDMP/filer issue, not anything to do with the backup vendor. NetBackup (or any NDMP DMA) doesn't produce that error; it only passes it back from the NDMP server. NDMP_ILLEGAL_ARGS_ERR is part of the NDMP spec (more than you want to know at www.ndmp.org) and it is returned (for many things, but in this case:) if the NDMP implementation doesn't accept the backup type or variables in an NDMP_DATA_START_BACKUP request. BlueArc filers accept asterisk wildcards; some filers accept them in certain places, other NDMP implementations don't accept them at all. Same thing for accepting directory versus file paths. Isolon accepts all sorts of wildcards and environment variables and a bunch of environment variables Did you RTFM? There's a NetBackup Administrator's Guide for NDMP for every release which tells you how to configure a policy, and has a link to the vendor-specific NDMP guide (http://entsupport.symantec.com/docs/267773). ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Purging hosts from Symantec OpsCenter
I have the same thought as Ed.. do you still have valid images for those servers? From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts Sent: Wednesday, April 07, 2010 6:40 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Purging hosts from Symantec OpsCenter On Wed, Apr 7, 2010 at 3:34 AM, nez netbackup-fo...@backupcentral.com wrote: We've been running Symantec OpsCenter for some time now and we see dead clients in OpsCenter. We have 96 unique clients, OpsCenter however shows 140 unique clients. Most of the false clients are old clients, servers which we've deleted for some time now, some are existing clients but with the domain suffix added to the hostname. In OpsCenter I can easily recognise them when I go to: Monitor Hosts Client the dead clients have the value - in OS Type and Hardware All these clients have been properly removed from policies and host properties in the NetBackup Java Administration Console. There is no trace of them there, but they appear to remain forever in OpsCenter which is sabotaging our reports as filtering hosts in reports is becoming more time consuming. Do you still have valid images in your catalog for those clients? .../Ed ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Jobs Que up but will not Start
I recently noticed that I have a handful of jobs that are qued up, but won't seem to actually run. There have been no changes to the NBU configuration and it was working before. The only change that has occurred is that our network has been re-IP'd (IT assigned new IP's to our servers). Is this the problem? If so, how do I correct the problem quickly? I need to get my backups running again quickly. Thanks, James McDonald System Administrator SAIC - IISBU 410-312-2232 mcdonal...@saic.com mailto:mcdonal...@saic.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Jobs Que up but will not Start
Do they eventually fail? If so after how long? Have you run all the usual tests (bptestbpcd, bpclntcmd, telneting to port bpcd, etc) all these tests should be run from the master, media servers and respective clients (unless of course you find the problem)? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk http://www.linkedin.com/in/patrickjosephwhelan cid:image001.gif@01C99E80.E2717A60 From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of McDonald II, James F. Sent: 07 April 2010 19:25 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Jobs Que up but will not Start I recently noticed that I have a handful of jobs that are qued up, but won't seem to actually run. There have been no changes to the NBU configuration and it was working before. The only change that has occurred is that our network has been re-IP'd (IT assigned new IP's to our servers). Is this the problem? If so, how do I correct the problem quickly? I need to get my backups running again quickly. Thanks, James McDonald System Administrator SAIC - IISBU 410-312-2232 mailto:mcdonal...@saic.com mcdonal...@saic.com image001.gif___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] per-directory policies a la NetWorker?
On Apr 6, 2010, at 21:21, David Magda wrote: NetWorker has a feature where you can put a .nsr file in a directory, and then during backup it's contents will be parse so that you can treat particular files or directories in a special way Thanks to Jeff and Christophe. /usr/openv/netbackup/exclude_list.* should be sufficient. (Though things like skip, null, logasm, and swapasm would be handy. Oh well.) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
