[HPADM] RE: RE: Data Centre MIgration with Lot of printers.

From: O'Donovan, Kevin (Kevin.O'Donovan_at_acs-inc.com)
Date: 10/28/05

  • Next message: Stephanie C: "[HPADM] inetd.sec"
    To: brian irvin <brian944us@yahoo.com>, hpux-admin@dutchworks.nl
    Date: Fri, 28 Oct 2005 06:25:16 -0500
    
    

    Apologies, I didn't mean to do a 'reply all'

     

     

    -----Original Message-----
    From: hpux-admin-owner@DutchWorks.nl [mailto:hpux-admin-owner@DutchWorks.nl]
    On Behalf Of O'Donovan, Kevin
    Sent: 28 October 2005 07:16
    To: brian irvin; hpux-admin@dutchworks.nl
    Subject: [HPADM] RE: Data Centre MIgration with Lot of printers.

     

    What you need to do largely depends on whether you're moving the servers or
    migrating onto new machines. If you're physically moving the equipment it
    makes it that much easier.

    My advise is to double backup EVERYTHING, and if possible verify the backups
    are complete. If you're moving the servers over, be prepared for the worse
    case where NONE of your data remains intact.

    - Ignite backup vg00 on all servers, at least twice -> if you're delivering
    these use different delivery routes for each set, one air, one ground, etc.
    which will cover you in case any set gets lost, the truck/plane has problems
    on the way.

    - generate an information collection script that goes through the system and
    documents everything - userids, groupids, volume group sizes, logical volume
    sizes, filesystem types (largefiles on?), mountpoints, file ownership, file
    permissions, complete swlist output, inittab, /sbin/init.d/ contents as well
    as the contents of all the /sbin/rc*.d/ directories, kernel parameters,
    drivers loaded, NIC configs.

    - ensure you have installation media or depots for all applications and
    system software you have installed on the servers, in case you need to
    reinstall them.

    - ensure you have full details of all maintenance & support agreements in
    case you need to call them
    - you'll need to update your support vendors to let them know the new
    addresses. It would also be worthwhile to give them advance warning that
    you are moving.

    Basically document everything you can think of.

    If you can get access to the new datacenter in advance, ensure that network
    connectivity is available, and try to do a dry run or two in advance to
    'sanity check' the process. That would be invaluable to iron out any
    problems you are likely to come across with the environment.

    On that basis ensure you have all the information you need for the new
    environment. Check whether you will keep your existing IP addresses or do
    you need to update them? If you need to update them find out what the new
    ones are as well as subnet masks, gateway addresses, etc.

    If possible, don't do it all in the one go, do a batch of servers at a time.

    That probably gives you a picture of the kind of task you're taking on,
    don't underestimate it, it is a huge task and the potential pitfalls are
    endless.

    Hope that helps,
    Kevin.

    -----Original Message-----
    From: hpux-admin-owner@DutchWorks.nl [mailto:hpux-admin-owner@DutchWorks.nl
    <mailto:hpux-admin-owner@DutchWorks.nl> ] On Behalf Of brian irvin
    Sent: 28 October 2005 05:02
    To: hpux-admin@dutchworks.nl
    Subject: [HPADM] Data Centre MIgration with Lot of printers.

    Hello:

    We are migrating our datacentre within the city to
    another location. Environment is full of RP
    Servers..Nclass, Lclass with EMC SAN. There are a
    large amount of printers also. This is a MC Service
    Guard environment. Could you all please guide me with
    respect what kind of prep work i need to do?
    Especially with the printer and EMC SAn what i need to
    do. I have never worked on a project like this..so
    please provide your valuable inputs. TIA and i will
    summarize.

    Thanks

    Brian.

     

                    
    __________________________________
    Yahoo! FareChase: Search multiple travel sites in one click.
    http://farechase.yahoo.com <http://farechase.yahoo.com>

    -- 
                 ---> Please post QUESTIONS and SUMMARIES only!! <--- 
            To subscribe/unsubscribe to this list, contact
    majordomo@dutchworks.nl 
           Name: hpux-admin@dutchworks.nl     Owner:
    owner-hpux-admin@dutchworks.nl 
      
     Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse
    only) 
                http://www.dutchworks.nl/htbin/hpsysadmin
    <http://www.dutchworks.nl/htbin/hpsysadmin>    (Web, browse & search) 
    --
                 ---> Please post QUESTIONS and SUMMARIES only!! <---
            To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
           Name: hpux-admin@dutchworks.nl     Owner: owner-hpux-admin@dutchworks.nl
     
     Archives:  ftp.dutchworks.nl:/pub/digests/hpux-admin       (FTP, browse only)
                http://www.dutchworks.nl/htbin/hpsysadmin   (Web, browse & search)
    

  • Next message: Stephanie C: "[HPADM] inetd.sec"

    Relevant Pages

    • Listing printers in AD after domain migration
      ... servers to our new AD enabled W2K domain. ... printers to "Enabled" (Policies are "Allow printers to be ... The problem appears to be with existing shared printers. ... After the migration, they continue to be shared, however, ...
      (microsoft.public.win2000.printing)
    • RE: Listing printers in AD after domain migration
      ... Listing printers in AD after domain migration ... servers to our new AD enabled W2K domain. ... This script will publish all shared printers on a machine. ...
      (microsoft.public.win2000.printing)
    • Re: Printer Migration questions
      ... I'm by no means an expert in this subject matter Printer Migration, ... 315983 How To Migrate a Printer Server Configuration Between Windows NT 4.0 ... servers. ... > The questions I have is how to migrate our 3000 Workstations printers. ...
      (microsoft.public.win2000.advanced_server)
    • CA agreement practices
      ... My environment has all 5.5 servers ... running on 2000 servers already part of a native mode AD. ... sites and 13 child domains. ... migration will take a couple of months. ...
      (microsoft.public.exchange.setup)
    • Moveing a 5.5 server to AD Domain
      ... Our company is currently using Exchange 5.5 as we wait for our other ... partners to finish their AD migration. ... Out current environment consists of an NT domain which holds only our ... like our NT domain removed and our Exchange 5.5 servers moved to the AD ...
      (microsoft.public.exchange.admin)