RE: [Veritas-bu] Can this be done?
3) originator collects replies and posts resolution or further enquirers Laudable goal; not gonna happen. Hardly anyone who didn't learn in ARPANet or Usenet days has ever _seen_ reply-to-me-I'll-post-a-summary-to-the-list, or other responsible behaviors in a mailing list: trimming replies, bottom-posting, et cetera. Doesn't make them/us bad people--just ones that have never seen what right looks like. But, very unfortunately there are also members that cancel their subscription due to the high level of activity. And the pages of HTML (like yours had, BTW--330 lines of it) and quoted-printable crap that takes time to sort through to find the few lines of text in messages? My estimate is that wastes far more of my time than multiple replies. Replies direct to me, please; I'll summarize and post to the list. :-) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] nbpem process terminating
Hi, We have just recently upgraded our Solaris master server from NBU 5.1 to NBU6.0 MP2. Only our Master server has been upgraded at this stage. Since the upgrade, the nbpem process seems to die about once a day, causing jobs to stop getting scheduled. Support have told me that there is a know issue with nbpem when checkpoint restarts are enabled, so I have disabled them all, but the nbpem process still dies for no apparent reason. The nbpem log does not show any errors. It appears as though the process simply dies. Has anyone seen this? Ian Fehring Lead Technical Specialist, Storage Management National Australia Bank Level 1, 122 Lewis Rd Tel: +61 (0) 3 9886 2367 | Fax: +61 (0) 3 9886 2700 | Mob: +61 (0)417 520 953 Email: [EMAIL PROTECTED] National Australia Bank Limited - ACN 004 044 937 This email may contain confidential information. If you are not the intended recipient, please immediately notify us at [EMAIL PROTECTED] or by replying to the sender, and then destroy all copies of this email. Except where this email indicates otherwise, views expressed in this email are those of the sender and not of National Australia Bank Limited. Advice in this email does not take account of your objectives, financial situation, or needs. It is important for you to consider these matters and, if the e-mail refers to a product(s), you should read the relevant Product Disclosure Statement(s)/other disclosure document(s) before making any decisions. If you do not want email marketing from us in future, forward this email with unsubscribe in the subject line to [EMAIL PROTECTED] in order to stop marketing emails from this sender. National Australia Bank Limited does not represent that this email is free of errors, viruses or interference ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Can this be done?
I understand your point Bob, but tend to agree with most of the other comments. Turning this into more like the sunmanagers list would completely change the dynamic. I think it's valuable to be able to see all responses as people work through a problem together. This is a fantastic mailing list and I really don't want to see it changed. The way I avoid the overflowing inbox issue is that I subscribe to veritas-bu from gmail, and use a filter to move all veritas-bu messages into a folder and archive them. gmail's search features are fantastic and it greatly increases the value of the information in this mailing list. I believe I have over 18 months of veritas-bu messages now in my gmail box, all easily searchable, along with several other busy mailing lists, and I'm still under 10% capacity.. Plus, I don't have to read or delete each and every message. At the moment, my veritas-bu folder has 950 unread messages, which I can read if/when I need to. I appreciate that not everyone can access gmail from work, but if you can, I highly recommend it as a receptacle for this and other similar mailing lists.The other option is moving to a forum type thing, which, as mentioned, has been tried before and didn't work out. CheersDeanOn 5/13/06, Bob Stump [EMAIL PROTECTED] wrote: The knowledge and experience level in this group is valuable. Unfortunately it is also very busy with a single thread growing into multiple replies to all. Can the volume be cut down by following this simple etiquette? 1) originatorposts question 2) participants reply directly to the originator (not reply all) 3) originator collects replies andpostsresolution or further enquirers 4) participants reply directly to the originator'sadditional questions 5) originator posts solution I have already started following the above described procedure and sent my replies to the originators only. If just the regularly active members follow this etiquette, then perhaps we can grow into a larger community. I realize that not all will comply because new members are added every day. But, very unfortunately there are also members that cancel their subscription due to the high level of activity.
RE: [Veritas-bu] What command cleans out DSSU's?
Title: What command cleans out DSSU's?
First, look at your global setting of "maximum
copies". If it is higher than 2, this will give you more
copies.
Also, go to the storage units area of the GUI and manually
run the staging to make sure that you are up to date.
On the dssu, there are files (all less than 2GB) named
{system_name}_{utime}_F$$ and there are files of "0" size named the same but
with "ds" at the end.
The file with the "ds" at the end are files that NB thinks
it has put on disk. The other files are the backup images named (in the
above format) as the backupid and the fragment number (dsu and dssu are limited
to 2GB fragments).
All NB is doing on the dssu is duplicating the images to
tape. Copy 1 is on disk, copy 2 (thru ...) is on tape. When the
duplication process completes successfully (the way it is designed anyway), the
backupid_fragment.ds file is created to let NB that it can be purged if
necessary.
You can check each file that ends in F1 (fragment 1) and
use bpimagelist to see how many copies you have. If the ds file version of
the file exists, you should show copy 1 or primary to be on the DSSU and copy 2
to be on tape (or wherever you stage to).
If you can verify that you have 2 copies, you can use
"bpexpdate -d 0 -copy 1 -backid {backupid} -force" to expire the copy that is on
disk.
That will clear up the DSSU.
Bobby Williams
2205 Peterson
Drive Chattanooga, Tennessee 37421 423-296-8200
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hillman,
EricSent: Friday, May 12, 2006 2:55 PMTo:
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] What command
cleans out DSSU's?
We use Disk Staging Storage Units in our Netbackup
5.0 MP5 environment. When jobs fail for whatever reason, the image files
created up to that point still stay on disk. At some point, they get
removed by Netbackup, but it's not immediate. This used to be a huge
problem pre mp5. In MP5, Veritas added better cleanup processes, but they
don't go into detail as to how it works. Can someone tell me what process
goes through DSSU's looking for invalid images to remove and when that process
runs? Also, is it possible to run that process manually at
will?
Thanks in advance for any help! THE
INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED,
CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader
of this message is not the intended recipient, you are hereby notified that any
dissemination, distribution, copying or use of this message and any attachment
is strictly prohibited. If you have received this message in error, please
notify us immediately by replying to the message and permanently delete it from
your computer and destroy any printout thereof.
RE: [Veritas-bu] What command cleans out DSSU's?
Title: What command cleans out DSSU's?
Booby,
Thank you! It's actually not the valid images
that automaticatlly get removed that I am trying to clean. It's the
invalid image files that get left on disk when jobs fail that I need to find and
clean. The only way I know of is to wait until I get error code 190's when
manually running archival to tape and then finding all *.F1 files without a
corresponding .ds extention. Then I can remove all of those image files
that belong to that invalid image.
From: Bobby Williams
[mailto:[EMAIL PROTECTED] Sent: Saturday, May 13, 2006 7:07
AMTo: Hillman, Eric;
veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] What
command cleans out DSSU's?
First, look at your global setting of "maximum
copies". If it is higher than 2, this will give you more
copies.
Also, go to the storage units area of the GUI and manually
run the staging to make sure that you are up to date.
On the dssu, there are files (all less than 2GB) named
{system_name}_{utime}_F$$ and there are files of "0" size named the same but
with "ds" at the end.
The file with the "ds" at the end are files that NB thinks
it has put on disk. The other files are the backup images named (in the
above format) as the backupid and the fragment number (dsu and dssu are limited
to 2GB fragments).
All NB is doing on the dssu is duplicating the images to
tape. Copy 1 is on disk, copy 2 (thru ...) is on tape. When the
duplication process completes successfully (the way it is designed anyway), the
backupid_fragment.ds file is created to let NB that it can be purged if
necessary.
You can check each file that ends in F1 (fragment 1) and
use bpimagelist to see how many copies you have. If the ds file version of
the file exists, you should show copy 1 or primary to be on the DSSU and copy 2
to be on tape (or wherever you stage to).
If you can verify that you have 2 copies, you can use
"bpexpdate -d 0 -copy 1 -backid {backupid} -force" to expire the copy that is on
disk.
That will clear up the DSSU.
Bobby Williams
2205 Peterson
Drive Chattanooga, Tennessee 37421 423-296-8200
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hillman,
EricSent: Friday, May 12, 2006 2:55 PMTo:
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] What command
cleans out DSSU's?
We use Disk Staging Storage Units in our Netbackup
5.0 MP5 environment. When jobs fail for whatever reason, the image files
created up to that point still stay on disk. At some point, they get
removed by Netbackup, but it's not immediate. This used to be a huge
problem pre mp5. In MP5, Veritas added better cleanup processes, but they
don't go into detail as to how it works. Can someone tell me what process
goes through DSSU's looking for invalid images to remove and when that process
runs? Also, is it possible to run that process manually at
will?
Thanks in advance for any help! THE
INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED,
CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader
of this message is not the intended recipient, you are hereby notified that any
dissemination, distribution, copying or use of this message and any attachment
is strictly prohibited. If you have received this message in error, please
notify us immediately by replying to the message and permanently delete it from
your computer and destroy any printout thereof.
THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
Re: [Veritas-bu] Status: 525 Can not connect to NB-Java
When I get this error in Linux it usually means that the 'vnetd' entry is not in /etc/services, once it is and (x)inetd is restarted, then it works. Solaris 10 doesn't use inetd though, so you'll have to check its equivilent. On 5/11/06, Yosifovski, Tammy [EMAIL PROTECTED] wrote: Solaris 10, NB 6.0 Receiving the following error when using jnbSA. Unable to login, status: 525 Can not connect to the NB-Java authentication service via VNETD on server name on port 13724. Check the log file for more details. Log file States: ServerInterface:Logon: java.net.ConnectException: Incompatible VNETD version: . ServerInterface:Logon - Initial host:null, Current host:migrrufsmc82, Firewall Env:true, MS port:13722, VNET D:13724, m_intPort:0, localPort:0, range use:false Can not connect to the NB-Java authentication service via VNETD on migrrufsmc82 on port 13724. Exception: java.net.ConnectException: Incompatible VNETD version: . ServerInterface:Logon: java.net.ConnectException: Incompatible VNETD version: . ServerInterface:Logon - Initial host:null, Current host:migrrufsmc82, Firewall Env:true, MS port:13722, VNET D:13724, m_intPort:0, localPort:0, range use:false Can not connect to the NB-Java authentication service via VNETD on migrrufsmc82 on port 13724. Exception: java.net.ConnectException: Incompatible VNETD version: . There are not any firewalls to block the port. Your help is appreciated. Tammy Yosifovski - Thise-mailistheexclusive,privateandconfidentialpropertyofthesender.The informationcontainedinitisintendedsolelyfortheuseofthesenderandthe intendedrecipient.Ifyouarenottheintendedrecipientyouareherebyadvisedthat anyunauthorizeddisclosure,copying,distributionorthetakingofanyactionin relianceonthecontentsofthismessageisstrictlyprohibited.Ifyouhavereceived thise-mailinerror,pleasenotifyusimmediatelybytelephone(calltheTechnical SupportCenterat1-888-873-8721)andthendestroythisdocumentandanycopiesin anyformimmediately.Finally,therecipientshouldcheckthisemailandany attachmentsforthepresenceofviruses.Senderacceptsnoliabilityforanydamage causedbyanyvirustransmittedbythisemail. -
RE: [Veritas-bu] Can this be done?
I'll do this, but I need some help organizing it and generating content. Here's a first pass at a phpbb for storage topics. All I need is content: http://www.safedatasite.com/bb I can keep it active as long as the volume is manageable. Constructive advice and comment is appreciated. Mickey Baker Safe Data Services, LLC Independent Storage Consultant From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan (Contractor) Sent: Friday, May 12, 2006 1:50 PM To: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Can this be done? Has anyone considered hosting a website for this topic? I'm not saying that every would want to join or could, but forums could be established so people would only have to read what they wanted to, and all the information would be kept centrally. Fixes to problems could be taken from the forums and posted into a knowledge base which would clean up the presentation of these conversations. I know someone tried to start a Yahoo group a while ago and that seemed to fizzle. I think a proper website would attract even more Netbackup professionals than this this group already has. I know when I stumbled upon this group I had already been working with Netbackup for quite some time and happened upon an old archive dealing with a problem I had which led me to email and sign up. In the mean time, I just route all messages from this list to a certain folder via email rules and catch up when I can. On busy days I simply ignore that folder. Can ya tell I'm a little laid back today? 8) -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Stump Sent: Friday, May 12, 2006 12:11 PM To: veritas-bu@mailman.eng.auburn.edu Cc: Doug Hughes Subject: [Veritas-bu] Can this be done? The knowledge and experience level in this group is valuable. Unfortunately it is also very busy with a single thread growing into multiple replies to all. Can the volume be cut down by following this simple etiquette? 1) originator posts question 2) participants reply directly to the originator (not reply all) 3) originator collects replies and posts resolution or further enquirers 4) participants reply directly to the originator's additional questions 5) originator posts solution I have already started following the above described procedure and sent my replies to the originators only. If just the regularly active members follow this etiquette, then perhaps we can grow into a larger community. I realize that not all will comply because new members are added every day. But, very unfortunately there are also members that cancel their subscription due to the high level of activity. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Planned Network Outage - What should I do about backups?
Hi, One way would be to enable checkpoints in your backup policies and then, pause the jobs, about 45 minutes before the outage and, resume the jobs after your network comes upbut you would need to test this. jayanth On Sat, May 13, 2006 22:24, Justin Piszcz said: One comment - running all fulls on the weekend is an extremely bad practice, if something happens on Friday, then you lose a week's worth of data, depending on your incremental schedule. A better practice is to run Fulls each day of the week and split it up in your environment. When the connection is cut the jobs should fail, but I have not done too much with DSSU/disk backups myself to comment on that part. On 5/12/06, Hillman, Eric [EMAIL PROTECTED] wrote: We start weekly backups every Friday night. They run through Sunday. There is a scheduled network outage on Saturday morning between 5am and noon. This will disconnect clients from the backup servers and the media servers from the master servers. Can anyone recommend the best way to pause these jobs? Here are the choices I'm considering: 1. Stop Netbackup daemons on all master and media servers Friday night and restart them after the network outage is done. I believe this will not allow all backups enough time to finish by Sunday night when our next backup window starts 2. Don't do anything. I'm not sure what will happed to jobs that are running including User database backups which get sent to the master server and run on a media server when the communication between those servers is gone. Also DSSU archival to tapes may experience problems when communication is cut between the master server who is sending the list of backup images to the media server to archive to tape. 3. Login immediately prior to the network outage and kill all backup jobs, stop Netbackup deamons and restart deamons after the network is back up. This has never ended cleanly. There's always jobs that don't stop. I almost always need to do some kill -9's to get the job processes to die and the rest of the daemons to stop. Also, partial images will be left on DSSU's which won't get removed. When jobs get restarted, they'll eventually run out of disk space because Netbackup left those partial images. Does anyone know of an easy way of cleaning out partial images on DSSU's? Any recommendations are helpful. Thanks! THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. ___ 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
