Prev: migrating server 2k3 SBS to 2008
Next: Terminal Servers in Cluster - Login/Profile Issues - Please Help!
From: Phillip Windell on 7 Apr 2010 12:29
What would be the best strategy to do backup for an individual VM in HyperV?
Imaging is bad and that is what backing up the VHDs externally ammounts to,
so what would be a good approach short of a "big$$$" solution like MS-DRM?

We are not heavey into Virtualization yet,...but DR has been a big question
in my mind too.

--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------



"kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message
news:e4uwjpm1KHA.4560(a)TK2MSFTNGP02.phx.gbl...
> One could use the builtin OS iSCSI initiator but there needs to be an
> iSCSI target somewhere (extra) for SAN storage or Virtual Tape. It's not
> an optimal solution. but the tape can be used to backup data from the
> iSCSI target devices. There's no direct method TTBOMK.
>
> Phillip Windell wrote:
>> KJ can correct me if I am wrong, but I believe the iSCSI (not SCSI)
>> would be virtualized hardware that is "presented" to the Guest by the
>> Hypervisor. The Drivers should already be there in the VM already
>> when it was created, or maybe when you enable the iSCSI for the VM.
>>
>> Anyway, I use VMWare and VirtualPC,..I don't use HyperV,...but
>> genarally speaking you would "power down" the VM Guest. The
>> configure the VM for what it needs,...then power it back up. But
>> don't just go off my ramblings,...check the HyperV documentation for
>> this. What I have said so far should at least help you know what you
>> are looking for.
>> In fact you should read anything you find in the Docs about Disaster
>> Recovery and what the best approaches are in a HyperV environment.
>> Virtualization changes our approach to almost everything,...you have
>> to change with it.
>>
>>
>>
>> "Sarah Kingswell" <sarahkingswell(a)hotmail.com> wrote in message
>> news:eyRxVSm1KHA.260(a)TK2MSFTNGP05.phx.gbl...
>>> Thanks all for your responses but I am still confused ...
>>>
>>> Are you saying I should be able to access the SCSI Tape from the
>>> Hyper-V Guest Machine. Where do I get drivers from to install on
>>> the Guest machine? I have looked at HP's site and found nothing. I
>>> have an HP LTO 400/800GB drive which cost just short of �1500 and I
>>> don;t think the customer wants to replace it. It's brand new. It
>>> came with software but only the Small Business Edition of Symantec
>>> Backup Exec. Can't install this version on the Hyper-V Host cause
>>> it's windows 2008 Server and won't run the license. I can backup
>>> using Symantec Backup on the SBS server to a folder/file then use
>>> something else to backup to tape on the Hyper-V Host computer but
>>> then the customer is going to have to buy another product or upgrade
>>> Symantec Back Exec. Can I use the old NTBACKUP program on the Windows
>>> 2008 host computer?
>>>
>>>
>>>
>>> "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message
>>> news:udGkECe1KHA.3744(a)TK2MSFTNGP04.phx.gbl...
>>>> Sarah Kingswell wrote:
>>>>> Am I correct in thinking you cannot add tape backup drivers to a
>>>>> virtual machine? I want to be able to use backup exec on a virtual
>>>>> machine running windows 2008 but I have no way of installing the
>>>>> drivers. I can use the backup on the Hyper-V Host computer
>>>>> without a problem.
>>>>> I have a Small Business Edition of the Backup software which came
>>>>> with the drive. My problem is I can only install on the SBS server
>>>>> which is installed on one of the virtual servers. Microsoft have
>>>>> taken out the tape backup option from the windows backup program..
>>>>> now I am little stuck what to do unless I buy a different copy of
>>>>> backup exec. Never known this to be so flipping complicated.
>>>>>
>>>>> Any ideas
>>>>
>>>> Hyper-V guests would need to use iSCSI to get to the tape drives -
>>>> if at all.
>>>>
>>>> If this is BackupExec it's reported to work and be supported
>>>> solution. Check with the vendor for supported configurations
>>>>
>>>>
>>>> --
>>>> /kj
>
> --
> /kj
>


From: kj [SBS MVP] on 7 Apr 2010 16:42
Hot swappables in 2008 R2 are pretty attractive for some smaller
implementations. I'm doing some of that and iscsi targets. Passthrough disks
are another option for the smaller side.

DR sized, I'm leaning towards a native backup to an iscsi device. Recovery
seems much more straightforward.

Phillip Windell wrote:
> What would be the best strategy to do backup for an individual VM in
> HyperV? Imaging is bad and that is what backing up the VHDs
> externally ammounts to, so what would be a good approach short of a
> "big$$$" solution like MS-DRM?
> We are not heavey into Virtualization yet,...but DR has been a big
> question in my mind too.
>
>
> "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message
> news:e4uwjpm1KHA.4560(a)TK2MSFTNGP02.phx.gbl...
>> One could use the builtin OS iSCSI initiator but there needs to be an
>> iSCSI target somewhere (extra) for SAN storage or Virtual Tape. It's
>> not an optimal solution. but the tape can be used to backup data
>> from the iSCSI target devices. There's no direct method TTBOMK.
>>
>> Phillip Windell wrote:
>>> KJ can correct me if I am wrong, but I believe the iSCSI (not SCSI)
>>> would be virtualized hardware that is "presented" to the Guest by
>>> the Hypervisor. The Drivers should already be there in the VM
>>> already when it was created, or maybe when you enable the iSCSI for
>>> the VM. Anyway, I use VMWare and VirtualPC,..I don't use HyperV,...but
>>> genarally speaking you would "power down" the VM Guest. The
>>> configure the VM for what it needs,...then power it back up. But
>>> don't just go off my ramblings,...check the HyperV documentation for
>>> this. What I have said so far should at least help you know what you
>>> are looking for.
>>> In fact you should read anything you find in the Docs about Disaster
>>> Recovery and what the best approaches are in a HyperV environment.
>>> Virtualization changes our approach to almost everything,...you have
>>> to change with it.
>>>
>>>
>>>
>>> "Sarah Kingswell" <sarahkingswell(a)hotmail.com> wrote in message
>>> news:eyRxVSm1KHA.260(a)TK2MSFTNGP05.phx.gbl...
>>>> Thanks all for your responses but I am still confused ...
>>>>
>>>> Are you saying I should be able to access the SCSI Tape from the
>>>> Hyper-V Guest Machine. Where do I get drivers from to install on
>>>> the Guest machine? I have looked at HP's site and found nothing. I
>>>> have an HP LTO 400/800GB drive which cost just short of �1500 and I
>>>> don;t think the customer wants to replace it. It's brand new. It
>>>> came with software but only the Small Business Edition of Symantec
>>>> Backup Exec. Can't install this version on the Hyper-V Host cause
>>>> it's windows 2008 Server and won't run the license. I can backup
>>>> using Symantec Backup on the SBS server to a folder/file then use
>>>> something else to backup to tape on the Hyper-V Host computer but
>>>> then the customer is going to have to buy another product or
>>>> upgrade Symantec Back Exec. Can I use the old NTBACKUP program on
>>>> the Windows 2008 host computer?
>>>>
>>>>
>>>>
>>>> "kj [SBS MVP]" <KevinJ.SBS(a)SPAMFREE.gmail.com> wrote in message
>>>> news:udGkECe1KHA.3744(a)TK2MSFTNGP04.phx.gbl...
>>>>> Sarah Kingswell wrote:
>>>>>> Am I correct in thinking you cannot add tape backup drivers to a
>>>>>> virtual machine? I want to be able to use backup exec on a
>>>>>> virtual machine running windows 2008 but I have no way of
>>>>>> installing the drivers. I can use the backup on the Hyper-V
>>>>>> Host computer without a problem.
>>>>>> I have a Small Business Edition of the Backup software which came
>>>>>> with the drive. My problem is I can only install on the SBS
>>>>>> server which is installed on one of the virtual servers. Microsoft
>>>>>> have taken out the tape backup option from the windows
>>>>>> backup program.. now I am little stuck what to do unless I buy a
>>>>>> different copy of backup exec. Never known this to be so
>>>>>> flipping complicated. Any ideas
>>>>>
>>>>> Hyper-V guests would need to use iSCSI to get to the tape drives -
>>>>> if at all.
>>>>>
>>>>> If this is BackupExec it's reported to work and be supported
>>>>> solution. Check with the vendor for supported configurations
>>>>>
>>>>>
>>>>> --
>>>>> /kj
>>
>> --
>> /kj

--
/kj


First  |  Prev  | 
Pages: 1 2 3
Prev: migrating server 2k3 SBS to 2008
Next: Terminal Servers in Cluster - Login/Profile Issues - Please Help!