Re: [Veritas-bu] Media Server Migration
We are also planning to do the same thing before upgrading to 6.5. We are currently running 5.2 on HP-UX. I'm a little concerned about your comment about how long the bpmedia -movedb step can take. Do you have any benchmarks on timing? What do you consider a media server with many tapes, 700 tapes, 1000 tapes, 3000 tapes? Wayne BeDour Unix System Administrator PH: 313-593-9876 Internet: [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Andres Sent: Friday, August 22, 2008 5:48 PM To: Dean Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Media Server Migration Same here, that's pretty much my plan. However, with large catalog's that bpmedia -movedb step can literally run for days, even weeks on a media server with many tapes. I've thought about using bpimage to move the images rather than the media. I haven't tested it thoroughly yet. Does anyone have experience with this alternative, is it any faster? Is it sufficient to move image and tape ownership away from the migrating media server? From: Dean [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 4:21 PM To: Mike Andres Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Media Server Migration We are about to do this. The basic steps we are looking at are : * bpmedia -movedb for each tape owned by the media server so that the tapes are owned by the old 5.1 master * Uninstall NBU 5.1 on media server * Install NBU 6.5 on media server and integrate into new 6.5 environment * Remove storage units associated with the media server in the 5.1 environment * Remove SERVER= entries from the 5.1 environment * Possibly, further down the track, import remaining long retention backups from 5.1 environment into 6.5 environment Cheers, Dean On Fri, Aug 22, 2008 at 10:41 PM, Mike Andres [EMAIL PROTECTED] wrote: I would be interested in hearing thoughts on migrating a 5.1 Media server from a legacy 5.1 Master to a new, different 6.5 Master server. Would this require formally decommissioning the 5.1 media server via the 5.1 master then reinstalling 6.5 media server under the new 6.5 Master? Or is there a faster, easier way to migrate while maintaining media and image integrity? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Thursday, August 21, 2008 11:59 AM To: Martin, Jonathan Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? Good discussion, as I am looking at MIGRATION from 5.1 Server to NEW Server 6.5.2 My onyl concerns I have in the back of my head is how to move a Media Server that is on 5.1 over to 6.5.2 Anyone done a migration from an old system to a new one? Not too worried about the old robot or catalog, as this is all being replaced. If need be, I will have to import. Some systems are SQL, Oracle based online media servers Thanks, Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Thursday, August 21, 2008 5:35 PM Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? Yeah! Cheap shots at Symantec are reserved for those of us who have spent many restless nights fighting Netbackup. =P Just my .02 - Migrated several Windows 2000 5.1 environments to 6.0 MP4 and then to 6.5.1, 6.5.2 and 6.5.2a. Although there have been issues, I've only had to apply one engineering binary to one environment that had an issue with calendar backups. Maybe I'm just lucky (or maybe Symantec doesn't test on Non-Windows OS =P) but from my experience I think 5.1, 6.0 MP4, 6.51+ are all stable products. -Jonathan From: [EMAIL PROTECTED] on behalf of Ed Wilts Sent: Thu 8/21/2008 7:46 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? On Thu, Aug 21, 2008 at 6:04 AM, [EMAIL PROTECTED] wrote: Watch out for this one with 6.5.1 on Windows: http://seer.entsupport.symantec.com/docs/301175.htm The technote says that this is fixed in 6.5.2. http://6.5.2./ Right now I'm caught between that one and the completely broken 6.5.2A - http://seer.entsupport.symantec.com/docs/305609.htm The technote says that there's an EEB available for this. 6.5.2A is *NOT completely broken. Many years, us included, are running it in full production. You'd think they'd test this stuff before release by ,say, trying to run a backup or something... This has been discussed before. Your comment is unwarranted and low shots like this don't encourage Symantec employees or other users to help you. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist
Re: [Veritas-bu] Media Server Migration
Is this a Windows environment? I don't know if other OS's are different but in Windows you would have to decommission the Media Server from the original Master and then bring it on line as a new media server on the new Master. Make sure you expire all of the images associated with the media server before you remove it from the original config. Once that media server owns no tapes, you can take it home if you want. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Andres Sent: Friday, August 22, 2008 7:41 AM To: WEAVER, Simon (external); Martin, Jonathan Cc: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Media Server Migration I would be interested in hearing thoughts on migrating a 5.1 Media server from a legacy 5.1 Master to a new, different 6.5 Master server. Would this require formally decommissioning the 5.1 media server via the 5.1 master then reinstalling 6.5 media server under the new 6.5 Master? Or is there a faster, easier way to migrate while maintaining media and image integrity? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Thursday, August 21, 2008 11:59 AM To: Martin, Jonathan Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? Good discussion, as I am looking at MIGRATION from 5.1 Server to NEW Server 6.5.2 My onyl concerns I have in the back of my head is how to move a Media Server that is on 5.1 over to 6.5.2 Anyone done a migration from an old system to a new one? Not too worried about the old robot or catalog, as this is all being replaced. If need be, I will have to import. Some systems are SQL, Oracle based online media servers Thanks, Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Thursday, August 21, 2008 5:35 PM Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? Yeah! Cheap shots at Symantec are reserved for those of us who have spent many restless nights fighting Netbackup. =P Just my .02 - Migrated several Windows 2000 5.1 environments to 6.0 MP4 and then to 6.5.1, 6.5.2 and 6.5.2a. Although there have been issues, I've only had to apply one engineering binary to one environment that had an issue with calendar backups. Maybe I'm just lucky (or maybe Symantec doesn't test on Non-Windows OS =P) but from my experience I think 5.1, 6.0 MP4, 6.51+ are all stable products. -Jonathan From: [EMAIL PROTECTED] on behalf of Ed Wilts Sent: Thu 8/21/2008 7:46 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? On Thu, Aug 21, 2008 at 6:04 AM, [EMAIL PROTECTED] wrote: Watch out for this one with 6.5.1 on Windows: http://seer.entsupport.symantec.com/docs/301175.htm The technote says that this is fixed in 6.5.2. http://6.5.2./ Right now I'm caught between that one and the completely broken 6.5.2A - http://seer.entsupport.symantec.com/docs/305609.htm The technote says that there's an EEB available for this. 6.5.2A is *NOT completely broken. Many years, us included, are running it in full production. You'd think they'd test this stuff before release by ,say, trying to run a backup or something... This has been discussed before. Your comment is unwarranted and low shots like this don't encourage Symantec employees or other users to help you. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 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 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist -
Re: [Veritas-bu] Media Server Migration
Same here, that's pretty much my plan. However, with large catalog's that bpmedia -movedb step can literally run for days, even weeks on a media server with many tapes. I've thought about using bpimage to move the images rather than the media. I haven't tested it thoroughly yet. Does anyone have experience with this alternative, is it any faster? Is it sufficient to move image and tape ownership away from the migrating media server? From: Dean [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2008 4:21 PM To: Mike Andres Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Media Server Migration We are about to do this. The basic steps we are looking at are : * bpmedia -movedb for each tape owned by the media server so that the tapes are owned by the old 5.1 master * Uninstall NBU 5.1 on media server * Install NBU 6.5 on media server and integrate into new 6.5 environment * Remove storage units associated with the media server in the 5.1 environment * Remove SERVER= entries from the 5.1 environment * Possibly, further down the track, import remaining long retention backups from 5.1 environment into 6.5 environment Cheers, Dean On Fri, Aug 22, 2008 at 10:41 PM, Mike Andres [EMAIL PROTECTED] wrote: I would be interested in hearing thoughts on migrating a 5.1 Media server from a legacy 5.1 Master to a new, different 6.5 Master server. Would this require formally decommissioning the 5.1 media server via the 5.1 master then reinstalling 6.5 media server under the new 6.5 Master? Or is there a faster, easier way to migrate while maintaining media and image integrity? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Thursday, August 21, 2008 11:59 AM To: Martin, Jonathan Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? Good discussion, as I am looking at MIGRATION from 5.1 Server to NEW Server 6.5.2 My onyl concerns I have in the back of my head is how to move a Media Server that is on 5.1 over to 6.5.2 Anyone done a migration from an old system to a new one? Not too worried about the old robot or catalog, as this is all being replaced. If need be, I will have to import. Some systems are SQL, Oracle based online media servers Thanks, Simon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Thursday, August 21, 2008 5:35 PM Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? Yeah! Cheap shots at Symantec are reserved for those of us who have spent many restless nights fighting Netbackup. =P Just my .02 - Migrated several Windows 2000 5.1 environments to 6.0 MP4 and then to 6.5.1, 6.5.2 and 6.5.2a. Although there have been issues, I've only had to apply one engineering binary to one environment that had an issue with calendar backups. Maybe I'm just lucky (or maybe Symantec doesn't test on Non-Windows OS =P) but from my experience I think 5.1, 6.0 MP4, 6.51+ are all stable products. -Jonathan From: [EMAIL PROTECTED] on behalf of Ed Wilts Sent: Thu 8/21/2008 7:46 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Most recent stable release? On Thu, Aug 21, 2008 at 6:04 AM, [EMAIL PROTECTED] wrote: Watch out for this one with 6.5.1 on Windows: http://seer.entsupport.symantec.com/docs/301175.htm The technote says that this is fixed in 6.5.2. http://6.5.2./ Right now I'm caught between that one and the completely broken 6.5.2A - http://seer.entsupport.symantec.com/docs/305609.htm The technote says that there's an EEB available for this. 6.5.2A is *NOT completely broken. Many years, us included, are running it in full production. You'd think they'd test this stuff before release by ,say, trying to run a backup or something... This has been discussed before. Your comment is unwarranted and low shots like this don't encourage Symantec employees or other users to help you. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 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
Re: [Veritas-bu] Media server migration
Title: Message Thanks Simon Yeah, tpautoconf -t results in the required info. Cheers Dave From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: 15 September 2006 06:36To: Clooney, David; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] Media server migration Hi Dave Points look fine. Only thing to point out is: This document may be worth a read: http://seer.entsupport.symantec.com/docs/230047.htm Turn off Removeable Storage and set service to Disable if this is going to be a media server using drives via zoning / fiber. I have also tended to manually configure robot / drives rather than auto-detect. I think the command tpautoconf (I think) may be worth a look at too. (from command line /?) Hope its of some help. Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B23AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Clooney, David [mailto:[EMAIL PROTECTED] Sent: 14 September 2006 16:33To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Media server migration All I am undertaking the task of migrating a windows media server and want to give the basic outline just in case I have missed anything. Just to add the new media server will be performing the exact same task as the old media server , windows 2000 to windows 2003 1. zone drives so new media server has visibility 2. reboot new media server 3. configure drives on new media server 4. Add device host and configure new drives on the master 5. Update SSO 6. Create STU's 7. List all media associated with old media server and move to standalone then apply the below on the same media bpmedia -movedb -m media_id -newserver hostname [-oldserver hostname] 8. Inventory new media 9. Change all policies using old media server stu's to reflect new 10. To avoid FORCE_RESTORE_MEDIA_SERVER being implemented on the old media server , get a list of all backupid's associated with old media server and apply the below to all bpimage: -newserver name [-oldserver name] [-id id] 11. Decomission old media server when ready Q 1. The new media server can currently see two test drives in the same library as what the production drives are in , all drives are stk 9940A and B's , all media servers using the same ACSLS host for robotic control. Upon zoning in the new drives and rebooting the new media server , should it be as straight forward as running C:\program files\veritas\volmgr\bin\scan to get all the new drive info or is there more that needs to be done for visibility of the new drives ? Regards David Notice to recipient:The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group entity.If this email originates from the U.K. please note that Bank of America, N.A., London Branch and Banc of America Securities Limited are authorised and regulated by the Financial Services Authority. This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of Astrium Limited.Nothing in this email shall bind Astrium Limited in any contract or obligation.Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, EnglandNotice to recipient:The information in this internet e-mail and any attachments is confidential and may be privileged. It is intended solely for the addressee. If you are not the intended addressee please notify the sender immediately by telephone. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful.When addressed to external clients any opinions or advice contained in this internet e-mail are subject to the terms and conditions expressed in any applicable governing terms of business or client engagement letter issued by the pertinent Bank of America group
