[Veritas-bu] Media server migration

Thanks Simon
 
Yeah, tpautoconf -t results in the required info.
 
Cheers
 
Dave

________________________________

From: WEAVER, Simon [mailto:simon.weaver at astrium.eads.net] 
Sent: 15 September 2006 06:36
To: Clooney, David; veritas-bu at mailman.eng.auburn.edu
Subject: 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 Weaver
3rd Line Technical Support
Windows Domain Administrator 

EADS Astrium Limited, B23AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU

Email: Simon.Weaver at Astrium-eads.net
<mailto:Simon.Weaver at Astrium-eads.net> 

        -----Original Message-----
        From: Clooney, David [mailto:david.clooney at bankofamerica.com] 
        Sent: 14 September 2006 16:33
        To: veritas-bu at mailman.eng.auburn.edu
        Subject: [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. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS,
England
        



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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060915/7b0c52b4/attachment.html