Physical server to Zone?

hey all,
I have been looking around for a bit on this and wasn't successful. I have 2 SFV100 running Solaris 10 and I would like to decom these machines in the very near future. I am looking for a way (if it exists) to move my Solaris install from the bare metal SFV100 to a zone running on a T1000.
Links to posts, a quick howto, I just need something to point me in the right direction.
Thank you all.

I haven't delved deep into the consolidation aspect of zones (just some rudimentary "playtime" with zones only so far). I foresee a problem with the scenario you are trying to address.
SunFire V100 are based on the sun4u architecture
T1000 are based on the sun4v architecture.
I believe there is that incompatibility that might prevent you from "migrating" your physicals to zones there in (especially if you have software that hasn't been tested on sun4v).
If I'm wrong, I'd request the other more learned members of this forum to correct me.
Cheers

Similar Messages

  • Migration from physical server to zone (solaris 10)

    Hello all,
    I found an old thread about the subject Migrate Solaris 10 Physical Server to Solaris 10 Zone but i have a question.
    Using the flarcreare command, will add to the flar archive all the zpools i have in the server?. Right now we have 14 zpools.
    If i execute this command "flarcreate -n "Migration File" > -S -R / -x /flash /flash/Migration_File-`date '+%m-%d-%y'`.flar" will take all the zpools?
    This is for migrating from a E25k Server to a M9k Server
    The E25k (Physical Server) have this release "Solaris 10 10/08 s10s_u6wos_07b SPARC" and the zone server (M9k) have this release "Oracle Solaris 10 8/11 s10s_u10wos_17b SPARC" this could be an issue?
    Thanks for any help.
    Edited by: 875571 on Dec 9, 2011 7:38 AM

    flarcreate will only include data from the root pool (typically called rpool). The odds are that this is what you actually want.
    Presumably, on a 25k you would have one pool for storing the OS and perhaps home directories, etc. This is probably from some sort of a disk tray. The other pools are likely SAN-attached and are probably quite large (terabytes, perhaps). It is quite likely that instead of creating a multi-terabyte archive, you would instead want an archive of the root pool (10's to 100's of megabytes) and would use SAN features to make the other pools visible to the M9000.
    One thing that you need to do that probably isn't obvious from the documentation is that you will need to add dataset resources to the solaris10 zone's configuration to make the other zpools visible in the solaris10 zone. Assuming that these other pools are on a SAN, the zpools are no longer imported on the 25k, and the SAN is configured to allow the M9000 to access the LUNs, you will do something like the following for each zpool:
    # zpool import -N -o zoned=on +poolname+
    # zonecfg -z +zonename+ "add dataset; set name=+poolname+; end"In the event that you really do need to copy all of the zpools to the M9000, you can do that as well. However, I would recommend doing that using a procedure like the one described at http://docs.oracle.com/cd/E23824_01/html/821-1448/gbchx.html#gbinz. (zfs send and zfs recv can be used to send incremental streams as well. Thus, you could do the majority of the transfer ahead of time, then do an incremental transfer when you are in your cut-over window.)
    If you are going the zfs send | zfs recv route and you want to consolidate the zpools into a single zpool, you can do so, then use dataset aliasing to make the zone still see the data that exists in multiple pools as though nothing changed. See http://docs.oracle.com/cd/E23824_01/html/821-1448/gayov.html#gbbst and http://docs.oracle.com/cd/E23824_01/html/821-1460/z.admin.task-11.html#z.admin.task-12.

  • Standby server time zone - sync-up with primary

    As we are running our database with physical standby database - Oracle 10.2.0.3, O/S RHEL4 ES
    now the primary database server time zone is set to EST Time Zone and Standby database server is set to PST time Zone
    We would need to Sync-up standby time zone with Primary database server (EST)
    and also the standby server is having 2 instances,
    1. standby instance
    2. independent instance
    We are running rman for both the instances in standby server
    as part of this time sync, we need to bring down both the instances then reset the time zone in standby server as primary and bring both the instances up and run the rman backup.
    is this fine.
    Please let us know if this is fine or do we need to perform anything more.
    Thanks,
    AJ

    Please see the attached screenshot, which is of the last page of the Sync Setup process. It says to backup your Sync Key, and it offers a Print ... button and a Save... button. The correct Sync Key is necessary to recover your data, it is the encryption / decryption key. Sorry, without it your data is useless.

  • Server 2012 R2 ISO download is larger than DVD, how do I install on a new physical server?

    I have downloaded Server 2012 R2 (not the trial version) and the size of the ISO is 5.2Gb.  I get 'disc image file is too large' error when trying to create image on DVD.  How do I install 2012 R2 on a new physical server? 

    Does your server have an out-of-band management console?  Those can generally mount virtual media that is simply a file residing on the machine you are using to connect to the console.
    Another option is to use USB -
    https://technet.microsoft.com/en-us/library/dn293258.aspx
    . : | : . : | : . tim

  • V2P Virtual Machine to physical Server migration on IBM x3650 M4 and switch from BIOS to UEFI Boot environment

    Hi there,
    just wanted to share my experience with a manual P2V Migration. The VM became to ressource hungry and it was decided to move it off an ESX 5 Cluster to a dedicated physical Machine.
    V2P Virtual Machine to physical Server IBM x3650 M4 and switch from BIOS to UEFI Boot environment
    Task:
    V2P Migrate a VMware virtual machine to a IBM x3650 M4 with a ServeRAID 5110e RAID Controller or any other LSI RAID Controller without 3rd Party tools.
    This should also work with other RAID Controllers or Servers but be sure to pick the right drivers then.
    Extra Task:
    The VM's boot environment/virtual BIOS is BIOS, not UEFI (as per default VMware Setting). The physical Server is running in UEFI mode.
    The Challenge:
    After restore the Server won't boot or get into a BSOD (7B), because the RAID drivers are missing.
    After restore the VM won't boot because the boot environment has changed from BIOS to UEFI
    Preparations:
    An existing physical Server of the same type and with the same RAID controller and same OS would be nice for troubleshooting and checking the registry.
    An existing DHCP server will make networking things easier.
    Connect the new physical server x3650 M4 to power and network
        create a virtual drive that has at least the size of the existing VM plus the size of the full backup (.vhd). Should be about twice the size of the original vmdk.
    Get a USB Flash stick (I used a 8GB modell so no problem with larger sticks)
    Download and extract LSI MegaRAID Driver on that USB media (I used 6.705.05.00-MR_Windows_Driver directly from LSI website)
    Download and extract INTEL Network Adapter Driver on that USB media (I used 12.11.97.0 of e1r62x64.inf from 19.5 driver release from 2014.09.26 directly from LSI website)
    Step by Step:
    if you have an other physical Server of the same type and same Controller and same OS:
    1.    open regedit and export everything related to SCSIAdapter and megasas2 to .reg files or skip this step and use my files below
        some of this (sub)keys may not be accesible - you will then first take ownership and/or modify permissions to read them
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_1000&DEV_005B&SUBSYS_04121014&REV_05
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\megasas2
        this one is more complicated:
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase (only relevant are those devices where the service name is megasas2 - export the whole subkey and get the filtering done with tools like notepad++)
        Make a copy of the following files/folders:
        c:\programdata\LSI\
        c:\windows\inf\megasas2.INF
        c:\windows\inf\megasas2.PNF
        c:\windows\system32\drivers\megasas2.SYS
    on the existing VM:
    1.    create a full backup (image) with the built-in Windows Backup Utility and save it in an accessible network location (you will need this one, if anything goes wrong or you want to come back to this point.
        Alternatively you could create a VMware snapshot.
    2.    import the .reg files you created earlier or import my files below.
        Attention: This will make the VM unbootable!
        But it is required to prepare the VM for the new RAID controller when it will be restored on the physical server.
        Do NOT reboot now as this will make the VM unbootable!
    4.    Copy the LSI folder and the megasas2.INF/PNF/SYS files to the appropriate destination folders on the VM.
    3.    again create a full backup (image) with the built-in Windows Backup Utility and save it in an other accessible network location but not where you safed the first backup.
        This will be the "golden" backup if you want, where the RAID controller is prepares. We will rebuild the new machine with this second backup.
    4.    Optional: you could use the Backuputility now to restore the Systemstate of the first backup and reboot or restore the VMware snapshot.
        This will undo the changes we made to the VM.
    on the new physical server:
    1.    boot the physical server from Windows Server 2008 R2 SP1 DVD
    2.    when it is ready to install, press shift+F10 to get command prompt and do not click to install Server 2008
    3.    check driveletter of the USB stick with diskpart list vol (was C: at my Server, so don't wonder about that letter)
    3.    load drivers for ServeRAID SAS controller (this is mandatory to see the volume in diskpart)
        drvload c:\srv_2008_x64\megasas2.inf
    4.    load drivers for INTEL I350 Gigabit NIC's (you will need this to access the backup that is on the network)
        drvload c:\PRO1000\NDIS62\e1r62x64.inf
    5.    wpeinit (will start network. wait ~15 sec to let it start and get IP address)
        check if you have IP connectivity an address with ipconfig, if not, use an other NIC driver and repeat steps 4+5
    6.    create the EFI and BCD
        diskpart
        list disk
        select disk x (where x is the number of the disk to convert)
        clean
        convert gpt
        create partition EFI size=128
        format fs=fat32 quick label=EFI
        assign letter=i or any other free drive letter
        create partition MSR size=128
    6.1    Copy EFI bootloader to EFI partition
        i: (where i is the letter of your EFI partition)
        mkdir EFI\Boot
        mkdir EFI\Microsoft\Boot
        copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Microsoft\Boot (where x ist the default letter of the current Windows PE environment)
        copy x:\Windows\Boot\EFI\bootmgfw.efi i:\EFI\Boot\bootx64.efi (note that the file will be renamed to bootx64.efi)
    7.    create the new partitions
        diskpart
        create partition primary size=100000 (edit the size to your needs. this will later become the system drive of your server)
        format fs=ntfs quick label=Windows
        assign letter=Y or any other free drive letter
        create partition primary size=990000 (this will temporarily store your backup and we need it for the restore process)
        format fs=ntfs quick label=Backup
        assign letter=B or any other free drive letter
        exit
    8.    map network drive and copy the backup .vhd  to the local disk
        net use L: \\networklocation\where\you\saved\the\backup (enter the credentials when asked)
            copy the .vhd file that contains the OS of your VM to the local Backup Partition B. The relevant vhd file is usually the largest file in that fileset.
            Note that the names are very similarly - be sure to get the correct file!
        copy "L:\WindowsImageBackup\VMNAME\Backup 2015-02-03 123456\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd" B:\
            give it time, this is slow and will take some minutes/hours and you will not see any progress! Look at the disk-LED's to see if anything is still happening
    9.    mount the .vhd and copy it's contents to the new system partition
            Note that you can only mount a locally stored .vhd. You cannot mount a .vhd in a network location.
        diskpart
        select vdisk file=B:\00e767c6-xxxx-xxxx-xxxxxxxxxxxx.vhd
        attach vdisk
        select vol 5 (where 5 is the number of the mounted vdisk)
        assign letter=Z or any other free drive letter
        exit
    10. Restore the files from the image
        z: (where z is the letter of your mounted .vhd)
        xcopy * Y:\ /e /c /h /k /o /b /q /y (where Y: is the letter of your new partition with the label "Windows")
            several "Access denied" messages appear, ignore them. Those are SystemVolumeInformation folders.
    11.    Create Boot Configuration Data (BCD)
        bootrec /RebuildBcd
            this will try to repair the missing BCD on the second of the two small partitions we created earlier in and should normally work, otherwise you'll have to create BCD manually (search google for that procedure)
            Note that it may find more than one Windows installation and ask which sould be added to the boot list. Be sure to select only the one that is in the correct Volume (Y:\)
        that's it - exit the DOS command box and close the "Install Windows" Window, after a prompt it will reboot.
        Select "Start Windows Normally", if Windows Error Recovery appears.    
    12. Preparing Windows
        When Windows boots for the first time, DO NOT reboot if you are asked, it won't come back at this stage!
        Install Intel chipset drivers for the Server (I used "intc_dd_inteldp_9.4.0.1026_windows_32-64.exe" from IBM website)
        Open Device Manager, uninstall the "RAID-Controller" with the exclamation mark. You cannot install the correct driver for this Device at this point, it will bring you the error: "Cannot create a stable subkey under a volatile
    parent key"
        Once again, DO NOT reboot!
        In Device Manager select Action>Add Legacy Hardware
        click Next
        select Hardware manually
        select Storage Controller as Type
        LSI should be listed, select "LSI MegaRAID SAS 9281-8E"
        click Next, ignore the error "Code 10" Message.
        Click Done.
        Rightclick the LSI MegaRAID SAS 9281-8E device with the exclamation mark in Device Manager
        select Update driver
        select Browse my computer for driver software
        select let me pick from a list of device drivers on my computer
        select "Have Disk"
        browse to the folder where the extracted RAID driver 6.705.05.00-MR_Windows_Driver is located (e.g. USB Flash stick E:\6.705.05.00-MR_Windows_Driver\srv_2008_x64)
        then unselect "Show Compatible Hardware"
        on the right side, scroll up and select "IBM ServeRAID M5110e SAS/SSATA Controller"
        ignore the Update Driver Warning and click Yes
        click Next, ignore the error "Code 10" Message.
        ignore the exclamation mark on "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager but be sure that there is only this controller and no other RAID-Controller or LSI SAS Controller listed under "Other Devices"
    or "Storage Controllers"
        NOW you are safe to reboot
        After reboot you will find two "IBM ServeRAID M5110e SAS/SSATA Controller" in Device Manager
        Rightclick and uninstall the one with the exclamation mark. Do not tick the checkbox to remove the driver as well!
    You're done!! (hopefully)

    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase]
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C31115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C38015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C41115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C48015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C51115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C58015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C61115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C68015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C71115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C78015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C81115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C88015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C91115D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_C98015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20219E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0060&SUBSYS_D20319E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0071&SUBSYS_00721137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00011BD4]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00721137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00731137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_008F1137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B01137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B11137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B61137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00B71137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C21137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_00C31137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_03B11014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_040D1014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_10541000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_11771734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_14581002]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_1F201462]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_30351054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350C8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_350D8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_822910F1]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_843B1043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_84711043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92211000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92401000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92408086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92411000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92418086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92421000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92431000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92441000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A01000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0073&SUBSYS_92A11000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92501000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92511000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0078&SUBSYS_92701000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00011BAA]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00021BD4]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_00791137]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_02001AE3]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B21014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03B31014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_03C71014]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_070015D9]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11761734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_11B31734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_30361054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_350B8086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84731043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_84801043]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_8985152D]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92551000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92561000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92568086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92601000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92608086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92611000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92618086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92621000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92631000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92641000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92648086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92671000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92678086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92681000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92688086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92751000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92758086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92761000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92768086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92771000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92801000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92808086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92811000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92821000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92828086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92841000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92881000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92891000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92901000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_92908086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20819E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0079&SUBSYS_D20919E5]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0409&SUBSYS_10091000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10011000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10018086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10021000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10031000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10038086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10041000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10081000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10088086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100C1000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_100D1000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10811734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_10a31734]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20041000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_20051000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_30161054]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_34908086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35008086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35018086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35048086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_35078086]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0411&SUBSYS_82871033]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_1000&DEV_0413&SUBSYS_10051000]
    "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
    "Service"="megasas2"
    "DriverPackageId"="megasas2.inf_amd64_neutral_8eb95ad00f4c26d7"

  • Two SAP production systems in a single physical server

    Dear All,
    Is SAP support installing two SAP production systems like SAP ECC 6.0 of one customer and ECC 6.0 with a different SID and instance no. for another customer in a single physical server? Would like to know from the experts is this possible? If yes ,  what are the things to take care of this design if any?
    Thanks
    Hany

    Hi ,
    check below blog
    You can check the following blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5124. [original link is broken]
    It helps you to understand different logon pages for portal
    Koti Reddy

  • Multiple entries in the DAD file but one physical server

    Can someone confirm (point me in the right direction for documentation) that we can have multiple DADs on the same physical server. A typical situation is where there are separate LIVE and TEST database installations of APEX but the one apache server. So, how do I get the TEST and LIVE to have different DAD configurations, in particular the location of the images file ie the alais '/i/'.
    Our situation is a great deal more complex than my example above, as we could have in excess of 6 different APEX installations on the same physical server with each having to have a different location for the image files etc.
    Thanks in advance

    Hello,
    Each dads.conf file can include several, unique, <Location> directives, according to your needs.
    As the aliases are being defined outside a specific directive, it seems that you'll need to use different alias to each APEX instance.
    You can read more about configuring the DAD in here - http://download-uk.oracle.com/docs/cd/B31017_01/web.1013/b28948/confmods.htm#sthref544
    Hope it helps,
    Arie.

  • Multiple SAP system on single physical server.

    Hello Experts.
    We are in process of implementaing SAP solution withLandscpe having systems ECC 6.0, SolMan 4.0, BI. We are planning to have 3 Sytem landscape for all.
    Now but currently we are having only one Physical server
    Is it possible to Install 6 SAP system on single server?(DEV and QAS for ECC, Solman, BI respectively). The server is having sufficient hardware for 6 system as per sap standered. Planne OS is RHEL and DB MaxDB. Initially we are having 16 GB RAM extendable.
    Will SAP support such kind of landscape?

    Hi Nikhil
    Just my two cents:
    Never put non-prod/prod systems on the same server, how would you test os patches, what if system wide components cause problems, what if - for example - you want to upgrade your database on the dev system, but you need a new library, which is not compatible to the version needed by the prod system.
    Your single linux box will not be big enough to hold all these systems, trust me. And x86_64 hw is sooo cheap ))
    Regards, Michael

  • ADS+Terminal Services on a Single Physical Server running Windows Server 2008 R2

    We have a Dual Processor Server (2 x Intel Xeon E5-2620v2 + 32GB RAM) running on Windows Server 2008 R2. This has ADS configured. We now wish to add a VDI Setup with NComputing Zero-Clients. We have to run Terminal Services with User RDS CAL + User
    CAL for all VDI Clients.
    Please confirm if we can have both the ADS & Terminal Services running on the same physical server ? Are there known issues or crashes due to this ? Or should both these run on two different servers ? Customer does not want to invest in one more server
    & OS. Hence, we have to run both the services on a single physical server. Customer has just upgraded his server to a Dual Processor with 32GB RAM to accommodate both the services.
    Please advice, if we can run both the ADS & TS on the same server. What is the best practice for this Solution ?
    Thanks & Regards,
    VR
    ([email protected])

    Hi,
    After referring your comment I can say that, you can able to use ADS and Terminal service on same physical server with server 2008 R2. But installing a terminal server on an Active Directory domain controller is not recommended. I suggest that it’s not a good
    practice to manage the environment in that way. If possible, then try to run on two different machines for better result and to avoid any problem. Allowing users to run programs on a domain controller could create security risks and performance issues.
    If the Terminal Server role service is installed on a domain controller, the security settings of the domain controller will need to be adjusted to allow user’s remote access to the server. This remote access is controlled by the "Allow log on through Terminal
    Services" user rights assignment, which can be configured by using the Group Policy Management Console (GPMC).
    You can refer below link for more information.
    1.  Installing RD Session Host on a Domain Controller
    2.  Best practices for setting up Remote Desktop Licensing (Terminal Server Licensing) across Active Directory Domains/Forests or Workgroup
    Hope it helps!
    Regards.

  • Exchange Server 2013 Hyper-V vs Physical Server & SMB3.0 vs SAN

    Looking for advise on installing Exchange Server 2013 in a virtual (Hyper-V) environment or dedicated physical server installation.  Also, when setting up the data storage, what's the best practices for using SMB3.0 vs direct storage SAN.  We're
    leaning to shared storage using SMB3.0 rather the SAN (very costly) and can use a dedicated 2012 Server with 4TB of storage (RAID 10) with (shares).
    Thank you,
    William

    Have you tried Storage Calculator? search it on TechNet site an input the values .. If you want me to give your the specs then I'd ask
    Total   Send/Receive Capability / Mailbox / Day
    Average Message Size (KB)
    Mailbox Size Limit (MB)
    Personal   Archive Mailbox Size Limit (MB
    If you already have an existing Exchange 2010/2007 then you can also calculate the above input.
    Let me know ..
    Where Technology Meets Talent

  • How to Implement DC and RDS on a single physical server

    Can any one guide me that how to install DC and RDS on a single physical server. It would be highly great full.

    Hi,
    Whilst possible to do it isn't supported and you should have your DC as a dedicated DC and then a separate server(s) for the remote desktop session host.
    Regards,
    Denis Cooper
    MCITP EA - MCT
    Help keep the forums tidy, if this has helped please mark it as an answer
    Blog: http://www.windows-support.co.uk 
    Twitter:   LinkedIn:

  • How to migrate Sun One directory server to a new physical server install

    need help
    We have to move our existing installation of sun on directory server 5.2 to a new physical server.
    We have a new physical server with a new host name. I am trying to find an easiest way to take a snapshot of our existing server and put it on a new installation
    So will installing sun one directory server , its shows me two choices either to create a new instance or copy configuration from a existing server
    What do i choose and which is the fastest route to replicate my old server
    Thanks a bunch in advance
    Sganb

    Hi,
    I'm glad you're still using the old, glorious Sun One Directory Server 5.2, because it brings me back a lot of memories... But are you seriously talking of the 'plain' version, with no patches/hot fixes on top? If that's the case, you're using of a software that has been developed in 2004 and released in Jan 2005! Just for you to be aware, in the last *8* (eight) years a considerable number (in the magnitude of 10^3) of bugs, security problems and performance issues has been identified and fixed...
    However, to provide a better answer to your question, it would be important to understand the 'big picture' in terms of scenario and requirements:
    1) Is this a critical 24x7 service for which you need to perform an on-line migration or you have a 'maintenance window' during which the service may be switched off?
    2) Is the old server member of replication environment? If yes, how many masters/slaves do you have already? Shall the new server be part of this topology? What role shall it have?
    3) Would it be possible to make the the old server able to communicate with the new server?
    4) How big is the database that you've got to migrate? Do you have any requirement in terms of caches?
    5) Do you take backups on a regularly basis and have in place working (*tested*) backup/restore procedures?
    6) Is the new server conserving or changing the O.S. and architecture? [SPARC->SPARC, x86->x86, SPARC->x86, Solaris -> ? , 32 .vs. 64-bit? ]
    7) What are the steps you did to 'install' the software on the new server?
    Thanks,
    Marco
    P.S.: I don't wanna sound 'scaring' with all these questions, neither this should be intended as an 'hidden advertising' for Oracle Professional/Consulting Services, but the only way to not put in jeopardy your data is being aware of the risks, having the control of what's going on and ... possibly have a 'B' plan ;-)
    P.S.S.: My last suggestion is to consider a migration to a later release AS SOON AS POSSIBLE; the latest is ODSEE 11.1.1.7, which is available here:
    http://www.oracle.com/technetwork/middleware/downloads/oid-11g-161194.html
    and seems to work pretty well ;-)

  • Improve VM IOPs performance vs. physical server

    Hi there,
    Need some advice on VM configuration and improving IOPs - were testing out VM IOPs performance on our EMC SAN vs. physical server attached to the same SAN testing for migration.
    Server setup - we have a 4-Way 32-Core (X7550CPU) HP DL580  from 3 years ago running physical OS connected to the above SAN and also a VM (8vCPU) hosted on  latest 3-Way HP DL580 60-Core (E4870 v2) with ESXi 5.1 both servers are using 8Gb FC connect to SAN.
    We've setup an IOmeter test on both physical and VM (test disk is RDM physcal mode) with 100GB test file on a RAID10 drive, based on the tests - the physical server can produce almost 10000IOPs while the VM can only produce 4800IOPs on a 4KB 100% read; 100% random test profile with 4 workers and 32 outstanding queues configuration.
    Can anyone advise how I can improve the performance IOPs on the VM or is this expected given that its a VM its likely to produce less IOPs and is the percentage difference between the physical/VM consistent or expected.We've even tried increasing the VM vCPU from 8-16 but the results don't seem to change much.
    Many thanks

    Are you using identical or similar multipathing configurations on both tests?
    Which virtual SCSI controller are you using on the VM?

  • Find whether OS on which Oracle DB is deployed is a VM or Physical server

    Hello,
    Is there a way via SQL or any built in utility could provide me the information that the OS on which my Oracle DB is deployed is a VM or a Physical Server?
    Ta.

    You can query the OS:
    [root@vm601 ~]# dmidecode | grep -i virtual
        Version: VirtualBox
        Product Name: VirtualBox
        Family: Virtual Machine
        Product Name: VirtualBox
    [root@vm601 ~]# virt-what
    virtualbox
    [root@vm601 ~]# lspci | grep -i VGA
    00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter

  • Maximum number of domains per physical server

    I am curious as to whether or not there is a maximum number of domains per physical server. Is it just based on resources, i.e. memory, hdd space, etc. or does Oracle have it's own specific recommendations? I realize, as implied, that one could put a number of vm's on a server that would utilize the server ram up to an amount reserved for the OS.
    Just wondering if there is a recommendation.
    By the way, we are running WLS (10.0MP1) and OSB (3.0) on top of Win2K3.
    Thanks for nay info,
    Todd

    Typically it depends on the resources.
    If the WLS instances are heavily utilized, at some point having more JVM's than the number of cores impacts performance if the apps are CPU bound. Similar applies for apps that use a lot of memory or sessions. There is no blanket answer and there is no hard and fast limit.

Maybe you are looking for