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 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 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. ---------------------------------- 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
