[Veritas-bu] Data Domain Question
Hi all, Anyone using a Data Domain VTL in the following manner? - 1 normal weekly full to start (Saturday/Sunday) - 5 incrementals daily (Monday through Friday) - following Saturday/Sunday create a synthetic full backup - repeat incremental / synthetic full cycle Does this seem like a logical use of the dedupe product? Is it even feasible? What are some of the cons? I want to minimize the hit on the primary systems (reduce the backup window, etc, etc), but still be able to perform full backups every week. I'd also want to replicate all that good stuff to a remote site (which I hear DD is good at ;-) Thanks for any input. Cheers, Jon ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU 6.5 or 6.0MP5
Any report on this for Aptare anyone? Thanks, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cruice, Daniel (US - Glen Mills) Sent: Wednesday, September 26, 2007 8:21 AM To: A Darren Dunham; Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5 or 6.0MP5 As far as the reporting tools, NBU 6.5 will break Bocada. Not sure why, but we had Bocada in here last week discussing our options, and they simply said Bocada will break. And they would not give us a ETA as to when they will have NBU 6.5 support for Bocada. But they did say they are working on it. Thanks Dan -Original Message- From: A Darren Dunham [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 25, 2007 6:37 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5 or 6.0MP5 On Tue, Sep 25, 2007 at 04:58:02PM -0400, Preston, Douglas L wrote: As far as I am concerned 6.5 is better. I have had far less issues with it that I did with any 6.0 MP#. If you have any reporting software it will break it. Do you know the mechanism of this breakage? Do some of the tools change output or something? -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 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 This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Schedule coordination question
NP. If any other Aptare user is interested, just fire me a request, I can send you the same stuff I sent Paul. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Friday, August 03, 2007 9:49 AM To: Paul Keating; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Schedule coordination question I know, bad form to respond to one's own post, but as an FYI another lister hooked me up with some custom report stuff for Aptare, to customise the days to coincide with backup windows. Very cool. Thanks JD. Paul -- -Original Message- From: Paul Keating Sent: August 3, 2007 9:07 AM To: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Schedule coordination question HEAR HEAR!! Same goes for Aptare. My reports come out based on Calander Days, but all I (or most storage admins, I would imagine) care about are successes per backup window. Given the choice, I would prefer user defined days.or who really cares about days, just make it windows. Then I could define my windows as Noon-noon during the week, and noon Friday to noon Sunday (or Monday) for weekend full windows. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: August 3, 2007 4:32 AM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Schedule coordination question I have a question for the group. I've had issues with this for years. Veritas responded that they have about half their customers that want it this way and half that don't, so they don't actively pursue making this better. I suggested that since a lot of backup windows fall somewhere between the 6 PM to 6 AM timeframe, that if they let me define what a backup day is, then I could say that NOON defines a day for me. I believe that would alleviate this issue of double backups in one evening and none until after midnight the next day ... Which then pushes other backups/resources out and causes me status 196's ... Which I then rerun during the day ... Which then sets an eternal motion of failures and late backups in flight until I just skip a night to get everything back in sync. I'd love to hear your thoughts !!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston Sent: Thursday, August 02, 2007 5:16 PM To: Wayne T Smith; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Schedule coordination question I had very minor issues with CBS (calendar-based schedules) and midnight issues. I do know that if you tell it to go on Friday, and you have all windows open, it will actually go Friday morning (just after midnight). Is that what you mean? I don't use CBS for daily backups for the reasons I think you're alluding to. You'll get two backups in one night and no backups until after midnight the next day. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne T Smith Sent: Thursday, August 02, 2007 2:48 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Schedule coordination question Of course! Frequency-based backups don't care about midnight. No joke, if I was recalling my previous post on Calendar-base backups, though. ;-) cheers, wayne Curtis Preston wrote, in part, on 2007-08-02 5:39 PM: You meant that as a joke, right? Almost all of my windows cross midnight. ___ 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 This e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
Re: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5
Ouch, was kind of counting on that... Good thing I asked then. Thanks for the info Paul. -Original Message- From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 12:56 PM To: Dyck, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Ya can't do it with NBU 5.x (group DSSUs in a SUG) It's a new fauture in 6.x Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, Jonathan Sent: August 2, 2007 12:51 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Can I infer that there may be an issue with grouping disk-as-disk filesystems in a storage unit grouping with Netbackup 5.1? That'd be a huge concern of mine... Is anyone (other poor souls like me who can't afford a VTL) out there grouping disk-as-disk filesystems for primary backup? 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. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5
All, Hopefully I've covered my bases here, I never was that good an English student (quoting references and such ;). Also I've never had the luxury of asking the author of a technical book a direct question, but am hoping Curtis will chime in here. Quoting Curtis Preston (p. 283, Backup Recovery, 2007): Some backup products require you to point disk-as-disk backups to a single filesystem. When that filesystem fills up, all the backups fail - even if there is another filesystem with adequate capacity Can I infer that there may be an issue with grouping disk-as-disk filesystems in a storage unit grouping with Netbackup 5.1? That'd be a huge concern of mine... Is anyone (other poor souls like me who can't afford a VTL) out there grouping disk-as-disk filesystems for primary backup? Thanks, Jon PS: Curtis, I couldn't have found a more exact scenario that I'm facing to what's described in your couple of pages here on advantages/disadvantages of disk-as-disk. I won't list off what you've written, (at the risk of a lawsuit or something), but I basically highlighted the entire two sections as exactly applicable to what's currently happening here - kudos. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5
If only it were that easy... (someone once told me it's important not to believe everything you read in books, so I thought I'd confirm it on the internet ;-) -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 1:32 PM To: Dyck, Jonathan; Paul Keating; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 I'm always scared when a question starts out with Curtis said. :) Paul's answer is right, though. 6.0 is stable, now, though. Come on in, the water's warm! --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, Jonathan Sent: Thursday, August 02, 2007 10:18 AM To: Paul Keating; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Ouch, was kind of counting on that... Good thing I asked then. Thanks for the info Paul. -Original Message- From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 12:56 PM To: Dyck, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Ya can't do it with NBU 5.x (group DSSUs in a SUG) It's a new fauture in 6.x Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, Jonathan Sent: August 2, 2007 12:51 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Can I infer that there may be an issue with grouping disk-as-disk filesystems in a storage unit grouping with Netbackup 5.1? That'd be a huge concern of mine... Is anyone (other poor souls like me who can't afford a VTL) out there grouping disk-as-disk filesystems for primary backup? 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. This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. 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] Question on Disk-as-Disk Targets NBU 5.1 MP5
Confused me slightly there, so destaging (basically make a Copy 2 to tape, Copy 1 still exists as primary on disk) will happen until the Low Water Mark is hit? And there's a second setting, High Water Mark, that will initiate the purging of Copy 1 data, making the already-staged images (Copy 2) become the primaries? Here's the kicker I guess: you have to make sure the high mark can keep up with destaging process? I've never worked with destaging, what kind of priority do those dupe jobs get if you're trying to destage while backups are running, can it be tuned with 6.x? I'm assuming this is all done via Vault, or are these just storage unit (group) settings? Great synopsis here though, easily makes it look like a no-brainer in my particular situation to push for 6.x. -Original Message- From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 2:32 PM To: Curtis Preston; Paul Keating; Dyck, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Clarification on Low Water Mark - NBU 6.0 Won't stop destaging (writing images to tape) until it gets to the low water mark, a full DSU will stop expiring images on disk that are already on tape once it gets to X% full. No? -Jonathan -Original Message- From: Curtis Preston [mailto:[EMAIL PROTECTED] Sent: Thursday, August 02, 2007 2:22 PM To: Martin, Jonathan; Paul Keating; Dyck, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 I just reviewed the release notes for 5.0, 5.1, 6.0, and here's my summary of the disk features in the last several versions. 4.5 and below: - basic disk storage units, no disk staging, etc. == 5.0 introduced disk staging - (Disk staging storage unit, or DSSU), but it only de-stages one backup at a time (slow) - DSUs/DSSUs have no concept of capacity. NBU would keep sending backups to a DSU even if a filesystem was full; they will just fail over and over. == 5.1 minor improvements in disk area - introduced unspecified performance improvements for disk backups - DSUs/DSSUs have no concept of capacity. NBU would keep sending backups to a DSU even if a filesystem was full; they will just fail over and over. == 6.0 Major improvements in disk backups - Summary is that if you want to do lots of disk stuff you should upgrade to 6.0. HUGE improvements in this area. - Introduced capacity concept. It monitors the space available on the DSU (i.e. like using df on unix or looking at disk properties in Windows), and you can specify a high water mark that tells it to stop sending data to the DSU when it reaches n% full - Backups that are in process will fail when they hit the high water mark. If you have checkpoints enabled, they'll restart where they left off on the next DSU (if using storage unit groups). - New backups will not be assigned to a full DSU - Disk staging is now just a property of a DSU (no more DSSUs) - Disk staging now de-stages multiple backups at a time - Disk staging also has low water mark that will stop de-staging once it hits that %. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Thursday, August 02, 2007 10:25 AM To: Paul Keating; Dyck, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 To clarify, you can group DSUs and DSSUs in 6.0 but if the disk fills up any backups writing to it fail. One of the 6.5 features is that when the DSU or DSSU fills up the backups will move on to a storage unit with space. I'm not 100% sure exactly how this works, only read the product docs on 6.5. I look forward to implementing it later this year however. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Keating Sent: Thursday, August 02, 2007 12:56 PM To: Dyck, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Ya can't do it with NBU 5.x (group DSSUs in a SUG) It's a new fauture in 6.x Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, Jonathan Sent: August 2, 2007 12:51 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Question on Disk-as-Disk Targets NBU 5.1 MP5 Can I infer that there may be an issue with grouping disk-as-disk filesystems in a storage unit grouping with Netbackup 5.1? That'd be a huge concern of mine... Is anyone (other poor souls like me who can't afford a VTL) out there grouping disk-as-disk filesystems for primary backup
[Veritas-bu] User Backup to Windows-Flashbackup policy from the command line
Hi all, Here's a rather specific one... Trying to launch a Windows-Flashbackup job from the command line of a client (part of a much larger script that is not handled by Netbackup) Anyone ever tried the following from a Windows client? bpbackup -p user_backup_policy_name -s Full -t 13 -S master_name \\.\G:\MyServer Results in a filelist served up of: /\\./G:/MyServer Which of course, isn't the \\.\ format that Flashbackup wants. Ie: Netbackup isn't accepting my string as literal. Looks oddly perl-ish in fact... Just curious. Thanks, Jon This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] retentions
Ed, I 100% agree with what you've said below. For my traditional and small environment (only about 550 servers), what I've outlined is extremely useful, especially since it works for both Netbackup and Backup Exec clients in a similar manner. And no, a single report will never be able to get you all the information you need (for example, there a second NBU specific report that gets at least a little closer to giving accurate results on what you describe below in interpreting schedules and report on backup success, believe they call it client_sla_summary_report or something). These reports don't replace one of my major functions, which is to follow-up and design a lot of those said one-offs. I certainly wouldn't want to be without the reports though, now that I know the value of them. My single biggest concern is the interpretation of these reports, and being able to explain without a doubt why an entry is or isn't in them. Thanks for the comments Ed. Cheers, Jon -Original Message- From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 24, 2007 5:19 PM To: Dyck, Jonathan; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retentions This doesn't really address all of the issues. In order for this to work, you have to know what the schedule of the jobs are supposed to be. We've got a ton of backups that only run monthly and another ton that only run semi-annually. Unless I sit down with a calendar, telling when the last full backup was and comparing that to what it should be is not going to be trivial. What's important to know is not when the last backup was, but when the last backup was *supposed to be*. To do that, you need to dig into the scheduler and that is where it gets tough. For one client having a weekly full is supposed to be normal. For another, I may not try to back it for 6 months and that's perfectly normal. Reports like this are great if you have a simple environment and everybody does your standard daily/weekly/monthly style backups. Not everybody does their weekly fulls on a weekend and incremental during the week and calls it a day. Any backup software can do that. I've got similar issues with Aptare's projections for tape consumption. In our environment it's absolutely useless since it's based on the day of the week and not on the NetBackup schedules. If it really wanted to a fantastic job (hint, hint), dig into the policies and schedules, its own historical database, and realize that the 2TB backup I did 6 months ago will be done again. I've got about 100TB of storage on a semi-annual backup schedule. To be able to get accurate estimates of those jobs coming up would be sweet... Again, there's no point in telling me when the last backup was. What I want to know is if the backups are getting done when they're supposed to be done. This gets even more complicated when you've got multiple policies for the same client - something that in some cases you *have* to do. Backup reporting and auditing is hard. StorageConsole does a good job at what it's attempted to bite off but it could still get better. And yes, I realize that our environment is non-traditional and that sometimes we're just not going to get a solution unless we write it ourselves. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] I GoodSearch for Bundles Of Love: http://www.goodsearch.com/?charityid=821118 -Original Message- From: [EMAIL PROTECTED] [mailto:veritas-bu- [EMAIL PROTECTED] On Behalf Of Dyck, Jonathan Sent: Tuesday, July 24, 2007 2:37 PM To: Wayne T Smith; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retentions Just to chime in on the Aptare reports... They have an automated report (out of the box, but not really) you can cron/windows schedule to run that will give you the following details on full backups... (hope your screens large enough to make out the headings...). Great way to stop sys admins bugging you about last successful backups. LATEST FULL BACKUP LAST 60 DAYS CLIENT SERVER LAST FULL MBYTES FILES AVG MBYTES AVG FILES -- -- - -- - -- - With a little fiddling, you can get something that looks like the following all in one email... 1) Missing Backups (from last window any scheduled backup that has yet to run or has failed) 2) Last successful full backup attempt 3) Any skipped files during last backup Get the right person on a DL for an email, and you're laughing. Cheers, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne T Smith Sent: Friday, July 20, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retentions I, too, agree the 2-week retention should
Re: [Veritas-bu] retentions
Just to chime in on the Aptare reports... They have an automated report (out of the box, but not really) you can cron/windows schedule to run that will give you the following details on full backups... (hope your screens large enough to make out the headings...). Great way to stop sys admins bugging you about last successful backups. LATEST FULL BACKUP LAST 60 DAYS CLIENT SERVER LAST FULL MBYTES FILES AVG MBYTES AVG FILES -- -- - -- - -- - With a little fiddling, you can get something that looks like the following all in one email... 1) Missing Backups (from last window any scheduled backup that has yet to run or has failed) 2) Last successful full backup attempt 3) Any skipped files during last backup Get the right person on a DL for an email, and you're laughing. Cheers, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne T Smith Sent: Friday, July 20, 2007 12:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retentions I, too, agree the 2-week retention should be addressed ... quite risky. A few thoughts ... I recently tested Aptare StorageConsole and one of its out-of-the-box displays is close what you're looking for, I think. When we obtain a license, I'll be discarding many scripts ... one of which sort of applies here. The script looks at all full images for all clients and reports the most recent full backup for each client, ordered by oldest first. Look at the top of the list for clients in distress. This is simple and works great for clients with one image holding everything. It isn't nearly good enough for clients using multiple streams or clients that also have Exchange/Oracle/etc images in addition to file system images. I've started more than once to approximate proof we are successfully backing up at least what we intend. So far I have a bunch of failed attempts that would have worked for simple cases, but failed miserably in multitudes of ways. The best answer for us has always seemed to be getting accurate, succinct information in front of the eyes of someone who understands it and cares. But even that is not enough sometimes. Your idea of keeping the last full has promise, but you'll need a process to get rid of the images once you really don't want them ... plus, if your data is on tape, you'll probably require more media, as tape occupancy goes down due to the retention-extended images living alone. cheers, wayne Brandon Zermeno wrote, in part, on 2007-07-19 6:50 PM: We had an issue where was server was down for over 2 weeks and the last full backups expired. The retention for this environment is 2 weeks. After the tapes expired the App team decided they wanted to restore. Now management wants Veritas to extend the retention period automatically if a full is not successfully run. I do not know of any company that has this capability so I am looking for ideas. I do not think it would be possible for a person to manually track all the servers and their last full and then manually bpexpdate the images. I have pushed back with the question of why was this server allowed to be down for 2 weeks but nobody is answering. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] MSL 6062 tape library and HP LTO3 Tape Drives
I think this might help you out? http://www.microsoft.com/windowsserversystem/wss2003/techinfo/plandeploy /storportwp.mspx Cheers, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mkiles Sent: Monday, December 11, 2006 12:20 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] MSL 6062 tape library and HP LTO3 Tape Drives Just polling to see what is more prevalent in the field: Have a MSL 6062 with two N1200-320 cards, 4 LTO3 tape drives from HP. Have installed two A7388A HBA's (Basically Emulex LP1050). Do you use Storport driver for these HBAs or SCSI Miniport? And any specific settings? I have both HBAs direct connected to one N1200-320 card, but I see only one changer and 2 tape drives, cabling is done as per diagram in the N1200-320 config guide. Any thoughts? Thx Need a quick answer? Get one in minutes from people who know. Ask your question on www.Answers.yahoo.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disabling File list / size estimate on backups.
http://seer.support.veritas.com/docs/267253.htm ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Preston, Douglas L Sent: Wednesday, November 01, 2006 1:49 PM To: NB List Mail Subject: [Veritas-bu] Disabling File list / size estimate on backups. Is there a way to disable the file list estiimate for file number and size that happens before a backup begins? I have a NB 6.0 MP3 media server with approx 50 million files and 3 TB of disk. It is taking over 30 hours to back up the system, part of that 36 hours is file list building that takes over 11 hours on one of the drives and over 13 hours on one of the other drives. This makes daily backups impossible. If I can disable the estimates the backups should complete in less than 24 hours. I don't have a problem if the media server runs 24/7 backing up files. I just can't see it taking over 24 hours. Media server is backing up local fiber attached data drives. The media server is win2k3 server Netbackup Enterprise server 6.0 MP3 The library is an ADIC Scalar I2000 with 12 LTO2 drives and 700 slots. Drives and robot are fiber attached to the media server. Fiber zones are split. Data Drives use one zone. Library / Tape drives use a different zone. Doug Preston Systems Engineer Land America Tax and Flood Services Phone 626-339-5221 Ext 104 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, please delete it from your system without copying it, and notify the sender by reply e-mail, so that our address record can be corrected. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Johnson Sent: Wednesday, November 01, 2006 8:31 AM To: WEAVER, Simon; Martin, Jonathan (Contractor); NB List Mail Subject: Re: [Veritas-bu] Weard one As usual thanks all for the quick responses this is a great group to belong to. As for the storage unit question it sees all 4 drives. I set the max jobs from 1 to 99 on the master server this was how it was before I had problems a week ago some how got reset. I will try this and see what happens. I will recheck all of my settings one more time. Thanks Matthew Johnson Entertainment Partners Backup Administrator Work - 818-955-6357 Cell - 805-914-4791 From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 01, 2006 6:34 AM To: 'Martin, Jonathan (Contractor)'; Matthew Johnson; NB List Mail Subject: RE: [Veritas-bu] Weard one Have you set the max jobs to 99 for the master server ? Host properties of the master :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Martin, Jonathan (Contractor) [mailto:[EMAIL PROTECTED] Sent: 01 November 2006 13:51 To: Matthew Johnson; NB List Mail Subject: Re: [Veritas-bu] Weard one Have you checked your storage units? Are both policies set to write to the same storage unit, and thus to the same drive (assuming this is how you are configured?) Are both backups of the same server. I've had mixed results trying to run multiple policies on the same server at the same time. If you fire off policy #2 (the one not running now) and then Policy #1 does the same issue occur? -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Johnson Sent: Tuesday, October 31, 2006 4:30 PM To: NB List Mail Subject: [Veritas-bu] Weard one Hello all, I have a weird one I have two separate policies that start at the same time with 4 available drives. One starts writing and the other stays queued. They are both windows systems running through a windows media server with a Sun Solaris master. I am running NetBackup 5.1 mp5 TIA Matt Matthew Johnson Entertainment Partners Backup Administrator Work - 818-955-6357 Cell - 805-914-4791 Disclaimer - October 31, 2006 This email and any attachments are confidential and intended solely for NB List Mail. If you are not a named addressee you are prohibited from reviewing, printing, disseminating, distributing, copying or altering this email or any part of it. If you
Re: [Veritas-bu] CLOSE_WAIT
From the MS document... == TcpNumConnections Key: Tcpip\Parameters Value Type: REG_DWORD - Number Valid Range: 0 - 0xfe Default: 0xfe Description: This parameter limits the maximum number of connections that TCP may have open simultaneously. == I didn't implement this, but it might be something you'd want to bring up with support? I could have sworn that one of my architects here said W2k3 entreprise allows something huge like 60k TCP concurrent connections... I have absolutely nothing to back that up however, some expert out there PLEASE correct me! Cheers, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clooney, David Sent: Tuesday, October 31, 2006 4:33 AM To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] CLOSE_WAIT Thanks Simon Yeah, I had implemented the value to be brought down to 30 seconds which helped immediately. The problem we have now encountered is no longer with TIME_WAIT and now with CLOSE_WAIT. You don't perhaps know the default a windows 2k box is for max tcp connections. A little birdie has told me it is ten which at first thought seem to be very low. My thinking is increase the max number of open tcp sockets and alleviate the issue ??? Regards Dave -Original Message- From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: 31 October 2006 06:31 To: Clooney, David; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] CLOSE_WAIT David I have a Support Call open, in regards to Media errors, and the Symantec Engineer said the following. Simon, Tcp tuning parameters changes the wait time for a port which is in a TIME_WAIT state. A port will stay in this state for 4 minutes by default. Decreasing this time allows the port to be closed sooner rather than later allowing the port to be re-opened or stay as listening if need be. I noticed VMD (the volume manager daemon process) in TIME_WAIT state. If NetBackup VMD is timing out when trying to write to the next media or when trying to write header information, this could possibly cause problems. NOTE: For more information see Microsoft article # Q120642 at the following URL: TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT http://support.microsoft.com/default.aspx?scid=kb;en-us;120642 I think this is the same link Steve sent, but does any of this help answer your Q - For the record, I have NOT implemented this yet, as I have made one major change and want to review this before applying any other fix straight away (otherwise applying multiple fixes at the same time, means I have no trackable method of knowing what fixed the root problem). Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: 30 October 2006 10:44 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] CLOSE_WAIT Hi All Scenario : Master server Solaris 8 Media server windows 2000 Over the past weekend we encountered a whole bunch of 219's on jobs using a particular media server, a netstat on the media server provided the below snapshot. The CLOSE_WAIT entries seemed to hang around for ages, additionally hogging sockets. On the master server everything was plodding along as usual. Q1. can anyone explain why these sockets on the media server do not close fully and hang around for quite sometime ? If indeed the master server has not finalised comms, what (on the master) would be keeping the socket open between the two. Q2. Does anyone know the default setting for the maximum number of simultaneous tcp connections on windows 2000? Q3. If I was to add the registry key to tcp parameters TcpNumConnections , what guidelines could I follow to determine the number of connections ? Q4. Not so long ago on the same windows media server I added the registry key to tcp parameters TcpTimedWaitDelay in order to clear TIME_WAIT more quickly. Are there any known issues with windows 2000 and tcp connections that I'm not aware off ? Much appreciated David Clooney TCPmedia_server:bpcd media_server:795ESTABLISHED TCPmedia_server:bpcd media_server:834ESTABLISHED TCPmedia_server:bpcd media_server:868CLOSE_WAIT TCPmedia_server:bpcd media_server:991CLOSE_WAIT TCPmedia_server:bpcd master_server:551 CLOSE_WAIT TCPmedia_server:bpcd master_server:562 CLOSE_WAIT TCPmedia_server:bpcd master_server:591 CLOSE_WAIT TCPmedia_server:bpcd master_server:610 CLOSE_WAIT TCPmedia_server:bpcd master_server:645 CLOSE_WAIT TCPmedia_server:bpcd master_server:696 CLOSE_WAIT TCPmedia_server:bpcd master_server:768
Re: [Veritas-bu] CLOSE_WAIT
I'm also interested in this topic. My netstat -a looked the same as yours last week David. Last week I ran into an issue where (what I think was..) some security scans on my network for TCP traffic tied up a certain number of ports on my W2k3 master and some NBU processes were unable to interact reliably. Four levels of support were unable to suitably explain the problem to me, and all we ended up doing was throwing in a TCP wait delay into the registry, which worked with middling success. The issue has since disappeared (mysteriously) - as I assume whatever activity that was happening over those couple of days has since stopped. Cheers, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Clooney, David Sent: Monday, October 30, 2006 5:44 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] CLOSE_WAIT Hi All Scenario : Master server Solaris 8 Media server windows 2000 Over the past weekend we encountered a whole bunch of 219's on jobs using a particular media server, a netstat on the media server provided the below snapshot. The CLOSE_WAIT entries seemed to hang around for ages, additionally hogging sockets. On the master server everything was plodding along as usual. Q1. can anyone explain why these sockets on the media server do not close fully and hang around for quite sometime ? If indeed the master server has not finalised comms, what (on the master) would be keeping the socket open between the two. Q2. Does anyone know the default setting for the maximum number of simultaneous tcp connections on windows 2000? Q3. If I was to add the registry key to tcp parameters TcpNumConnections , what guidelines could I follow to determine the number of connections ? Q4. Not so long ago on the same windows media server I added the registry key to tcp parameters TcpTimedWaitDelay in order to clear TIME_WAIT more quickly. Are there any known issues with windows 2000 and tcp connections that I'm not aware off ? Much appreciated David Clooney TCPmedia_server:bpcd media_server:795ESTABLISHED TCPmedia_server:bpcd media_server:834ESTABLISHED TCPmedia_server:bpcd media_server:868CLOSE_WAIT TCPmedia_server:bpcd media_server:991CLOSE_WAIT TCPmedia_server:bpcd master_server:551 CLOSE_WAIT TCPmedia_server:bpcd master_server:562 CLOSE_WAIT TCPmedia_server:bpcd master_server:591 CLOSE_WAIT TCPmedia_server:bpcd master_server:610 CLOSE_WAIT TCPmedia_server:bpcd master_server:645 CLOSE_WAIT TCPmedia_server:bpcd master_server:696 CLOSE_WAIT TCPmedia_server:bpcd master_server:768 CLOSE_WAIT TCPmedia_server:bpcd master_server:807 CLOSE_WAIT TCPmedia_server:bpcd master_server:829 CLOSE_WAIT TCPmedia_server:bpcd master_server:830 CLOSE_WAIT TCPmedia_server:bpcd master_server:867 CLOSE_WAIT TCPmedia_server:bpcd master_server:904 CLOSE_WAIT TCPmedia_server:bpcd master_server:919 ESTABLISHED TCPmedia_server:bpcd master_server:976 ESTABLISHED TCPmedia_server:bpcd master_server:982 CLOSE_WAIT TCPmedia_server:bpcd master_server:1008 ESTABLISHED TCPmedia_server:bpcd master_server:1023 ESTABLISHED 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 message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist -
Re: [Veritas-bu] LTO3 Drivers - HP ESL
Title: Message Are the VERITAS drivers not working for you? I use 960's, and the 5.1 VERITAS driver is working just fine for me. Should be on any NBU 5.x install CD under "Additional Products" or somesuch. Let me know if you needs exacts... Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, SimonSent: Wednesday, October 25, 2006 12:25 PMTo: 'veritas-bu@mailman.eng.auburn.edu'Subject: [Veritas-bu] LTO3 Drivers - HP ESL Hi Guys Wonder if I could get some assistance? Have a HP ESL-322e Robotic Library using Ultrium 960 Drives I have a driver on them, but they are dated 2004 !! I cannot for the life of me find any NEW drivers for LTO3 Drives! Would anyone happen to have a link or possibly provide some help - I am still working on some odd issues within NBU, and drivers are the last resort. Thanks Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B23AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [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. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42
Thanks Dave. I've been pretty wary setting up my buffers in the environment, and haven't changed them for a few months, so I'm relatively confident they're not the issue. Backline support is scratching their heads at the moment... From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 24, 2006 4:55 AMTo: Dyck, Jonathan; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Couple of technotes regarding buffers, buffers are a delicate scenario , make sure your read the docs well and understand them before implementing. Also read the tuning performance guide Hope it helps Dave note : if NUMBER_DATA_BUFFERS_RESTORE is not implemented restores will use NUMBER_DATA_BUFFERS http://seer.entsupport.symantec.com/docs/183702.htm http://seer.support.veritas.com/docs/244652.htm From: Dyck, Jonathan [mailto:[EMAIL PROTECTED] Sent: 23 October 2006 17:19To: Clooney, David; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Yup, that brings up some interesting stuff... 11:59:48.246 [8168.6708] 2 logconnections: BPRD ACCEPT FROMx.x.x.x. TOx.x.x.x.x 11:59:48.246 [8168.6708] 2 process_request: setsockopt SO_LINGER on 280 succeeded. 11:59:48.246 [8168.6708] 2 connected_peer: Connection from hostX, x.x.x.x, on non-reserved port 4584 11:59:48.246 [8168.6708] 2 ParseConfigExA: Unknown configuration option on line 90: RenameIfExists = 0 11:59:48.246 [8168.6708] 2 nb_is_valid_master_server: checking ifmaster_server is a valid server 11:59:49.340 [8168.6708] 2 get_string: buffer space for 3072 bytes, but incoming data needs 218762506 bytes 11:59:49.340 [8168.6708] 2 get_string: (7) inadequate buffer space for data 11:59:49.355 [8168.6708] 32 process_request: get_string() failed - incoming data too large for buffer (0) 11:59:49.355 [8168.6708] 32 process_request: could not process request from master_server From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: Monday, October 23, 2006 12:01 PMTo: Dyck, Jonathan; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Agreed , keep a tail on your bprd log on the master to see whats happening at time of restore request.. Possible number of allowed tcp connections limitation. Dave From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, JonathanSent: 23 October 2006 15:58To: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Hmm, seems port 13720 isn't accepting connections... now to figure out why. Anyone have any advice? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, JonathanSent: Monday, October 23, 2006 7:40 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Hi all, Since hardware support and Veritas support seem to be getting nowhere on my problem, thought I'd hit the DL up to see if anyone's run into this problem before. Here's the environment: 1 Wintel Master, 3 Wintel +3 Solaris media servers(5.1 MP5) SSO, all LTO3 drives visible to all master/media, a single HP ESL712e No firewalls set up between any of these Here's the problem: Catalog is fully browsable. Backups can be queued manually or scheduled, and run fine in the environment. When submitting a restore (from either a workstation or straight from the master itself, both of which worked perfectly fine up until now, and no changes have been made in the environment), the GUI hangs up, takes over 10 minutes to submit, and report back asking that the restore has been submitting successfully and if I want to see its progress. At this point the restore appears in the Activity Monitor and stays in a queued state (for sometimes up to 30 minutes) and then reports back with an SC 42 (network read failed). I've checked my hardware, switch, application and system logs, and nothing really stands out. Probably something out there buried in my Veritas logs, but support hasn't been able to tell me anything in over 3 days now (plus a weekend). Any insight out there? I'd appreciate it! Thanks, Jon This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. 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
[Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42
Hi all, Since hardware support and Veritas support seem to be getting nowhere on my problem, thought I'd hit the DL up to see if anyone's run into this problem before. Here's the environment: 1 Wintel Master, 3 Wintel +3 Solaris media servers(5.1 MP5) SSO, all LTO3 drives visible to all master/media, a single HP ESL712e No firewalls set up between any of these Here's the problem: Catalog is fully browsable. Backups can be queued manually or scheduled, and run fine in the environment. When submitting a restore (from either a workstation or straight from the master itself, both of which worked perfectly fine up until now, and no changes have been made in the environment), the GUI hangs up, takes over 10 minutes to submit, and report back asking that the restore has been submitting successfully and if I want to see its progress. At this point the restore appears in the Activity Monitor and stays in a queued state (for sometimes up to 30 minutes) and then reports back with an SC 42 (network read failed). I've checked my hardware, switch, application and system logs, and nothing really stands out. Probably something out there buried in my Veritas logs, but support hasn't been able to tell me anything in over 3 days now (plus a weekend). Any insight out there? I'd appreciate it! Thanks, Jon This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42
Hmm, seems port 13720 isn't accepting connections... now to figure out why. Anyone have any advice? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, JonathanSent: Monday, October 23, 2006 7:40 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Hi all, Since hardware support and Veritas support seem to be getting nowhere on my problem, thought I'd hit the DL up to see if anyone's run into this problem before. Here's the environment: 1 Wintel Master, 3 Wintel +3 Solaris media servers(5.1 MP5) SSO, all LTO3 drives visible to all master/media, a single HP ESL712e No firewalls set up between any of these Here's the problem: Catalog is fully browsable. Backups can be queued manually or scheduled, and run fine in the environment. When submitting a restore (from either a workstation or straight from the master itself, both of which worked perfectly fine up until now, and no changes have been made in the environment), the GUI hangs up, takes over 10 minutes to submit, and report back asking that the restore has been submitting successfully and if I want to see its progress. At this point the restore appears in the Activity Monitor and stays in a queued state (for sometimes up to 30 minutes) and then reports back with an SC 42 (network read failed). I've checked my hardware, switch, application and system logs, and nothing really stands out. Probably something out there buried in my Veritas logs, but support hasn't been able to tell me anything in over 3 days now (plus a weekend). Any insight out there? I'd appreciate it! Thanks, Jon This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42
Yup, that brings up some interesting stuff... 11:59:48.246 [8168.6708] 2 logconnections: BPRD ACCEPT FROMx.x.x.x. TOx.x.x.x.x 11:59:48.246 [8168.6708] 2 process_request: setsockopt SO_LINGER on 280 succeeded. 11:59:48.246 [8168.6708] 2 connected_peer: Connection from hostX, x.x.x.x, on non-reserved port 4584 11:59:48.246 [8168.6708] 2 ParseConfigExA: Unknown configuration option on line 90: RenameIfExists = 0 11:59:48.246 [8168.6708] 2 nb_is_valid_master_server: checking ifmaster_server is a valid server 11:59:49.340 [8168.6708] 2 get_string: buffer space for 3072 bytes, but incoming data needs 218762506 bytes 11:59:49.340 [8168.6708] 2 get_string: (7) inadequate buffer space for data 11:59:49.355 [8168.6708] 32 process_request: get_string() failed - incoming data too large for buffer (0) 11:59:49.355 [8168.6708] 32 process_request: could not process request from master_server From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: Monday, October 23, 2006 12:01 PMTo: Dyck, Jonathan; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Agreed , keep a tail on your bprd log on the master to see whats happening at time of restore request.. Possible number of allowed tcp connections limitation. Dave From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, JonathanSent: 23 October 2006 15:58To: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Hmm, seems port 13720 isn't accepting connections... now to figure out why. Anyone have any advice? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, JonathanSent: Monday, October 23, 2006 7:40 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NetBackup 5.1 MP5 restore failures: SC 42 Hi all, Since hardware support and Veritas support seem to be getting nowhere on my problem, thought I'd hit the DL up to see if anyone's run into this problem before. Here's the environment: 1 Wintel Master, 3 Wintel +3 Solaris media servers(5.1 MP5) SSO, all LTO3 drives visible to all master/media, a single HP ESL712e No firewalls set up between any of these Here's the problem: Catalog is fully browsable. Backups can be queued manually or scheduled, and run fine in the environment. When submitting a restore (from either a workstation or straight from the master itself, both of which worked perfectly fine up until now, and no changes have been made in the environment), the GUI hangs up, takes over 10 minutes to submit, and report back asking that the restore has been submitting successfully and if I want to see its progress. At this point the restore appears in the Activity Monitor and stays in a queued state (for sometimes up to 30 minutes) and then reports back with an SC 42 (network read failed). I've checked my hardware, switch, application and system logs, and nothing really stands out. Probably something out there buried in my Veritas logs, but support hasn't been able to tell me anything in over 3 days now (plus a weekend). Any insight out there? I'd appreciate it! Thanks, Jon This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. 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
Re: [Veritas-bu] Monitoring for Locked jobs
Title: Scalix message content Phil, I run into this kind of thing once in awhile, although I typically see hung jobs in a "mounting" state if there's a problem, and for some reason my media mount timeout doesn't kill the job. Did you experience something similar? One way to go about scripting a job would be to "bpdbjobs -report" and grep on "Mounting". You can get a elapsed time from the report too, and using that time, you should be able to page out based on your threshold. Just my thoughts... Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of "Koster, Phil"Sent: Tuesday, September 26, 2006 7:55 AMTo: veritas-buSubject: [Veritas-bu] Monitoring for Locked jobs NBU 6 MP2 on Win2K Srvr. Over the weekend, all our jobs locked up on the back up server essentially stopping all backups beginning around 9 AM Saturday. All NBU processes (Windows) continued to run normally which did not allow our Nagios Monitoring system to notify us (it all seemed just fine). So my question is, is there anything we can monitor, even if by manual script, to let us know when jobs get hung? Can we do like a bpdbjobs and see how long the jobs have been running and use a script to evaluate that information? Anyone doing something like that already? What I am thinking is at the very least just get something that can monitor the jobs automatically (like a once per hour check) and if the jobs get over x hours active then it sends some e-mails out to our cell phones and inboxes. I tried to play around with bpdbjobs last night but ran out of time before our back ups finished. (Took to long getting the kids to bed ;-) Thanks. Phil KosterNetwork AdministratorCity of Grand RapidsDirect: 616-456-3136Helpdesk: 456-3999 * This message has been prepared on resources owned by the City of Grand Rapids, MI. It is subject to the Acceptable Use Policy and Procedures of the City of Grand Rapids. The information contained herein is confidential and is intended solely for the addressee. Access by any other party is unauthorized without the express written permission of the sender. If you are not the intended recipient, please contact the sender and delete this message. * This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Monitoring for Locked jobs
Title: Scalix message content I hear ya Phil. Can't count the number oftimes @ 2AM I'vecursed doing my "due diligence" on data collectionin the event of a failure, but sometimes it even helps :) Here's the quote straight from my support (I asked them the same question awhile ago) on the bpdbjobs command, you can customize to yourown needs with BPDBJOB_COLDEFS... I run all my scripts on a Solaris box, maybe someone else on this DL can fill you in on the Windows equivalent... Cheers, Jon == Yes, thats correct. If you want to have the Operation column displayed when executing bpdbjobs command then you can add the setting BPDBJOB_COLDEFS = Operation 12 true in the bp.conf. However, you will only get the output for Operation column when you execute the bpdbjobs command. To have specific columns output for bpdbjobs, youd need to add multiple BPDBJOB_COLDEFS entries in the bp.conf. For detailed use of BPDBJOB_COLDEFS, please refer to the technote http://support.veritas.com/docs/266314 If you dont want to use the BPDBJOB_COLDEFS settings in the bp.conf you can reference the text file attached, which deciphering all the fields/columns for different outputs of bpdbjobs command. You can then use it in the script to spit out whatever fields/columns you want.== From: "Koster, Phil" [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 10:12 AMTo: Dyck, Jonathan; veritas-buSubject: RE: [Veritas-bu] Monitoring for Locked jobs According to the report logs we got a "bad image header" and a "could not build host list" error right around the same time it locked up. Not to say it wasn't a mounting problem but our primary interest was getting things running again so we did not take enough care in documenting the state we found the server in. What status's will a bpdbjobs show? When I look in the Windows Command reference I only see: field3 = state (0=queued, 1=active, 2=waiting for retry, 3=done) The rest don't provide definitions with the potential responses (like a -all_columns or a -most_columns). I suppose we could do a bpdbjobs -all_columns and look for a state (field 3)of 1 or 2 and then look at the elapsed time (field 10). But is there a better field then the "state" field or is state just as useful for this as any other field? In 20/20 hindsight we would have been better off with a forensic quality investigationinstead of a rapid recovery style response. It was one of those split second decisions based on the fear of the status of our back ups. (Back ups arehigh profile around here. Last yearwe had a NAS devicedouble fault on a RAID 5and the back ups were bad, one week and $36,000 later we had only recovered about 60% of the ~500 GB of data. Ever since then). Thanks. Phil Koster Network Administrator City of Grand Rapids Direct: 616-456-3136 Helpdesk: 456-3999 From: Dyck, Jonathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 9:08 AMTo: Koster, Phil; veritas-buSubject: RE: [Veritas-bu] Monitoring for Locked jobs Phil, I run into this kind of thing once in awhile, although I typically see hung jobs in a "mounting" state if there's a problem, and for some reason my media mount timeout doesn't kill the job. Did you experience something similar? One way to go about scripting a job would be to "bpdbjobs -report" and grep on "Mounting". You can get a elapsed time from the report too, and using that time, you should be able to page out based on your threshold. Just my thoughts... Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of "Koster, Phil"Sent: Tuesday, September 26, 2006 7:55 AMTo: veritas-buSubject: [Veritas-bu] Monitoring for Locked jobs NBU 6 MP2 on Win2K Srvr. Over the weekend, all our jobs locked up on the back up server essentially stopping all backups beginning around 9 AM Saturday. All NBU processes (Windows) continued to run normally which did not allow our Nagios Monitoring system to notify us (it all seemed just fine). So my question is, is there anything we can monitor, even if by manual script, to let us know when jobs get hung? Can we do like a bpdbjobs and see how long the jobs have been running and use a script to evaluate that information? Anyone doing something like that already? What I am thinking is at the very least just get something that can monitor the jobs automatically (like a once per hour check) and if the jobs get over x hours active then it sends some e-mails out to our cell phones and inboxes. I tried to play around with bpdbjobs last night but ran out of time before our back ups finished. (Took to long getting the kids to bed ;-) Thanks. Phil KosterNetwork AdministratorCity of Grand RapidsDirect: 616-456-3136Helpdesk: 456-3999 ***
Re: [Veritas-bu] Monitoring for Locked jobs
Title: Scalix message content Bah! See? All you Windows users should bail, and get a real OS ;-) (this coming from a guy who's just put in a new Windows master and Windows media server) Sorry Phil. Guess I was just wasting your time. On a different thread, there are some definite benefits of having mixed masters in an environment with mixed clients... Don't really have the time to speak to them, but there ya go. Cheers,Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob StumpSent: Wednesday, September 27, 2006 10:58 AMTo: Phil Koster; Dyck, Jonathan; veritas-buSubject: Re: [Veritas-bu] Monitoring for Locked jobs Ain't no windows equivalent. "Dyck, Jonathan" [EMAIL PROTECTED] 9/27/2006 10:47 AM I hear ya Phil. Can't count the number oftimes @ 2AM I'vecursed doing my "due diligence" on data collectionin the event of a failure, but sometimes it even helps :) Here's the quote straight from my support (I asked them the same question awhile ago) on the bpdbjobs command, you can customize to yourown needs with BPDBJOB_COLDEFS... I run all my scripts on a Solaris box, maybe someone else on this DL can fill you in on the Windows equivalent... Cheers, Jon == Yes, thats correct. If you want to have the Operation column displayed when executing bpdbjobs command then you can add the setting BPDBJOB_COLDEFS = Operation 12 true in the bp.conf. However, you will only get the output for Operation column when you execute the bpdbjobs command. To have specific columns output for bpdbjobs, youd need to add multiple BPDBJOB_COLDEFS entries in the bp.conf. For detailed use of BPDBJOB_COLDEFS, please refer to the technote http://support.veritas.com/docs/266314 If you dont want to use the BPDBJOB_COLDEFS settings in the bp.conf you can reference the text file attached, which deciphering all the fields/columns for different outputs of bpdbjobs command. You can then use it in the script to spit out whatever fields/columns you want.== From: "Koster, Phil" [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 10:12 AMTo: Dyck, Jonathan; veritas-buSubject: RE: [Veritas-bu] Monitoring for Locked jobs According to the report logs we got a "bad image header" and a "could not build host list" error right around the same time it locked up. Not to say it wasn't a mounting problem but our primary interest was getting things running again so we did not take enough care in documenting the state we found the server in. What status's will a bpdbjobs show? When I look in the Windows Command reference I only see: field3 = state (0=queued, 1=active, 2=waiting for retry, 3=done) The rest don't provide definitions with the potential responses (like a -all_columns or a -most_columns). I suppose we could do a bpdbjobs -all_columns and look for a state (field 3)of 1 or 2 and then look at the elapsed time (field 10). But is there a better field then the "state" field or is state just as useful for this as any other field? In 20/20 hindsight we would have been better off with a forensic quality investigationinstead of a rapid recovery style response. It was one of those split second decisions based on the fear of the status of our back ups. (Back ups arehigh profile around here. Last yearwe had a NAS devicedouble fault on a RAID 5and the back ups were bad, one week and $36,000 later we had only recovered about 60% of the ~500 GB of data. Ever since then). Thanks. Phil Koster Network Administrator City of Grand Rapids Direct: 616-456-3136 Helpdesk: 456-3999 From: Dyck, Jonathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 27, 2006 9:08 AMTo: Koster, Phil; veritas-buSubject: RE: [Veritas-bu] Monitoring for Locked jobs Phil, I run into this kind of thing once in awhile, although I typically see hung jobs in a "mounting" state if there's a problem, and for some reason my media mount timeout doesn't kill the job. Did you experience something similar? One way to go about scripting a job would be to "bpdbjobs -report" and grep on "Mounting". You can get a elapsed time from the report too, and using that time, you should be able to page out based on your threshold. Just my thoughts... Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of "Koster, Phil"Sent: Tuesday, September 26, 2006 7:55 AMTo: veritas-buSubject: [Veritas-bu] Monitoring for Locked jobs NBU 6 MP2 on Win2K Srvr. Over the weekend, all our jobs locked up on the back up server essentially stopping all backups beginning around 9 AM Saturday. All NBU processes (Windows) continued to run normally which did not allow our Nagios Monitoring system to notify us (it all seemed just fine). So my question is, is there anything we can monitor, even if by manual script, to let us know when jobs get hung?
Re: [Veritas-bu] LTO3 throughput on Vault/Duplication jobs
Title: Message Agreed. Coming from an environment where we are "afraid" of multiplexing everything due to those image's importability (or lack thereof), the fact that we cannot demux quick enough has us handcuffed a little. Just a question, what's the rationale on mpx'ing to your VTL's? Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Tuesday, September 19, 2006 8:50 AMTo: Liddle, Stuart; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] LTO3 throughput on Vault/Duplication jobs It's not fishyyour problem is the demultiplexing.no question. you want to be reading one "virtual tape" and writing to one "physical tape".when you're finished reading that virtual tape, you load another and keep going. In your case, you're loading a virtual tape, reading 256k, skipping ahead on the disk abit, reading another 256k, skipping ahead somemore, etc, etc, and then reassembling that and writing it to a tape...in the mean time, you probably have another job that's jumping in between those 256k blocks and trying to get some different blocks to write to a different tape...I believe the docs even warn that this will cause poor duplication performance. instead of shooting from VTL to tape, you' have several jobspulling little bits from all over your VTL, then reassembling them and trying to write them to different tapes..a NIGHTMARE wrt performance. Either use the "preserve multiplexing" option, which will do a straight dupe, without all the sourcing and assemblingor..create more virtual drives on the VTL, and don't multiplex you original backups for example: if you have 4 virtual drives, and MPX=4, instead create 16 virtual drives, and turn MPX off. you're actually having to read 100MB/s off the VTL to get enough data to assemble into a 11MB/s stream for your tapes. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liddle, StuartSent: September 18, 2006 9:08 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] LTO3 throughput on Vault/Duplication jobs ALL, we have an issue with LTO-3 drive performance. Our environment is set up as follows: q a single master server running Solaris q 4 Linux media servers q 4 Windows media servers q ADIC i-2000 tape library with 16 LTO-3 drives that are shared on a SAN to all of the media servers with SSO q five NetApp VTLs that have multiple virtual libraries on each one. Each media server is connected to two virtual libraries (also over the SAN) We do all of our backups to the VTLs and are using Vault to make duplicate copies to the physical tapes. We are multiplexing to the VTLs and then de-multiplexing to the physical tapes. We are currently seeing only about 11MB/sec going out to the physical tapes. However, our read performance on the dups is averaging about 80 100+ MB/sec from the VTLs. Is anyone else doing something like this and are you getting better throughput to your physical tapes using Vault? Symantec told us today that doing a single-stream to the physical LTO-3 drives was only going to do about 8 or 9MB/sec and we should Preserve Multiplexing for the output in order to get better throughput to the physical tapes. Does this sound right? Its sounding kind of fishy to me. We have our buffers set as follows: NUMBER_DATA_BUFFERS: 128 SIZE_DATA_BUFFERS: 262144 thanks --stuart This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup and VMWare Licencing
FYI (here's what I got straight from the monkey's mouth... ;-)
Maybe this clears something up? Haven't been following this thread
really...
Cheers,
J _D_
{Paul, I shed the JR when the old man retired ;)
==
MULTIPLE DOMAIN OR VIRTUAL MACHINE SYSTEMS
NetBackup components (servers, clients, and database agents) for UNIX,
Windows, NetWare, and Linux are each licensed
once per physical machine. If a physical machine runs multiple Operating
Systems and Databases, then the physical machine
requires one NetBackup component for each Operating System and Database
type. Please note that this policy supersedes
previous licensing policies that were communicated before the date of
this document.
Exception: NetBackup Clients installed on IBM zSeries (OS/390) should be
licensed once per virtual machine. This is an
exception to the standard NetBackup policy of licensing clients once per
physical machine.
==
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul
Keating
Sent: Tuesday, September 19, 2006 11:57 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Netbackup and VMWare Licencing
We were as Scott.
Each client *TYPE* needs a license
As Scott said, if you have 5 NetWare, 5 Windows and 5 Linux, you need a
license per OS type
I didn't think it was limited to 5 though...I was under the impression
for a given host, you need one license for the host, then 1 license PER
client TYPE.
Ie, a vmware ESX host running linux with 10 linux VMs running would be 2
linux licenses.
A vmware ESX host running linux with 10 windows VMs would be 1 linux and
1 windows, etc,
Paul
--
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bobby
Williams
Sent: September 19, 2006 11:43 AM
To: Scott Jacobson; veritas-bu@mailman.eng.auburn.edu; Hampus Lind
Subject: Re: [Veritas-bu] Netbackup and VMWare Licencing
That is not what I infer from the support matrix (5.X)
http://ftp.support.veritas.com/pub/support/products/NetBackup_
Enterprise_Server/263839.pdf
It indicates that the VM host needs a license and each client needs a
license.
If you have something that shows this better than the support matrix,
please let us know. We are way over purchasing licenses if you are
correct.
Bobby.
This message may contain privileged and/or confidential information. If
you have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any attachments,
delete it immediately from your system and notify the sender promptly by e-mail
that you have done so. Thank you.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Flashbackup and Database clients
Title: Message Agreed. I implemented a Flashbackup policy for a server with 10M files (30 raw disk streams, 1.4 TB) this past weekend (using the copy-on-write method), and itsaved me exactly 0 drive hours in the tape drive bank :) Write speeds were roughly 30-50% faster, but the extra data made up for the savings. We run at about 60-70% usage, and were hoping to get away with not having to divvy up the server into two categories: which filesystems to back up with Flashbackup, and which not to.Looks like the problem is that the file to block mapping just takes too @*#$ long. Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul KeatingSent: Monday, September 11, 2006 10:23 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Flashbackup and Database clients AND your filesystem is "mostly" used. ie, you wouldn't want to use flashbackup on a 1TB filesystem that only has 100Gig of data on it. Paul -- -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shyam HazariSent: September 11, 2006 9:38 AMTo: [EMAIL PROTECTED]Cc: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Flashbackup and Database clients Flashbackups will help if you havemillions of small files. -Shyam On 9/11/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: will flashbackup help speedup my lotus notes database agent backups? ___Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU 5.1 MP5 Flashbackup using nbu_snap
Title: Message Thanks Phil, I'd given up on hearing a response on this one. From the list of gotchas you provided, I should be aok. I've asked the same question to Symantec, and they replied with a "I'll get back to you" about a week ago. Ie: not the kind of response you want to show management when you're trying to convince them we should be changing the way we do something... Cheers, Jon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Weber, PhilipSent: Tuesday, September 05, 2006 11:04 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NBU 5.1 MP5 Flashbackup using nbu_snap We're using advanced client for offhost backups, using nbu_snap (using the media server as the data mover, not doing Flashbackup). Currently only on MP4, haven't got around to MP5 yet though it is supposed to include fixes for some of the issues we have had, namely : 1. Doesn't work properly with vnetd, so some traffic still attempts to go over random ports. A problem if you have a firewall between your media server and client. 2. Cache size was limited to 1 Tb (not sure why we found this, we're not using anything like this size cache now). 3. Filesystem size was limited to 2 Tb (may still be). 4. Backups were failing when files changed in size during the backup (rather than ending with a status code 1). I have found that occasionally the cache will not be cleared down if a backup fails, though haven't bottomed out exactly how it has to fail for this to be the case. So it may be worth writing some scripts to monitor the status of the cache snapshotted filesystems. So in your example, A, B and C should all run but sometimes if B fails it won't clear up properly ... and if the cache is then not empty enough for C, it will also fail. It should start, because as I understand it the cache is only used as changes are made to the original filesystem. cheers, Phil -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dyck, JonathanSent: 28 August 2006 15:17To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NBU 5.1 MP5 Flashbackup using nbu_snap All, Anyone have any "gotchas" to report using block level, copy-on-write backups using the nbu_snap (Solaris only)method with NBU 5.1 MP5's Advanced Client? I'm getting closer to implementation time here, and my biggest concern is the cache size at the moment. One thing I'm concerned about is using a single job to back up all raw disk devices on the system.In the event of a full cache and subsequent failed backup on a particular stream, can anyone confirm that the cache will clear prior to the next stream in the file list for the job? Or does the job have to be restarted completely? Here's the scenario... Job list is: /dev/rdsk/A /dev/rdsk/B /dev/rdsk/C Where A is successful, B fills up the cache and craps out. Does C start? Thanks, Jon (in an environment where I can't just plug in a cache that's as big as my largest disk unfortunately) This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. Egg is a trading name of the Egg group of companies which includes:Egg plc (reg no2448340), Egg Financial Intermediation Ltd (reg no 3828289), and Egg Banking plc (reg no 2999842). Egg Banking plc and Egg Financial Intermediation Ltd are authorised and regulated by the Financial Services Authority (FSA) and are entered in the FSA register under numbers 205621 and 309551 respectively. These members of the Egg group are registered in England and Wales. Registered office: 1 Waterhouse Square, 138-142 Holborn, London EC1N 2NA.This e-mail is confidential and for use by the addressee only. If you are not the intended recipient of this e-mail and have received it in error, please return the message to the sender by replying to it and then delete it from your mailbox. Internet e-mails are not necessarily secure. The Egg group of companies do not accept responsibility for changes made to this message after it was sent.Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by the Egg group of companies in this regard and the recipient should carry out such virus and other checks as it considers appropriate.This communication does not create or modify any contract. ___ Veritas-bu maillist -
[Veritas-bu] NBU 5.1 MP5 Flashbackup using nbu_snap
All, Anyone have any "gotchas" to report using block level, copy-on-write backups using the nbu_snap (Solaris only)method with NBU 5.1 MP5's Advanced Client? I'm getting closer to implementation time here, and my biggest concern is the cache size at the moment. One thing I'm concerned about is using a single job to back up all raw disk devices on the system.In the event of a full cache and subsequent failed backup on a particular stream, can anyone confirm that the cache will clear prior to the next stream in the file list for the job? Or does the job have to be restarted completely? Here's the scenario... Job list is: /dev/rdsk/A /dev/rdsk/B /dev/rdsk/C Where A is successful, B fills up the cache and craps out. Does C start? Thanks, Jon (in an environment where I can't just plug in a cache that's as big as my largest disk unfortunately) This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VTL images to tape
Sounds like Greg and the some of the rest of the the mailing list are likely talking about two different products here... Symantec Enterprise Vault now has a feature to migrate data to disk/tape etc that was backed up with Netbackup 5.1+ Vault, the add-on to Netbackup can dupe from VLT to tape... Or maybe not... Just an inkling ;-) Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hindle, Greg Sent: Tuesday, August 22, 2006 1:51 PM To: David Rock; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VTL images to tape Are you using enterprise vault to get your images off from the VTL to tape? This is what I am referring to. There is an option in enterprise vault that says vault the images and du0liacte them to tape. This option does not work if you are trying to vault from the VTL. You must use a script to get the images off the VTL. 6.5 will have this part (from what I have been told this obvious could change) added to the gui and it will work. Greg -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Rock Sent: Tuesday, August 22, 2006 1:36 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VTL images to tape * Liddle, Stuart [EMAIL PROTECTED] [2006-08-22 10:25]: Actually, the story I heard from Symantec/Veritas about the VTL support under 6.x is that it will allow for automatic expiration of the VTL images once they have been successfully duplicated to physical tape. That's similar to the current option in vault for images coming from a DSSU. Yes, that's one of our enhancement requests (like many others) because we use the VTL mostly for staging only and would really like a checkbox in vault like the one for DSUs to expire after X hours. -- David Rock [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Moving media from one master to another.
It's definitely possible, although it tends to be one of those things Veritas likes to hold in their back pocket for PS work (i.e: you probably won't find good documentation around on how to do it). I've recently had an NBU 5.1 MP4 catalog migrated from a Sol. 9 master to a new Windows master (which made it a little easier, as volume pools could be duplicated on the new master getting rid of the problem with the old volume pool id's). I also had a quote to merge my two masters into a single at one point... Cheers, Jon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon Sent: Monday, July 17, 2006 2:21 AM To: 'Jim Horalek'; Veritas-Bu Subject: Re: [Veritas-bu] Moving media from one master to another. Jim Not sure this is actually possible, because both masters would not be sharing the same Database, therefore would not know anything about the media id (that's my understanding). I would assume that the only possible cause of action is to import the tape or tapes into the master which will then populate its own internal database. Guys, help me out if I am wrong here Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Jim Horalek [mailto:[EMAIL PROTECTED] Sent: 13 July 2006 20:44 To: Veritas-Bu Subject: [Veritas-bu] Moving media from one master to another. Anyone know how to move media from on mastet to another master? Cavat old server is an Sgi(Unix) New server is Windows. Note: I'm not trying to keep the same hostname for the master. Bpmedia ?? NBU 5.0 Thanks. Jim ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS 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 This message may contain privileged and/or confidential information. If you have received this e-mail in error or are not the intended recipient, you may not use, copy, disseminate or distribute it; do not open any attachments, delete it immediately from your system and notify the sender promptly by e-mail that you have done so. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
