Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Hi Good thing you are holding off with the upgrade because of Data Domain. We did the upgrade and everthing worked ok except Data Domain backups. To make a long story short, the problem was on the Data Domain side and it all had to do with permissions - This is was fixed it for us, so let the Data Domain Guys confirm: This can be resolved by logging into the ddr and running the following CIFS commands as well as changing some services for NBU on the windows system running NBU. On the DDR's command line run these commands: cifs option set guestaccount sysadmin cifs option set guestok yes cifs disable cifs enable On the Windows system running NBU change these services to be run as the user doing the backups. Netbackup Remote Manager and Monitor Service Netbackup Client Service Symantec Private Branch Exchange Hope this helps another person upgrading with Data Domain in the environment. JR From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Thursday, March 13, 2008 3:28 PM To: Paul Keating; WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On the flip side - at this point Symantec probably has more experience in migrating 5.1 to 6.0 than 6.5. Not having used 6.5 I can't say what, if any, differences there might be in doing such an upgrade. Many are saying 6.5 is just a fix of 6.0 but I imagine there ARE some differences. I do know that following the advice on this list we were able to go to 6.0 without suffering a lot after the conversion. We did have to do an iterative process in running the utility to check, have Symantec analyze it, then run it again and have another analysis done etc... until we got a run that had nothing left to be corrected and it was only at that point we did the upgrade. We're holding off on 6.5 mainly because we recently implemented Data Domain and want to make sure we understand how that impacts us coming on the heels of the 6.0 upgrade (which we waited for until MP4). Those who opted to wait for 6.5 to upgrade now seem to be feeling the pain of that decision which I counseled against on this list back when that thread occurred. From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 8:34 AM To: WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Scott Does not sound too bad to me - well done. Can I just ask what is the size of the DB on the Master Server - its just so I can get an idea roughly how long my environent may take Thanks, Simon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Thursday, March 13, 2008 4:04 PM To: nbu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I've done two upgrades in the last two weeks, one Windows and one Linux Master. Pulling and working from several document sources had my desk looking like I was trying to cram for a test so I created an internal checklist in an attempt to consolidate everything I believed was needed for the upgrade. For DR purposes, use by other staff, and because Management loves documentation I spent more time than usual in creating this check list which is attached. My stagging upgrade environment: W2K 5.1 MP60A Master, 4 SuSE 9 SP3 Media Servers - 5.1 MP6, 1 P2000 and P3000 Library, Remote Media Host and SSO. Both upgrades went well, but each had caveats, here is the Windows upgrade summary: 1. Much preparation, including the on line and off line help from Symantec (see doc). 2. Windows upgrade ok, nbpushdata completed with soft errors (3 1/2 hrs for the push). 3. Linux upgrade ok, nbpushdata very fast. Only issue was with the media install times, using our own script, we changed that from 35 to 7 minutes (see doc). 4. Three Post upgrade issues with Windows, only one with Linux. I suggest one might review note #5 for the Linux post upgrade issue (see doc for all post upgrade issues and notes). My worst upgrade experience was from 4.x to 5.x which sounded similar in pain for those who went from 5.x to 6.0. All in all, this one went well and I'm more at ease about upgrading our other production systems later in April. I think Tony posted early about a Hot Backup problem with error code 800, we also encountered that problem, but in our case when we obtained the solution from Symantec we could no longer duplicate the error. That solution was: SOLUTION/WORKAROUND: Stopped services Renamed the SYNC file in Netbackup\db\config Started services Reconfigured Off-line catalog REFERENCE: Veritas NetBackup (tm) 6.5 Administrator's Guide for Windows, Volume 1 http://support.veritas.com/docs/290203 Page 278 As mentioned by others, I would highly recommend a fallback plan and use it as a test environment for a 6.5 pre-install to get an idea of what you'll run into when you upgrade your production systems. PLEASE, don't consider the attached anything more than my checklist based on my experience (here it comes), so the disclaimer is use at your own risk - I guarantee your experience will be different. Scott This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Hi Tony First, let me say that my comments were not aimed at you, it was purely a simple question. I am in the process of planning for my 6.5.1 upgrade, and the key point I haev focused on is reverting back. For example, I am planning for the following: 1) 2 x good catalog backups, one in the robot, the other in an alternative location 2) disk based catalog backup (so in total, 3 cat backups I can revert back from) 3) A snapshot image of the System PRIOR to any work being done on the Master Server 4) Secondary Image on a backup system Another consideration is a second server, built and configured as the live box, same parts, firmware ect and use this as a secondary backup plan. Sounds OTT? yes of course but like I mentioned, I am covering all angles. I recently attended a Symantec meeting and one of the discussions was the 5.1 to 6.5.1 upgrade, and it seems clear that Symantec have done everything possible to help people move off of 5.x and upgrade with very little trouble or problems. That is not to say it will go wrong (as in your case), but it seems to be a case of trying to prepare for everything you possibly can. And you could bet your dollar something unusual may well crop up. The procedure for rolling back.. well from the Master it would be uninstall the NEW version, reinstall the 5.1 software, and restore the catalog from backup. I would imagine that if you had media servers, it would be the same (ie: restore from catalog). Please could anyone correct me on this process, because for my plan of revert, its simply a case of going back to a snap shot image and I am done :-) Like I said, I do not have real world experience, but I am doing this all in a test lab - so I hope this goes someway to show I am doing some research. Thanks, Simon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Wednesday, March 12, 2008 3:50 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:42 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: Tony Quick Q - when you realised the problems, were you able to plan to REVERT the systems back ? Simon Revert back to 5.1? I realize now that there should have been a plan to do that; Symantec reccomended it after hours of going nowhere but the client didn't want to. And even if they did, what is the procedure for doing this? This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. maybe careful planning is the key? Careful planning is always key but this alone doesn't guarantee a successful outcome. Part of the planning, however, should include a fall back plan... .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. maybe careful planning is the key? Careful planning is always key but this alone doesn't guarantee a successful outcome. Part of the planning, however, should include a fall back plan... .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England 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
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
On the flip side - at this point Symantec probably has more experience in migrating 5.1 to 6.0 than 6.5. Not having used 6.5 I can't say what, if any, differences there might be in doing such an upgrade. Many are saying 6.5 is just a fix of 6.0 but I imagine there ARE some differences. I do know that following the advice on this list we were able to go to 6.0 without suffering a lot after the conversion. We did have to do an iterative process in running the utility to check, have Symantec analyze it, then run it again and have another analysis done etc... until we got a run that had nothing left to be corrected and it was only at that point we did the upgrade. We're holding off on 6.5 mainly because we recently implemented Data Domain and want to make sure we understand how that impacts us coming on the heels of the 6.0 upgrade (which we waited for until MP4). Those who opted to wait for 6.5 to upgrade now seem to be feeling the pain of that decision which I counseled against on this list back when that thread occurred. From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 8:34 AM To: WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. maybe careful planning is the key? Careful planning is always key but this alone doesn't guarantee
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
that may be, but I was simply pointing out that they have made much more of an effort to make the 5.1 to 6.5.x upgrade alot more smoother and reliable. (at least based on the conversations I had and documents I downloaded from the Portal). I have always held off the 6.0 upgrade, and even now I am going to focus on the jump to 6.5.1. Remember, I have never used 6.0, so I have no real experience - but one would hope Symantec Support does and have been involved in many migrations based on customers requirements. From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:34 PM To: WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. maybe careful planning is the key? Careful planning is always key but this alone doesn't guarantee a successful outcome. Part of the planning, however, should include a fall back plan... .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[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
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
That reminds me of joke where women said to the pope about birth controls: If you don't play the game, you don't make the rules. If you haven't even done 6.0 upgrade you don't really have a good grasp on how different it is. It is a lot worse than 4.5 to 5.1 for example. From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 9:37 AM To: Paul Keating; Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 that may be, but I was simply pointing out that they have made much more of an effort to make the 5.1 to 6.5.x upgrade alot more smoother and reliable. (at least based on the conversations I had and documents I downloaded from the Portal). I have always held off the 6.0 upgrade, and even now I am going to focus on the jump to 6.5.1. Remember, I have never used 6.0, so I have no real experience - but one would hope Symantec Support does and have been involved in many migrations based on customers requirements. From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:34 PM To: WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. maybe careful planning is the key? Careful planning is always
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Maybe, but its still go to be done :-) From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 1:47 PM To: WEAVER, Simon (external); Paul Keating; Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 That reminds me of joke where women said to the pope about birth controls: If you don't play the game, you don't make the rules. If you haven't even done 6.0 upgrade you don't really have a good grasp on how different it is. It is a lot worse than 4.5 to 5.1 for example. From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 9:37 AM To: Paul Keating; Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 that may be, but I was simply pointing out that they have made much more of an effort to make the 5.1 to 6.5.x upgrade alot more smoother and reliable. (at least based on the conversations I had and documents I downloaded from the Portal). I have always held off the 6.0 upgrade, and even now I am going to focus on the jump to 6.5.1. Remember, I have never used 6.0, so I have no real experience - but one would hope Symantec Support does and have been involved in many migrations based on customers requirements. From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:34 PM To: WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I've done two upgrades in the last two weeks, one Windows and one Linux Master. Pulling and working from several document sources had my desk looking like I was trying to cram for a test so I created an internal checklist in an attempt to consolidate everything I believed was needed for the upgrade. For DR purposes, use by other staff, and because Management loves documentation I spent more time than usual in creating this check list which is attached. My stagging upgrade environment: W2K 5.1 MP60A Master, 4 SuSE 9 SP3 Media Servers - 5.1 MP6, 1 P2000 and P3000 Library, Remote Media Host and SSO. Both upgrades went well, but each had caveats, here is the Windows upgrade summary: 1. Much preparation, including the on line and off line help from Symantec (see doc). 2. Windows upgrade ok, nbpushdata completed with soft errors (3 1/2 hrs for the push). 3. Linux upgrade ok, nbpushdata very fast. Only issue was with the media install times, using our own script, we changed that from 35 to 7 minutes (see doc). 4. Three Post upgrade issues with Windows, only one with Linux. I suggest one might review note #5 for the Linux post upgrade issue (see doc for all post upgrade issues and notes). My worst upgrade experience was from 4.x to 5.x which sounded similar in pain for those who went from 5.x to 6.0. All in all, this one went well and I'm more at ease about upgrading our other production systems later in April. I think Tony posted early about a Hot Backup problem with error code 800, we also encountered that problem, but in our case when we obtained the solution from Symantec we could no longer duplicate the error. That solution was: SOLUTION/WORKAROUND: Stopped services Renamed the SYNC file in Netbackup\db\config Started services Reconfigured Off-line catalog REFERENCE: Veritas NetBackup (tm) 6.5 Administrator's Guide for Windows, Volume 1 http://support.veritas.com/docs/290203 Page 278 As mentioned by others, I would highly recommend a fallback plan and use it as a test environment for a 6.5 pre-install to get an idea of what you'll run into when you upgrade your production systems. PLEASE, don't consider the attached anything more than my checklist based on my experience (here it comes), so the disclaimer is use at your own risk - I guarantee your experience will be different. Scott NBU 6.5.1 Internal Checklist.odt Description: application/vnd.oasis.opendocument.text ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I don't know that upgrading to 6.5 is any easier than going to 6.0. Granted there are some known issues in 6.0, but I think that's beside the point of this discussion. The main reason it's easier is because Symantec realized they dropped the ball after there were a high number of people having upgrade issues when going to 6.0. After that, they got it together and put out the documentation set. While the docs are much better than nothing, I still think they could have done a better job organizing the steps as some steps overlap and others contradict previous information. With that said, I have upgraded two environments to 6.5.0 from 5.1MP6 successfully. I owe this success to the docs and taking the time to following the steps (though as said, that's not a guarantee all will be well). The first upgrade ran into some minor snags, the second went well, and I have another one scheduled for next Wednesday. Here's hoping I didn't just jinx myself! -Rusty WEAVER, Simon \(external\) [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/13/2008 08:55 AM To Paul Keating [EMAIL PROTECTED], Ed Wilts [EMAIL PROTECTED] cc veritas-bu@mailman.eng.auburn.edu, Jeff Lightner [EMAIL PROTECTED] Subject Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 that may be, but I was simply pointing out that they have made much more of an effort to make the 5.1 to 6.5.x upgrade alot more smoother and reliable. (at least based on the conversations I had and documents I downloaded from the Portal). I have always held off the 6.0 upgrade, and even now I am going to focus on the jump to 6.5.1. Remember, I have never used 6.0, so I have no real experience - but one would hope Symantec Support does and have been involved in many migrations based on customers requirements. From: Paul Keating [mailto:[EMAIL PROTECTED] Sent: Thursday, March 13, 2008 12:34 PM To: WEAVER, Simon (external); Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: RE: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 I think what Ed is saying is that either way (6.0 or 6.5) you have to make the transition from the old flat file binary catalog to the new sybase/EMM. Therefore, 5.x - 6.0 or 5.x - 6.5 is no difference. What you're saying about an easier transition to 6.5 I believe is merely symantec providing the means to go direct to 6.5 rather than make an intermediate step at 6.0, where no one likely wants to stay. Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: March 13, 2008 3:50 AM To: Ed Wilts Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hello Ed I am basing this comment (as you detailed below) on a discussion with Symantec. that is not to say its right, but I know after the huge cock-ups there were with 6.x one of their focus points was an easier transition from 5.x to 6.5 or 6.5.1 Of course, alot would depend on the environment, and also the stability of that environment. I guess one small fault can cause an endless amount of headaches and quite possible downtime for your NetBackup environment. Having Symantec on the end of the phone could be a good thing depending on their expertise me thinks. In regards to the second comment (see below in blue), I did respond to this in another thread of the same subject line. Hopefully this is clear. Thanks, Simon From: Ed Wilts [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 12, 2008 4:56 PM To: WEAVER, Simon (external) Cc: Jeff Lightner; Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
We haven't gone to 6.5 but our upgrade from 5.1 to 6.0 MP4 was no where near as traumatic as you describe. Maybe it works better 5.1 -- 6.0 --6.5? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Tuesday, March 11, 2008 10:10 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Mon, Mar 10, 2008 at 3:46 PM, rascal [EMAIL PROTECTED] wrote: ok, so we found an interesting issue now with our upgrades. Right now our master/media server is experiencing issues with hot catalog backups (to tape). Here are some interesting, fun facts: 1. our master server is an aix box with multiple interfaces 2. its an upgrade from 5.1mp5 to 6.5.1 3. everything BUT catalog works just peachy 4. Error codes in include 252 (800), and 134. I have not seen that, but our upgrade is nothing short of a nightmare. We ran the NBCC tool again, and there was one error that we sent to support and they had us run a command to fix it. So we started the upgrade...*everything* took like an hour; after clicking setup, the status bar didnt move and just about the time we were going to give up it finished. Then the dreaded nbpushdata command produced an error. Sent that into support, after about 5 hours of back and forth running various commands nothing is working. NBU wont start, it generates all sorts of errors. Support finally said we should roll back to 5, but didn't tell us how. They said instead we could just patch it to 6.5.1. Well that had the predictable result of just hanging for an hour, then finally spitting back an error along the lines of Setup was interupted before it could finish What a comedy of errors this is...I don't even know where to begin, support had us run so many things that are not listed in their 20 page Upgrade Doc that I would not feel comfortable ever doing this again. In fact the next time I hear the word upgrade I am going to suggest getting new equipment, since NBU is obviously not stable enough to withstand an in place upgrade. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
not sure I would agree - it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. maybe careful planning is the key? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Wednesday, March 12, 2008 3:16 PM To: Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 We haven't gone to 6.5 but our upgrade from 5.1 to 6.0 MP4 was no where near as traumatic as you describe. Maybe it works better 5.1 -- 6.0 --6.5? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Tuesday, March 11, 2008 10:10 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Mon, Mar 10, 2008 at 3:46 PM, rascal [EMAIL PROTECTED] wrote: ok, so we found an interesting issue now with our upgrades. Right now our master/media server is experiencing issues with hot catalog backups (to tape). Here are some interesting, fun facts: 1. our master server is an aix box with multiple interfaces 2. its an upgrade from 5.1mp5 to 6.5.1 3. everything BUT catalog works just peachy 4. Error codes in include 252 (800), and 134. I have not seen that, but our upgrade is nothing short of a nightmare. We ran the NBCC tool again, and there was one error that we sent to support and they had us run a command to fix it. So we started the upgrade...*everything* took like an hour; after clicking setup, the status bar didnt move and just about the time we were going to give up it finished. Then the dreaded nbpushdata command produced an error. Sent that into support, after about 5 hours of back and forth running various commands nothing is working. NBU wont start, it generates all sorts of errors. Support finally said we should roll back to 5, but didn't tell us how. They said instead we could just patch it to 6.5.1. Well that had the predictable result of just hanging for an hour, then finally spitting back an error along the lines of Setup was interupted before it could finish What a comedy of errors this is...I don't even know where to begin, support had us run so many things that are not listed in their 20 page Upgrade Doc that I would not feel comfortable ever doing this again. In fact the next time I hear the word upgrade I am going to suggest getting new equipment, since NBU is obviously not stable enough to withstand an in place upgrade. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
On Wed, Mar 12, 2008 at 10:42 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: Tony Quick Q - when you realised the problems, were you able to plan to REVERT the systems back ? Simon Revert back to 5.1? I realize now that there should have been a plan to do that; Symantec reccomended it after hours of going nowhere but the client didn't want to. And even if they did, what is the procedure for doing this? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: *not sure I would agree - it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path.* *maybe careful planning is the key? * Honestly, I don't know how much more we could have planned/prepared. We went through the upgrade document at Symantec with a fine tooth comb; not one step was done flippantly, out of order or skipped. We ran the NBCC right before we started and had Symantec look at the output and address any inconsistencies, even got the go ahead from them that Your upgrade can now proceed. The problem was just about every step listed in that doc produced unexpected results; either the box would just sit there doing nothing, or it would come back with some error that was not addressed in the upgrade guide and had to be sent to Symantec. I will think twice about ever reccomending an in place upgrade again. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Tony Quick Q - when you realised the problems, were you able to plan to REVERT the systems back ? Simon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Wednesday, March 12, 2008 3:39 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: not sure I would agree - it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. maybe careful planning is the key? Honestly, I don't know how much more we could have planned/prepared. We went through the upgrade document at Symantec with a fine tooth comb; not one step was done flippantly, out of order or skipped. We ran the NBCC right before we started and had Symantec look at the output and address any inconsistencies, even got the go ahead from them that Your upgrade can now proceed. The problem was just about every step listed in that doc produced unexpected results; either the box would just sit there doing nothing, or it would come back with some error that was not addressed in the upgrade guide and had to be sent to Symantec. I will think twice about ever reccomending an in place upgrade again. This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I would say a full clean re-install of netbackup 5.1 and recover the cold catalog backup created before(right?) the initiation of the 6.0 upgrade Jared M. Seaton Recovery Administrator Mylan Inc. 304-554-5926 304-685-1389 (Cell) Tony T. [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/12/2008 11:55 AM To veritas-bu@mailman.eng.auburn.edu cc Subject Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:42 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: Tony Quick Q - when you realised the problems, were you able to plan to REVERT the systems back ? Simon Revert back to 5.1? I realize now that there should have been a plan to do that; Symantec reccomended it after hours of going nowhere but the client didn't want to. And even if they did, what is the procedure for doing this? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu == CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you. == ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: * it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path.* What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. * maybe careful planning is the key?* Careful planning is always key but this alone doesn't guarantee a successful outcome. Part of the planning, however, should include a fall back plan... .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
It would have been nice to have an upgrade option that allowed a new 6.5 environment to just import a 5.x config. I intend on doing a hardware refresh at the same time. Since I'm currently runnin 5.0 MP4, which isn't supported on Solaris 10, I'm looking at upgrading the exisitng env to 5.1 MP6, then building a new Solaris 10 env on new hardware, importing the 5.0 catalog, then upgrading the Sol10 env to 6.5.1 It would be much nicer to build the Sol 10 env with a fresh install of 6.5.1 and just import the 5.0 catalog. :o/ Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: March 12, 2008 12:56 PM To: WEAVER, Simon (external) Cc: veritas-bu@mailman.eng.auburn.edu; Jeff Lightner Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 On Wed, Mar 12, 2008 at 10:33 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: it seems that going from 5.1 to 6.5 or even 6.5.1 should be the easier upgrade path. What are you basing this on? The 6.0 to 6.5 upgrade has been relatively painless for everybody. It's always been the 5.x to 6.0 upgrade that has been the issue and the steps to do that are in the 5.1 to 6.5 path - you can't avoid the migration by skipping 6.0. In general, the uglier the source environment in 5.1, the uglier the migration, and it hasn't always been the admin's fault (although sometimes it has been). Some things worked in earlier releases but were never really documented or supported and NetBackup is not unique in this. The more complex the product is, the uglier upgrades are going to be since there are too many input permutations to even consider testing. There are lots of environments out there where Symantec just says we didn't know anybody was even doing *that* or we didn't even know you *could* do that. If the source environment would have been bugfree since it was installed, it would be easier, but it wasn't - all releases that I've worked on, going back to 3.4 had some set of bugs that would leave the system in weird and wonderful states. That makes the upgrade even harder since they can't just trust that the source system was pristine. It also doesn't help that sometimes the upgrade processes themselves have bugs. maybe careful planning is the key? Careful planning is always key but this alone doesn't guarantee a successful outcome. Part of the planning, however, should include a fall back plan... .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I sync'd our production NetBackup 5.1MP6 installation to a test server we have (normally used for DR) and upgraded that to 6.5, then patched to 6.5.1. Everything worked as documented, no problems were encountered other than one inconsitency that NBCC caught (there was a frozen tape with expired images on it that it complained about. We unfroze the tape, let the images expire, and it was fine after that). We have yet to upgrade our production environment, but we have a simple setup, one master server that is also the media server, so it's very straightforward. Rollback plan involves breaking the root disk's mirror and snapshotting the netbackup volume (which is ZFS). Any problems and we boot off the other side of the mirror and roll back the snapshot. However, if we've written to tapes since ugprading, it becomes a bit more difficult... Eric On Wed, Mar 12, 2008 at 10:42 AM, WEAVER, Simon (external) [EMAIL PROTECTED] wrote: Tony Quick Q - when you realised the problems, were you able to plan to REVERT the systems back ? Simon Revert back to 5.1? I realize now that there should have been a plan to do that; Symantec reccomended it after hours of going nowhere but the client didn't want to. And even if they did, what is the procedure for doing this? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu == CONFIDENTIALITY NOTICE: This e-mail message and all attachments transmitted with it may contain legally privileged, proprietary and/or confidential information intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution, duplication or other use of this message and/or its attachments is strictly prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and its attachments. Thank you. == ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
On Mon, Mar 10, 2008 at 3:46 PM, rascal [EMAIL PROTECTED] wrote: ok, so we found an interesting issue now with our upgrades. Right now our master/media server is experiencing issues with hot catalog backups (to tape). Here are some interesting, fun facts: 1. our master server is an aix box with multiple interfaces 2. its an upgrade from 5.1mp5 to 6.5.1 3. everything BUT catalog works just peachy 4. Error codes in include 252 (800), and 134. I have not seen that, but our upgrade is nothing short of a nightmare. We ran the NBCC tool again, and there was one error that we sent to support and they had us run a command to fix it. So we started the upgrade...*everything* took like an hour; after clicking setup, the status bar didnt move and just about the time we were going to give up it finished. Then the dreaded nbpushdata command produced an error. Sent that into support, after about 5 hours of back and forth running various commands nothing is working. NBU wont start, it generates all sorts of errors. Support finally said we should roll back to 5, but didn't tell us how. They said instead we could just patch it to 6.5.1. Well that had the predictable result of just hanging for an hour, then finally spitting back an error along the lines of Setup was interupted before it could finish What a comedy of errors this is...I don't even know where to begin, support had us run so many things that are not listed in their 20 page Upgrade Doc that I would not feel comfortable ever doing this again. In fact the next time I hear the word upgrade I am going to suggest getting new equipment, since NBU is obviously not stable enough to withstand an in place upgrade. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
ok, so we found an interesting issue now with our upgrades. Right now our master/media server is experiencing issues with hot catalog backups (to tape). Here are some interesting, fun facts: 1. our master server is an aix box with multiple interfaces 2. its an upgrade from 5.1mp5 to 6.5.1 3. everything BUT catalog works just peachy 4. Error codes in include 252 (800), and 134. Anyone have this problem out there? On Fri, Mar 7, 2008 at 10:31 AM, rascal [EMAIL PROTECTED] wrote: We are going through the upgrade process right now (5.1 to 6.5.1. on multiple servers/clients spanning aix5, solaris9/10, w2k3). So far we have run into a couple of hiccups: 1. DB inconsistency: Call Symantec!!! Save your sanity, lol! 2. If you have multiple interfaces that you are using (pub, private, backup, extra, etc...) keep an eye on this as this caused some issues with our configuration and forced us to rollback to 5.1 at one site to resolve (simply rebuilding the device base and re-inventory the library). 3. VxSS: nno issues thus far... 4. Catalog backup change: We noticed that the EMM becomes unavailable during a backup; anyone else see this or this part of the new approach that netbackup is taking with catalogs? Other than that, everything seems to be running good. Anyone else? On Thu, Mar 6, 2008 at 10:28 AM, Weber, Philip [EMAIL PROTECTED] wrote: We upgraded our environment a couple of weeks ago, from 5.1 to 6.5.1. Follow the instructions, and make sure you have a call open with Symantec well in advance so you can run all the database consistency checks and pass the results back and forth to Symantec to resolve any issues with media - we went through several cycles of this. This environment is Solaris 9 / Solaris 10 with 1 master and 4 media servers, 2 Spectralogic libraries with LTO2/LTO3 tapes encryption. Solaris Windows clients. Issues during the upgrade : - Still had problems with some LTO1 tapes imported from a previous environment. Easily resolved with a call to Symantec. - Couldn't automatically upgrade the Solaris clients without going to them all to create a symlink for gzip and gunzip, easily resolved but a bit naff. - Ongoing issues with Advanced Client where I can't get the snapctl driver to work at all (Solaris). See separate posting. thanks, Phil -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *WEAVER, Simon (external) *Sent:* 04 March 2008 15:35 *To:* Tony T.; veritas-bu@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x- 6.5 Id be interested to hear if anyone had a plan of action from any NBU upgrade - I will be doing 5.1 to 6.5.1 Si -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Tony T. *Sent:* Tuesday, March 04, 2008 3:32 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hi all, I am interested in hearing about any of the upgrades that you have done, mainly going from 5.x to 6.5 There seem to be quite a few environments (in my area) that are looking to upgrade, and I am putting together some documentation that asks questions to better prepare for it. I am still learning the ropes of NBU but I have a lot of experience with the server side of things especially Sun and AIX systems with SAN storage. I have the Symantec upgrade guide Upgrading to Veritas Netbackup 6.5 and it appears to be pretty detailed, but it just covers the steps to get from point A to point B. Some of the things I am interested in finding out: - is there anyway to estimate how long step X might take? I realize that there are so many variables that it is not possible to say popluating the EMM will take X hours but if enough people chime in on what their experience was like, maybe we can come up with an average - have there been any show stoppers that were unanticipated? We could all learn from this, knowing what questions to ask up front based on our past...er...challenges. NBU has so many options and is such a broad product that I doubt any two environments are identical. Just sort of brain storming here, looking forward to hearing (seeing?) what you all have to share. If we get a good dialog going I will attempt to compile it into something usable and post it back here. T. -- ) ( ) [_]) 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
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
We are going through the upgrade process right now (5.1 to 6.5.1. on multiple servers/clients spanning aix5, solaris9/10, w2k3). So far we have run into a couple of hiccups: 1. DB inconsistency: Call Symantec!!! Save your sanity, lol! 2. If you have multiple interfaces that you are using (pub, private, backup, extra, etc...) keep an eye on this as this caused some issues with our configuration and forced us to rollback to 5.1 at one site to resolve (simply rebuilding the device base and re-inventory the library). 3. VxSS: nno issues thus far... 4. Catalog backup change: We noticed that the EMM becomes unavailable during a backup; anyone else see this or this part of the new approach that netbackup is taking with catalogs? Other than that, everything seems to be running good. Anyone else? On Thu, Mar 6, 2008 at 10:28 AM, Weber, Philip [EMAIL PROTECTED] wrote: We upgraded our environment a couple of weeks ago, from 5.1 to 6.5.1. Follow the instructions, and make sure you have a call open with Symantec well in advance so you can run all the database consistency checks and pass the results back and forth to Symantec to resolve any issues with media - we went through several cycles of this. This environment is Solaris 9 / Solaris 10 with 1 master and 4 media servers, 2 Spectralogic libraries with LTO2/LTO3 tapes encryption. Solaris Windows clients. Issues during the upgrade : - Still had problems with some LTO1 tapes imported from a previous environment. Easily resolved with a call to Symantec. - Couldn't automatically upgrade the Solaris clients without going to them all to create a symlink for gzip and gunzip, easily resolved but a bit naff. - Ongoing issues with Advanced Client where I can't get the snapctl driver to work at all (Solaris). See separate posting. thanks, Phil -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *WEAVER, Simon (external) *Sent:* 04 March 2008 15:35 *To:* Tony T.; veritas-bu@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Id be interested to hear if anyone had a plan of action from any NBU upgrade - I will be doing 5.1 to 6.5.1 Si -- *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Tony T. *Sent:* Tuesday, March 04, 2008 3:32 PM *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hi all, I am interested in hearing about any of the upgrades that you have done, mainly going from 5.x to 6.5 There seem to be quite a few environments (in my area) that are looking to upgrade, and I am putting together some documentation that asks questions to better prepare for it. I am still learning the ropes of NBU but I have a lot of experience with the server side of things especially Sun and AIX systems with SAN storage. I have the Symantec upgrade guide Upgrading to Veritas Netbackup 6.5 and it appears to be pretty detailed, but it just covers the steps to get from point A to point B. Some of the things I am interested in finding out: - is there anyway to estimate how long step X might take? I realize that there are so many variables that it is not possible to say popluating the EMM will take X hours but if enough people chime in on what their experience was like, maybe we can come up with an average - have there been any show stoppers that were unanticipated? We could all learn from this, knowing what questions to ask up front based on our past...er...challenges. NBU has so many options and is such a broad product that I doubt any two environments are identical. Just sort of brain storming here, looking forward to hearing (seeing?) what you all have to share. If we get a good dialog going I will attempt to compile it into something usable and post it back here. T. -- ) ( ) [_]) This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England -- * Egg is a trading name of the Egg group of companies which includes: Egg Financial Intermediation Ltd (reg no 3828289) and Egg Banking plc (reg no 2999842). Egg Banking plc and Egg Financial Intermediation Ltd
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
Id be interested to hear if anyone had a plan of action from any NBU upgrade - I will be doing 5.1 to 6.5.1 Si From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Tuesday, March 04, 2008 3:32 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hi all, I am interested in hearing about any of the upgrades that you have done, mainly going from 5.x to 6.5 There seem to be quite a few environments (in my area) that are looking to upgrade, and I am putting together some documentation that asks questions to better prepare for it. I am still learning the ropes of NBU but I have a lot of experience with the server side of things especially Sun and AIX systems with SAN storage. I have the Symantec upgrade guide Upgrading to Veritas Netbackup 6.5 and it appears to be pretty detailed, but it just covers the steps to get from point A to point B. Some of the things I am interested in finding out: - is there anyway to estimate how long step X might take? I realize that there are so many variables that it is not possible to say popluating the EMM will take X hours but if enough people chime in on what their experience was like, maybe we can come up with an average - have there been any show stoppers that were unanticipated? We could all learn from this, knowing what questions to ask up front based on our past...er...challenges. NBU has so many options and is such a broad product that I doubt any two environments are identical. Just sort of brain storming here, looking forward to hearing (seeing?) what you all have to share. If we get a good dialog going I will attempt to compile it into something usable and post it back here. T. -- ) ( ) [_]) This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
On Tue, Mar 4, 2008 at 10:26 AM, Scott Jacobson [EMAIL PROTECTED] wrote: I'm in the process of a 5.1 to 6.5.1 upgrade in my stagging environment (Windows Master, 4 Linux Media Servers) as of yesterday and today. When finished, I'll be heading east to upgrade the operations there. Upon returning, I'll then upgrade the production system here (Windows Master, 11 Linux Media Servers with ACSLS and a SL8500 Library), so I'll have much to share. One thing I've noticed (with two different 6.5.1 media sets); many read errors. We've found it easier to copy the data to a media server and NFS mount to that location and run the install's from there. At minimum, I'd check the read or copy capability from the CD/DVD drives on the systems you intend to upgrade. -sj Interesting... Do you mean you are finding some of the NBU media to be defective? Or are we talking older drives that are flaking out? T. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I'm in the process of a 5.1 to 6.5.1 upgrade in my stagging environment (Windows Master, 4 Linux Media Servers) as of yesterday and today. When finished, I'll be heading east to upgrade the operations there. Upon returning, I'll then upgrade the production system here (Windows Master, 11 Linux Media Servers with ACSLS and a SL8500 Library), so I'll have much to share. One thing I've noticed (with two different 6.5.1 media sets); many read errors. We've found it easier to copy the data to a media server and NFS mount to that location and run the install's from there. At minimum, I'd check the read or copy capability from the CD/DVD drives on the systems you intend to upgrade. -sj WEAVER, Simon (external) [EMAIL PROTECTED] 3/4/2008 8:35 AM Id be interested to hear if anyone had a plan of action from any NBU upgrade - I will be doing 5.1 to 6.5.1 Si From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Tuesday, March 04, 2008 3:32 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hi all, I am interested in hearing about any of the upgrades that you have done, mainly going from 5.x to 6.5 There seem to be quite a few environments (in my area) that are looking to upgrade, and I am putting together some documentation that asks questions to better prepare for it. I am still learning the ropes of NBU but I have a lot of experience with the server side of things especially Sun and AIX systems with SAN storage. I have the Symantec upgrade guide Upgrading to Veritas Netbackup 6.5 and it appears to be pretty detailed, but it just covers the steps to get from point A to point B. Some of the things I am interested in finding out: - is there anyway to estimate how long step X might take? I realize that there are so many variables that it is not possible to say popluating the EMM will take X hours but if enough people chime in on what their experience was like, maybe we can come up with an average - have there been any show stoppers that were unanticipated? We could all learn from this, knowing what questions to ask up front based on our past...er...challenges. NBU has so many options and is such a broad product that I doubt any two environments are identical. Just sort of brain storming here, looking forward to hearing (seeing?) what you all have to share. If we get a good dialog going I will attempt to compile it into something usable and post it back here. T. -- ) ( ) [_]) This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5
I upgraded from 5.1 to 6.5 in Oct 2007. It was a very smooth update that worked really well. I did all my prework and made sure that my catalog was in sync. I had no bad tape entries in the database. I also upgraded my WHOLE environment in a 12 hour window. I started with my master server and moved my way thru all 27 Media Servers. They consist of Solaris8, Solaris9, Solaris10, HPUX 11.11, Windows 2003 Server. I use SSO, vaulting, exchange backups, ORACLE RMAN backups. I have a EMC CDL720 (Virtual Tape Library), a L700e with 11 9940B tape drives, and 1 8TB disk staging unit. I really had no issues that were show stoppers. I would say to do all the prework and double and triple check it. As long as your existing environment is not messed up, it will work just great. Kevin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, March 04, 2008 10:35 AM To: Tony T.; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Id be interested to hear if anyone had a plan of action from any NBU upgrade - I will be doing 5.1 to 6.5.1 Si From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony T. Sent: Tuesday, March 04, 2008 3:32 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Lets hear about your upgrade experience! 5.x - 6.5 Hi all, I am interested in hearing about any of the upgrades that you have done, mainly going from 5.x to 6.5 There seem to be quite a few environments (in my area) that are looking to upgrade, and I am putting together some documentation that asks questions to better prepare for it. I am still learning the ropes of NBU but I have a lot of experience with the server side of things especially Sun and AIX systems with SAN storage. I have the Symantec upgrade guide Upgrading to Veritas Netbackup 6.5 and it appears to be pretty detailed, but it just covers the steps to get from point A to point B. Some of the things I am interested in finding out: - is there anyway to estimate how long step X might take? I realize that there are so many variables that it is not possible to say popluating the EMM will take X hours but if enough people chime in on what their experience was like, maybe we can come up with an average - have there been any show stoppers that were unanticipated? We could all learn from this, knowing what questions to ask up front based on our past...er...challenges. NBU has so many options and is such a broad product that I doubt any two environments are identical. Just sort of brain storming here, looking forward to hearing (seeing?) what you all have to share. If we get a good dialog going I will attempt to compile it into something usable and post it back here. T. -- ) ( ) [_]) This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
