Restore VM with empty (0 byte) disks files - possible ?

[dsATspace]

Hello,
I need to restore VMs but only the 1.st DISK / operating system disk.

Have build a script that restore the 1.st DISK but the VM needs to be exists. (using: Start-VBRViVirtualDiskRestore)

Is it possible to restore a VM but all disks are "0 byte"
so that I can use "Start-VBRViVirtualDiskRestore" to restore the 1. disk after ?

Or is it possible to restore with exlude all disks insted of disk 1 ?

[david.domask]

Hey dennis,

The EntireVM Restore cmdlet doesn't really have an option for that, but can I ask, why not just make a new VM with PowerCLI/HyperV cmdlets first, and then restore the disks to that VM?

Also, is there a reason for just the OS Disk? If you're looking to do some malware assessment on the VMs, maybe SureBackup or the DataIntegration API are more suitable?

[dsATspace]

Hi David,

thanks

>The EntireVM Restore cmdlet doesn't really have an option for that, but can I ask, why not just make a new VM with PowerCLI/HyperV cmdlets first, and then restore the disks to that VM?

OK thats a idea... but there a some diffrent systems: windows / linux / etc.
arround 300 ... and the development will restore some of them for testing...
then I need to know what kind of OS, CPU count, RAM count ......
I am lazy so if it will restored the settings are still there


>Also, is there a reason for just the OS Disk?

yes not enough space (diskspace) on the restore site
it is a small System for testing, and it sould be vor testing with real systems (updates / changes etc.)

Can not restore the hole VMs because the testing.System will going out of diskspace.

[david.domask]

> OK thats a idea... but there a some diffrent systems: windows / linux / etc.
arround 300 ... and the development will restore some of them for testing...
then I need to know what kind of OS, CPU count, RAM count ......
I am lazy so if it will restored the settings are still there

You can check the AuxData property of COib objects returned by Get-VBRRestorePoinit.

OsInfo is parsed there as well as a lot of other useful stuff you can parse over automagically