Possibly. If nothing else goes wrong, which over a long enough timeline - it does; and you should count on it. Depending on your resources, these are thing you either are or arent willing and prepared to allow to happen.
Ultimately, there is no need for an aggressive approach unless it absolutely calls for it. The more aggressive you get, the wider your problem vector typically gets. I'm not nay-saying the approach -only advising caution if its not a necessary one. -- Espi On Mon, Apr 28, 2014 at 7:08 PM, Mike Tobias < [email protected]> wrote: > If something did go wrong with the restore, couldn't he just put the > original drives back in? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Micheal Espinola Jr > *Sent:* Monday, April 28, 2014 8:48 PM > *To:* ntsysadm > *Subject:* Re: [NTSysADM] RE: server migration w/new HDs > > > > Backup/restore situations are often ones that bite people in the ass when > they least expect it to. In this situation, I would not opt to put that to > the test unless it was absolutely a neccessity. > > > -- > Espi > > > > > > On Mon, Apr 28, 2014 at 3:01 PM, Kent McKinney <[email protected]> > wrote: > > Even if you swap one drive at a time and get the virtual disk size > increased, the OS partition would also need to be resized. Its time > consuming and will greatly affect server performance. Safest way is to > install the server backup feature, do a system state backup, pull the old > drives out (with existing data intact that you can always roll back to) > create the new array and restore. > > --- Original Message --- > > From: "Maglinger, Paul" <[email protected]> > Sent: April 28, 2014 5:34 PM > To: "'[email protected]'" <[email protected]> > Subject: [NTSysADM] RE: server migration w/new HDs > > This is a multi-part message in MIME format. > > > --_000_36DA94300D69184A91500B695547A148481711CCCOMSTAR1scvlcom_ > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > > I just talked with someone about a similar situation. > > HP-UX server running 2 72G mirrored drives and had one fail. The vendor > su= > bbed a 146G drive. In this case it would rebuild to only 72G of the 146 > dr= > ive, but the vendor said that if the other 72 drive failed and was > replaced= > > with the 146 then I could extend it to the full 146 at that point > . > > I have not tested this, and am not sure if it would work, but wondering if > = > you could replace the drives one at a time allowing for the rebuild. I > did= > something similar with a EVA SAN and was successful. It took a long > time,= > but I didn't have to take the system down. I'm not sure I'd risk it on a > = > > production system. > Can you do a system level backup/restore? > > From: [email protected] [mailto: > [email protected]= > > ] On Behalf Of Jesse Rink > Sent: Monday, April 28, 2014 4:07 PM > To: [email protected] > Subject: [NTSysADM] server migration w/new HDs > > Have a Dell T310 server with (4) 1TB sas drives in a RAID5 array, > running W= > indows 2008R2. Need to replace the drives with (4) 2TB sas drives in a > RAI= > D5 array. Server only holds 4 physical HD bays so I can't just add an > ex= > tra array. Curious if anyone has any tricks to speeding up this migration > = > other than rebuilding the OS from scratch on the (4) new 2Tb sas drives > and= > reinstalling all the app > > s on the server, etc. > > > > JR > > > > > > --_000_36DA94300D69184A91500B695547A148481711CCCOMSTAR1scvlcom_ > Content-Type: text/html; charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > > <html xmlns:v=3D"urn:schemas-microsoft-com:vml" > xmlns:o=3D"urn:schemas-micr= > osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" > = > xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml"; > xmlns=3D"http:= > //www.w3.org/TR/REC-html40"> > <head> > <meta http-equiv=3D"Content-Type" content=3D"text/html; > charset=3Dus-ascii"= > > > <meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)"> > <style><!-- > /* Font Definitions */ > @font-face > {font-family:Calibri; > panose-1:2 15 5 2 2 2 4 3 2 4;} > @font-face > {font-family:Tahoma; > panose-1:2 11 6 4 3 5 4 4 2 4;} > /* Style Definitions */ > p.MsoNormal, li.MsoNormal, div.MsoNormal > {margin:0in; > margin-bottom:.0001pt; > font-size:12.0pt; > font-family:"Times New Roman","serif";} > a:link, span.MsoHyperlink > {mso-style-priority:9 > 9; > color:blue; > text-decoration:underline;} > a:visited, span.MsoHyperlinkFollowed > {mso-style-priority:99; > color:purple; > text-decoration:underline;} > p > {mso-style-priority:99; > margin:0in; > margin-bottom:.0001pt; > font-size:12.0pt; > font-family:"Times New Roman","serif";} > p.MsoAcetate, li.MsoAcetate, div.MsoAcetate > {mso-style-priority:99; > mso-style-link:"Balloon Text Char"; > margin:0in; > margin-bottom:.0001pt; > font-size:8.0pt; > font-family:"Tahoma","sans-serif";} > span.BalloonTextChar > {mso-style-name:"Balloon Text Char"; > mso-style-priority:99; > mso-style-link:"Balloon Text"; > font-family:"Tahoma","sans-serif";} > p.msochpdefault, li.msochpdefault, div.msochpdefault > {mso-style-name:msochpdefault; > margin:0in; > margin-bottom:.0001pt; > font-size:10.0pt; > font-family:"Times New Roman","serif";} > span.balloontextchar0 > {mso-style-name:balloontextchar; > font-family:"Tahoma","sans-serif";} > span.emailstyle20 > {mso-style-name:emailstyle20; > font-family:"Calibri","sans-serif"; > > color:#1F497D;} > span.emailstyle21 > {mso-style-name:emailstyle21; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.emailstyle22 > {mso-style-name:emailstyle22; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.emailstyle23 > {mso-style-name:emailstyle23; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.emailstyle24 > {mso-style-name:emailstyle24; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.emailstyle25 > {mso-style-name:emailstyle25; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.emailstyle26 > {mso-style-name:emailstyle26; > font-family:"Calibri","sans-serif"; > color:#1F497D; > font-weight:normal; > font-style:normal; > text-decoration:none none;} > span.emailstyle27 > {mso-style-name:emailstyle27; > font-family:"Calibri","sans-serif"; > color:#1F497D;} > span.EmailStyle30 > {mso-style-type:personal-reply; > color:black;} > .MsoChpDefault > {mso-style-type:export-only; > font-size:10.0pt;} > @page WordSection1 > {size:8.5in 11.0in; > margi > n:1.0in 1.0in 1.0in 1.0in;} > div.WordSection1 > {page:WordSection1;} > --></style><!--[if gte mso 9]><xml> > <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> > </xml><![endif]--><!--[if gte mso 9]><xml> > <o:shapelayout v:ext=3D"edit"> > <o:idmap v:ext=3D"edit" data=3D"1" /> > </o:shapelayout></xml><![endif]--> > </head> > <body lang=3D"EN-US" link=3D"blue" vlink=3D"purple"> > <div class=3D"WordSection1"> > <p class=3D"MsoNormal"><span style=3D"color:black">I just talked with > someo= > ne about a similar situation. > <o:p></o:p></span></p> > <p class=3D"MsoNormal"><span style=3D"color:black">HP-UX server running 2 > 7= > 2G mirrored drives and had one fail. The vendor subbed a 146G > drive.&= > nbsp; In this case it would rebuild to only 72G of the 146 drive, but the > v= > > endor said that if the other 72 drive failed and > > was replaced with the 146 then I could extend it to the full 146 at that > p= > oint.<o:p></o:p></span></p> > <p class=3D"MsoNormal"><span style=3D"color:black">I have not tested this, > = > > and am not sure if > > it would work, but wondering if you could replace the dr= > ives one at a time allowing for the rebuild. I did something similar > = > with a EVA SAN and was successful. It took > a long time, but I didn’t have to take the system down. > I̵= > 7;m not sure I’d risk it on a production > system.<o:p></o:p></span></p= > > > <p class=3D"MsoNormal"><span style=3D"color:black">Can you do a system > leve= > l backup/restore?<o:p></o:p></span></p> > <p class=3D"MsoNormal"><span > style=3D"color:black"><o:p> </o:p></span>= > </p> > <div> > <div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in > = > 0in 0in"> > <p class=3D"MsoNormal"><b><span > style=3D"font-size:10.0pt;font-family:"= > ;Tahoma","sans-serif"">From:</span></b><span > style=3D"font-s= > ize:10.0pt;font-family:"Tahoma","sans-serif""> > listsadm= > [email protected] [mailto:[email protected]] > <b>On Behalf Of </b>Jesse Rink<br> > <b>Sent:</b> Monday, April 28, 2014 4:07 PM< > br> > <b>To:</b> [email protected]<br> > <b>Subject:</b> [NTSysADM] server migration w/new HDs<o:p></o:p></span></p> > </div> > </div> > <p class=3D"MsoNormal"><o:p> </o:p></p> > <div> > <p><span > style=3D"font-size:10.0pt;font-family:"Tahoma","san= > s-serif";color:black">Have a Dell T310 server with (4) 1TB sas drives > = > in a RAID5 array, running Windows 2008R2. Need to replace the > drives&= > nbsp;with (4) 2TB sas drives in a RAID5 array. Server > onl= > y holds > 4 physical HD bays so I can't just add an extra array. Curious > = > if anyone has any tricks to speeding up this migration other than > rebuildin= > g the OS from scratch on the (4) new 2Tb sas drives and reinstalling all > th= > e apps on the server, etc. <o:p></o:p></span></p> > <p><span > style=3D"font-size:10.0pt;font-family:"Tahoma","san= > s-serif";color:black"> <o:p></o:p></span></p> > <p><span > style=3D"font-size:10.0pt;font-family:"Tahoma","san= > > s-serif";color:black">JR<o:p></o:p></span></p> > <p><span > style=3D"font-size:10.0pt;font-family:"Tahoma","san= > s-serif";color:black"> <o:p></o:p></span></p> > <p><span > style=3D"font-size:10.0pt;font-family:"Tahoma","san= > s-serif";color:black"> <o:p></o:p></span></p> > </div> > </div> > </body> > </html> > > > --_000_36DA94300D69184A91500B695547A148481711CCCOMSTAR1scvlcom_-- > > > > >
