Subject: Re: [Veritas-vx] Adding a second A5x00 array to UE4500 volume manager is smart. Many of your disks have configuration database copies stored on them. VxVM will use this information and everything will be fine. -- ____________________________________________________________________________ Doug Hughes Engineering Network Services System/Net Admin Auburn University doug@eng.auburn.edu ================ I'm still learning Veritas, but my understanding is that when VxVM starts up, it scans all disks to find which were initialized to be under VxVM control. The private region on each disk specifies which disk group/volume the disk is in, and VxVM will set things up accordingly. So, in short, I don't believe it matters if the devices change, VxVM should figure it out. -- _ _ |_| Collective |_| Theo Van Dinter |_ technologies _| Consultant, on-site at RSA/Security Dynamics. ========================= Using VxVM, this will be fine, the meta information for the volumes and stuff are stored on the disks themselves. As long as the system can see the disks it will be fine. A quick test for it is to shut the system down, swap some of the disks around (label them to be sure) and bring the system up. > Richard Hogg > Senior Pre Sales Consultant > Compelsolve - e-Business Solutions ============================= I highly recommend not doing a reconfiguration reboot. Instead, attach everything, bring the system up normally, and run 'drvconfig', 'devlinks', and 'disks'. This will do the equivalent of a reconfig reboot, but it won't change any of your device aliases, only create new ones. Otherwise, if your controllers get renumbered, you can definitely run into serious problems. There are sources for how it is that IO controllers get numbered, thus letting you figure out if things will get renumbered and how to deal with it if they do, but I recommend avoiding the whole situation by just running the above three commands. -- Luke A. Kanies | "The Internet, of course, is more than just a place System Engineer | to find pictures of people having sex with dogs." ============================== In general, no. Veritas writes a unique serial number on each disk. So, you should be able to shut down the machine, scramble all the disks (other than boot) and have it reboot just fine. As long as Veritas can *see* the disks, you should be fine, and nothing bad should happen if the controllers change. In fact, that's how DMP can tell that it has redundant paths to the disks. -- Darren Dunham ddunham@taos.com Unix System Administrator Taos - The SysAdmin Company Got some Dr Pepper? San Francisco Bay Area < Please move on, ...nothing to see here, please disperse > ============================== Hello, Veritas Volume Manager doesn't care when you move your hardware around. Just make sure you do a "boot -r" at the OK prompt after you install your new disks. You can re-arrange your disks, and do a boot -r and VxVM will see everything. The VxVM disk names will not change, but the controller names will. VxVM sits on top of Solaris, so its okay. Brendan =============================================== You don't have anything to worry about, especially if your not using fibre hubs. Each new HBA will show as a new controller, so if you are adding a new A5200, with BoxID set to 0, and you are setting the array to function as a Full Loop (as opposed to a split loop) you'll see the new disks show up as C5, targets 0-10 (front) and 16-26 (back). If you then connect another HBA to the array (say on B0) you'll endup with C6, targets 0-01, and 16-26, and DMP should pick up C6 as a multiple path. If your using a hub things can get alittle more tricky, however. Let me know if you have problems. But in answer to your origoal question, you won't touch your old drivers, and don't have to worry. benr@cuddletech.com