VM Converter (SV2I)
You can use theVMware vCenter ConverterTM to create a virtual machine from an exisiting .sv2i image. The .sv2i image is created by Symantec BackupExec System Recovery (formerly Livestate Image).
The .sv2i file is a system restore file that contains information about your system. Using the Recovery Environment (PQRE), an entire computer containing more than one drive can be restored. This type of restore uses the system index file (.sV2i) to reduce the amount of time needed to restore the drives.
Ghost Products
Can we use Ghost to create the sv2i image? This is where we discover that “Ghost” is different products;
- Symantec LiveState Recovery is a backup product
- Norton Ghost (Ghost v9 & v10) is a backup product (since version 9, based on the same engine as LSR)
Norton Ghost is not a “ghost” or classic ghost product. Symantec Ghost or Ghost Solution suite is a “classic ghost”. - Symantec Ghost Solution Suite [GSS] (Ghost v8 & v11) is a deployment product
Symantec Ghost/Ghost Solution Suite does things like post clone configuration, which are essential for deployment, but not required for backup. If you use Ghost to image 100 machines at a time, you don’t actually want them to be indentical — machine names, domain joining and network settings need to be configured automatically. The Ghost console also allows the deployment of applications, and the migration or preservation of user data across a imaging operation. GSS can convert from V2i to either GHO/VMDK/VHD/real disk but not write to V2i.
SUMMARY:
LiveState Recovery and Norton Ghost v9 & v10 use the SV2I extension.
Symantec Ghost v8 & v11 produce GHO files.
The newer GSS 2.5 contains Ghost v11.5 which can also save images directly to VMDK format
VMDK (Virtual Machine Disk Format)
VMware products use the VMDK (Virtual Machine Disk Format) file format to store a virtual machine’s hard-disk image. Ghost Solution Suite (GSS) 2.5 contains Ghost v11.5 which can save images directly to VMDK format with no intermediate step.
NOTE: VirusScan Access Protection can get in the way of your VMDK creation process, make sure that your settings are warn not block;
4/06/2009 1:07:00 PM Would be blocked by Access Protection rule (rule is currently not enforced) %machine%\%user% C:\Program Files\Symantec\Ghost\ghost32.exe E:\GHOST\IMAGE\image.vmdk Virtual Machine Protection:Prevent modification of VMWare virtual machine files Action blocked : Create
