That's my idea as well. But I would like to keep the original config as well. Thinking I can use the fact that the drives are mirrored. Op 10 jun. 2015 17:25 schreef "David McSpadden" <[email protected]>:
> Not sure if it is the same but when I p2v’d my HP’s in production one > thing we found was to uninstall all the HP tools prior to the P2V. The HP > tools played havoc on the VM machines. > > We use the VMWare and not the Hyper V though. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Dave Lum > *Sent:* Wednesday, June 10, 2015 11:18 AM > *To:* [email protected] > *Subject:* RE: [NTSysADM] SBS2008, baremetal backup needs other drive > besides C: > > > > I can’t tell you how happy I was when I migrated SBS to a VM! When it came > time to do a swing migration to SBS2011 it was nice to make a copy of the > VM’s and take them to the lab (to create a clone SBS server) to perfect the > swing migration as I was able to snapshot the SBS environment at every step > of the way. Today I VM everything, even in scenarios where it just 1 VM on > a physical box. > > > > I too, have used disk2VHD to P2V servers, but it’s been many years. > > > > My latest trick is to use a USB 3.0 dual-bay HDD dock to flip workstations > from spinning drives to SSD using the clone feature. Old PC, SSD speed, no > need to reinstall anything. Way too easy… > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Rene de Haas > *Sent:* Wednesday, June 10, 2015 2:05 AM > *To:* [email protected] > *Subject:* Re: [NTSysADM] SBS2008, baremetal backup needs other drive > besides C: > > > > :-) > > > > That was my preference as well. > > > > I did do that with 2 of their terminal servers actually. > > > > I did try that first with disk2vhd and it looked like it was working at > first. > > Then after installing the Hyperv tools things went wrong. > > Maybe I will have another go at that. > > > > Thanks > > > > On Wed, Jun 10, 2015 at 12:47 AM, Susan Bradley <[email protected]> > wrote: > > Okay now I get what you are trying to do, you are trying to move drive > config as part of the restore process. > Bare metal backup will want to put itself back on exactly the same > configuration as it had before. > You are probably going to need something like Storagecraft to rejigger the > drive config. > Or put it in a virtualized setup (which honestly I'd recommend - SBS 2008 > and 2011 work better as virtualized servers IMHO - the virtualized hardware > behaves better than real metal) > > MS wants feedback on patching: http://tinyurl.com/patchingsurvey > On 6/9/2015 3:40 PM, Rene de Haas wrote: > > As for the disk, thanks for the confirmation. > I meant the windows server backup. > I tried first the whole server, then realized the problem that it wanted 4 > disks. > Then thought restore the system, but that also didn't work because it > wanted to restore drive 3 besides drive 1. > Which I can also see when starting to create a backup it will also check > that drive. > > On Wed, Jun 10, 2015 at 12:21 AM, Susan Bradley <[email protected] > <mailto:[email protected]>> wrote: > > Server 2008 or Vista disk will do as well, but it has to be that era. > > When you say standard windows backup, do you mean you are using > the Windows backup console or the wizard in the SBS console to > backup the entire server? > > Which disks does it look like it's trying to recover? > > Hardware independent restores can also be done with StorageCraft. > I've also moved a physical to virtual with the Disk2vhd tool in > sysinternals. > > On 6/9/2015 3:13 PM, Rene de Haas wrote: > > I use the standard Windows backup. I don't get an > errormessage. The backup runs ok. > Just if I in the backup enable system recovery it > automatically checks 2 disks instead of just c: > > What brought it up is I want to replace 4 smaller mirrors by 4 > 600GB drives in Raid 10 config and just have the original > drives as partitions on the Raid 10 > > The problem is when I restore it sees only one drive and > complains there aren't enough. > So I was thinking first restore system as c:, start up and > from there restore other drives to partitions on the big Raid 10. > > They did have Acronis. Tried that, disk to disk, but it was > soooo slow. I cancelled it after about one hour trying to copy > a 76G drive with according to the software 11 hours remaining. > > One other question. Do I need to use the SBS2008 disk for the > bare metal restore, of can I make due with just a Windows 2008 > disk? > > Thanks > René > > On Tue, Jun 9, 2015 at 6:19 PM, Susan Bradley > <[email protected] <mailto:[email protected]> > > <mailto:[email protected] <mailto:[email protected]>>> > > > wrote: > > Say what? > > What exact error messages are you getting as that's not so > unless > of course you have multiple drives and the files are > spread around > a bit as noted.. > What backup program are you using? Native? > And you booted with SBS 2008 or Vista media? (you can't use > Win7/2008r2 era boot media to boot to find the backup devices) > > MS wants feedback on patching: > http://tinyurl.com/patchingsurvey > On 6/9/2015 9:08 AM, Rene de Haas wrote: > > No no pagefile, bootfiles.are on C: > The only thing I saw out of the ordinary so far was a > folder > ai_recyclebin. > That location doesn't seem to be mentioned in the > registry though. > I also noticed our online backup program has temporary > folders > there. One for the backup and one for brick level backup. > Could that be the cause? > Thanks > René > > On Tue, Jun 9, 2015 at 5:39 PM, Charles F Sullivan > <[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>>> wrote: > > Pagefile, boot files (separate partition on > Windows 7 and > later), > any file that is considered part of the System State. > Files that > are considered part of the System State expanded > hugely > with Vista > and often include even third-party application files. > > *From:*[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> > > [mailto:[email protected] > > > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>>] *On Behalf Of *Rene > de Haas > *Sent:* Tuesday, June 9, 2015 11:26 AM > *To:* [email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>> > <mailto:[email protected] > <mailto:[email protected]> > <mailto:[email protected] > <mailto:[email protected]>>> > *Subject:* [NTSysADM] SBS2008, baremetal backup needs > other drive > besides C: > > Hi, > > Like in the subject. To be able to restore the > system it needs > another drive besides C: > > I haven't seen yet why that would be. Googling hasn't > given me the > right hint yet. > > Any Ideas? > > Thanks > > René > > > > > > > > > > > > > Attention: Information contained in this message and or attachments is > intended only for the recipient(s) named above and may contain confidential > and or privileged material that is protected under State or Federal law. If > you are not the intended recipient, any disclosure, copying, distribution > or action taken on it is prohibited. If you believe you have received this > email in error, please contact the sender, delete this email and destroy > all copies. > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > Please consider the environment before printing this email. >
