Normal redundancy and physical disks

Version of the grid: 11.2.0.3
Platform: Oracle Enterprise Linux 6


I'm a bit confused about the term "Two-way mirrored" in the documentation of the DSO.


If I want to keep 1 tera bytes of business data in an ASM diskgroup with NORMAL redundancy.
Should I need 2 physical Disks of 1TB each ?
or 
Should I need 3 physical Disks of 1TB each ?

ASM is not a software RAID. ASM works based on file extensions and provides data redundancy by using the free space on drive failure of disk groups. By default, each disc is a group of failure. For a mirror (normal) 2 channels, you need at least 2 rupture discs groups; for the 3 - way (top), you need at least 3. You can also create a 2-way mirror with 3 drives, in which case data will be written alternating. Having ASM normal redundancy in your example you must have at least two drives of 1 TB, but you can also use 3 and will have more space. You can also use an external RAID and use no redundancy ASM (external), although ASM will give you better performance and flexibility because you can add disks to increase the space without having to rebuild your storage space.

Tags: Database

Similar Questions

  • Problem with VMWare Workstation combo, .vhd virtual drives and physical disks in the sector of size 4K?

    All,

    I suspect something wrong with some of my virtual machines.  I have been using these virtual machines for a while, and I see some weird behaviour recently.

    I see a lot of corruption in the virtual hard disk (.vhd based).  CHKDSK automatically gets performed many large files such as Oracle datafiles get damaged etc...  It all seems quite random and inconsistent, but I am using .vhd virtual machines in VMWare Workstation for years without problem.  This problem is new, and hard drives are basically unstable.

    I * think * (and I'm totally off base) that is perhaps the issue with my new external hard drives.  These discs have a 4 KB sector size, without e512.  Thanks to this architecture of hard drive, don't mount not the tools of Microsoft or manupulate .vhd files on these disks.  The questions seem to go away if I switch to vmdk or switch to the physical hard disk size-one-sector 512kb.  Because errors are not compliant, that I don't really have a way to document/prove that is the case, but it seems to be.

    I use version 9.0.0 on Windows 7 Workstation, and the guest is Windows Server 2008R2.

    My question is:

    (1) what meaning?

    (2) how I prove/document, since it is a contradiction?

    (3) is this a known problem?

    (Btw, switching HDD's vmdk is not an option in our case due to an obscure legal agreement with Microsoft.  I have to distribute my VMs in vhd format, even if they are designed to run on VMWare...)

    -> Adam

    These discs have a 4 KB sector size, without e512.

    (I've highlighted "without e512" in "BOLD" to key in my answer to the host operating system.)

    -L'OS is Windows 7 Enterprise

    According to the political support for the 4 K sector hard drives in Windows, Windows 7 does not support the native 4 K (logical 4 k sector size) but it does not support Advanced Format or 512th (size of logical sector physical and 512 bytes of 4 K) and that is can be the question.

  • How many per physical disk VHDs?

    I'm new on the ESXi server.  My company is going through the transition from physical servers to virtual servers on one of our contracts.  The client has provided the material for us, but there are a limited number of hard disks of the 'new' server  The server will run three virtual computers, 2 Web servers and a database server.  Each VM has its own dedicated hard disk.  Our old server DB had 11 young readers and our initial plan was to migrate all of them in a virtual drive.  My feeling is that this will cause performance problems because the operating system will treat the separate virtual drives and physical disks and try more I/O that the drive can handle.  I think it might be better to move to a few large virtual drives and their partition into 11 partitions.  Any ideas on that?

    For the DB (assuming that MSSQL server), you should have an OS vmdk, one for data files, one for the transaction logs files and possibly one for tempdb files.

    That should be enough. It would be better to place the data, logs, and the Tempdb on high performance specifien 9VMFS built RAID 10) but of course, we can always what we want.

  • 11 GR 2 Grid Infrastructure install - with normal redundancy ASM disk group requires 3 disks?


    Hello

    I want to install 11 GR 2 grid Infrastructure in a new environment in cluster - 2 nodes). I use the 11.2.0.4 GI Installer on Oracle Linux 6.5 x 86-64

    However when it is in the installer of GI, it comes to choose the storage Option - I choose ASM disk groups.

    Then change the path of discovery to pick up my candidate ASM disks.

    I enter the disk group name SIR give Normal redundancy, choose 2 discs of candidate and then press < next > to Setup.

    However, I gives me the message

    [INS-30510] Insufficient number of ASM disks selected

    The number of selected disks was inadequate for the level of redundancy selected

    For a disk group with redundancy level "Normal" disks at least "3" are recommended

    I always thought that Redunancy Normal required only 2 discs and high redundancy requires 3 disks?

    No idea what is gpoing?

    Thank you

    Jim

    Consult the following notes for how to move:

    Note 1638177.1 and 428681.1

    Concerning

    Thomas

  • Oracle ASM normal, high and external redundancy

    Hello

    I have some doubts in the levels of normal, high, and external redundancy in the concept of the DSO.

    External - any group fail. No mirroring.

    Normal - two way mirror. Group of failure.

    Top - three way mirror. Group of two failed.

    1. I hope that my understanding on above mentioned 3 types in good.

    2. my main question is what is the minimum number of disks required for the establishment of normal and external redundancy disk group? We cannot create disk group with the members of a single disc?

    Kind regards

    007

    Normal - two way mirror. Group of failure.

    Top - three way mirror. Group of two failed.

    This is false. You need at least two failure for normal and three groups of failure for high redundancy.

    By default, each disk or logical unit number is a group of default, but you can also add more drives to the same group of interlacing of the installation failure. The configuration depends on material available, disk space requirements and the needs of redundancy. ASM provides redundancy between groups of failure.

    Remember that ASM is not disk mirror. It is not RAID. ASM from mirrors of the level and allocation of file units. He knows about Oracle database files and can therefore use optimum and variable block sizes based on the patterns of files. You can add and remove disks to reconfigure your drive grouips online without having to re - initialize your storage, which you can not do with RAID or external redundancy.

  • Reference Dell MD3000i and degraded physical disk channel

    Nice day

    We have a Dell MD 3000i with an extra box storage. And today, there are two mistakes in the journal:

    1 physical disk channel set to gradient

    Date/time: 30.04.13 10:56:14
    Sequence number: 9783
    Type of event: 1209
    Description: Physical disk set to gradient channel
    Specific event codes: 0/0/0
    Event category: error
    Component type: channel
    Location of components: side physical disk: channel 1
    Recorded by: Module to slot 1 RAID controller

    2. each physical disk - gradient path

    Date/time: 30.04.13 10:56:14
    Sequence number: 9784
    Type of event: 1513
    Description: Individual physical disk - gradient path
    Specific event codes: 0/0/0
    Event category: error
    Component type: channel
    Location of components: side physical disk: channel 1
    Recorded by: Module to slot 1 RAID controller

    In this case recovery guru say "you must contact your technical support representative to correct this defect. Do NOT try to fix this problem yourself. So, how we can receive technical support recommendations and try to repair this failure?

    If you need more details, we can put any storage array profile output.

    Hello UtkinE,

    Yes, you will need to stop all iSCSI traffic so that you can update the NVSRAM.  With the timeout error you get all came from controller 1 & he had only discs 1 & 5.  The current version of NVSRAM you version 4 and the last one which is for the MD3000i is version 13.  With who have older firmware it was improvements to correct your problem in the latest versions of firmware.  I also had one of our analysts will confirm as well just to make sure that it is the best fix for your problem.

    Please let us know if you have any other questions.

  • Analyze the index on the machine of Dataguard and redundancy of ASM disks

    Dear friends,

    I have two questions regarding disc Dataguard and ASM.

    (> > 1) for best performance, periodically, we rebuild the index index and analysis analyze table. What is the best periodic steps to do to get better performance?

    I mean, first of all is rebuilding of index, is second index analysis and so on......

    (> > 2) if I run analyze the index or the table on my PRODUCTION system he replicated this effect on statndby dataguard automatic system? If so, how it is replicated?

    (> > 3) my last question related with high redundancy of the ASM disk. I have some confusion on this area.

    Let's say I have 10 disks in a diskgroup '+ DATA' and I did 'HIGH' level redundancy, means 3 way redundancy. Here I know 3-way the redundancy, it writes data on 3 discs at a time. But what of the other 7 discs. In fact, I need to know the mechanism of writing?

    -Each disc is identical to the other drive?

    -For HIGH redundancy, how many disk failure can be tolerated for any loss of data?

    Waiting for your kind reply......

    "on my PRODUCTION'---> you mean"on my FIRST.

    Yes, the data dictionary is updated when you run dbms_stats.gather% and updates data dictionary are through recovery that applies to the WAITING for more.

    NOLOGGING surgery would not be applied to the expectation (the index would be marked corrupted to the standby) unless you have set on FORCELOGGING.

    Hemant K Collette

  • Im trying to install adobe creative suite 2 premium without cd and after running Disk 1 it ask disc 2 but I have just electronics cd physical disks

    Im trying to install adobe creative suite 2 premium without cd and after running Disk 1 it ask disc 2 but I have just electronics cd physical disks

    Unless you install the special download version provided by Adobe, everything that you install in the way of CS2 you will get very far.  See below for an explanation and then follow download instructions.

    CS2: Error: unavailable activation server | CS2, Acrobat 7, hearing 3 -.

    l http://helpx.adobe.com/x-productkb/Policy-Pricing/Creative-Suite-2-activation-end-Life.htm

    https://helpx.Adobe.com/Creative-Suite/KB/CS2-product-downloads.html

  • Script to create the folder on the physical disk and not in the package

    Hello-

    Attached is a script that I have which will create a folder on the C:\ inside the bubble.  What I need, it's so he can create a folder on the physical disk and not inside the bubble.  Can someone tell me what I did wrong here?  I have a similar script which creates a folder on the D drive for the linked clones and it works fine.  Thanks in advance!

    Change the isolation mode of the file %drive_C%\vaforms5 'Merged' into the Attributes.ini, rebuild the ThinApp and check.

    With the help of isolation have merged, the application can read/write file on the physical machine.

  • PERC 710 add physical disks for RAID 5 virtual disk and keep data

    I think to set up a physical disk 4 RAID 5 array on my new PowerEdge T320.  That should give me enough space to last long.  I have two empty slots of HD.  If I need more space, later, I'll be able to add one or two additional physical disks without losing the data already on the virtual disk?  If so, how?  I don't see a way to do this in the manual of Perc 710.

    Thank you

    Andrew

    Yes, it is "doable" later.  This can be done in the PERC BIOS, but it can be done in OMSA (OpenManage Server Administrator) within the OS.

    One thing to keep in mind is the limit of 2 TB "floppy" Windows on BIOS systems compatible.  If you plan to 4x4TB disks in a RAID 10, that TB ~ 8 'disc' will be converted to the GPT and BIOS UEFI boot mode value.

  • AGAIN starts after only one physical disk has several partitions makes no sense to the production oracle database?

    Dear Experts,

    Don't + REDO1 diskgroup have only one physical disk has several partitions makes no sense to the production oracle database?

    For example

    • + Diskgroup Redo1 have 2 50 GB disks (fact these 2 discs are the same physical disk partitions OR these should be separate disk as recommended approach)?
    • + Diskgroup Redo1 have 2 drives of capacity 50 GB (for RAID 1 + 0)
    • + Diskgroup Redo2 have 2 50 GB disks
    • + Diskgroup Redo2 have 2 drives of capacity 50 GB (for RAID 1 + 0 )

    Thank you and best regards,

    IVW

    Hello

    Partitioning your disks for ASM configuration as 'A' might make sense. If you lose one disk, you have the discs to another.

    'B' totally make sense if you have lost the disc that you have lost all group ASM and you need to change this with something like 'C '.

    But obviously you need redundancy ASM configured appropriately.

    Kind regards

    Juan M

  • Is this normal in "normal redundancy?

    The GI version: 11.2.0.4 (RAC 3-node)

    OS: Oracle Linux 6.4

    Storage EMC Symmetrix VMAX

    I created a diskgroup with normal redundancy as shown below.

    10 each = 5000GB 500 GB LUN

    CREATE DISKGROUP DATA_DG1

    NORMAL REDUNDANCY

    DISC

    "ORCL:DATA_D1,"

    "ORCL:DATA_D2,"

    "ORCL:DATA_D3,"

    "ORCL:DATA_D4,"

    "ORCL:DATA_D5,"

    "ORCL:DATA_D6,"

    "ORCL:DATA_D7,"

    "ORCL:DATA_D8,"

    "ORCL:DATA_D9,"

    'ORCL:DATA_D10 '.

    ATTRIBUTE 'au_size' = "4 M";

    DiskGroup created.

    Given that it was normal, I was expecting half of gross space 5000 GB = 2.5 terabytes of usable space. But, the query below shows the output, I myself only 2.19 terabytes of usable (2249,86 GB) space. About 250GB short of what I expected. So where's my advantage 250 GB?

    SQL > select name, TYPE, 1024/1024/TOTAL_MB, FREE_MB/1024/1024, USABLE_FILE_MB/1024/1024 of v$ asm_diskgroup where name = 'DATA_DG1 ';

    NAME TYPE TOTAL_MB/1024/1024 FREE_MB/1024/1024 USABLE_FILE_MB/1024/1024

    ------------------------------ ------ ------------------ ----------------- ------------------------

    NORMAL DATA_DG1 4.8828125 4.8825531 2.19713593

    The amount of usable file space is equal to the amount of free disk space subtracted from the amount of disk space required to restore redundancy after failure divided by the level of redundancy of the disk group that is in your case.

    Run:

    select trunc((free_mb - required_mirror_free_mb) / 2) as useable from v$asm_diskgroup where name='DATA_DG1';
    

    Source: http://prutser.wordpress.com/2013/01/03/demystifying-asm-required_mirror_free_mb-and-usable_file_mb/

  • VMware Workstation failed to mount the physical disk 10TB

    VMware workstation or any other product vmware does support more than 2 TB of physical disks?

    I am trying to connect a 5 of 10 TB raid enclosure and mount it on my ubuntu vmware workstation machine. The common error that I receive is when mounting the reader on ubuntu and I think it might have something to do with the size of the file.
    I am running vmware workstation 12 in windows 10.
    The disk is taken offline in windows and I'm under WS as an administrator.

    Error VMDK CONTENT DiskPart Info

    Operation failed on the file "\\.\PhysicalDrive1".

    If the file is located on a remote file system, make sure that the network connection and the server on which resides this disk to work correctly. If the file is saved on a removable medium, link media.

    Select Retry to retry the operation.

    Click Cancel to end this session.

    Select continue to pass the error to the guest operating system.

    I/o error, dev sdb, sector 11721553632

    I/o error, dev sdb, sector 11721552128

    I/o error detected. File system stop

    Please unmount the file system and to rectify the problem (s)

    metadata I/O error: block 0x2baa8b100 ("xlog_bwrite") error 5 numblks 8200

    can not read the superblock

    # Disk DescriptorFile

    version = 1

    Encoding = "windows-1252".

    CID = 6f4a8bb1

    parentCID = ffffffff

    isNativeSnapshot = 'no '.

    createType = "fullDevice."

    # Description of the measure

    RW 23441768448 DISH '\\.\PhysicalDrive1' 0 partitionUUID \\?\scsi#disk & ven_h #w & prod_raid5 #5 & 19bb575e & 0 & 010000 #{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

    # The database disk

    #DDB

    ddb.adapterType = "free".

    ddb.geometry.biosCylinders = "1024".

    ddb.geometry.biosHeads = "255".

    ddb.geometry.biosSectors = "63".

    DDB. Geometry.Cylinders = "16383.

    DDB. Geometry.Heads = "16".

    DDB. Geometry.sectors = "63".

    ddb.longContentID = "55c8f3052c372c02465d66656f4a8bb1".

    DDB. UUID = "60 00 C2 97 8 a 7 c c2 cb - 9 a 27 51 78 58 a7 e6 3f"

    ddb.virtualHWVersion = "12".

    H/W RAID5

    Disc ID: 00000000

    Type: SATA

    Status: Offline (policy)

    Path: 1

    Target: 0

    LUN ID: 0

    Path: PCIROOT (0) #PCI (1C07) #PCI (0000) #ATA (C01T00L00)

    Current read-only State: No.

    Read-only: No.

    Boot disk: No.

    Disk swap file: No.

    Disk hibernation file: No.

    Crash dump disk: No.

    Cluster disk: No.

    The official version said that WS allows only virtual up to 8 TB of disk.

    According to my own tests, it only limits the size of the VMDK for 'New - VM' Assistant.
    Once you have a greater vmdk - just tried a vmdk 10TB - WS won't complain about the size.
    I don't expect that WS will prevent the physical disks to use inside a virtual machine that is already configured.
    So in your case I think you started WS with a normal user account.
    Try to start as administrator WS - maybe even using the administrator account.
    I think that then it will work.
    Unfortunately, the error messages produced by vmware.exe are not really accurate-, so there is no way to know if you really have a bad super block.
    To test if this is really the problem and not just an error message - poor try to mount the drive directly.
    Please post the vmdk - want to know if there is something unusual about 5.5 TB in the disk.

  • VMware Vista support physical disk device does not not for some VM.

    I handle Win2k8 64 bit vm on esx5.5 Update 2 which are evidence of "Disk of Vista VMware help" have the error "this device is not present, is not working properly or is not all its drivers installed." (Code 24) ». Versions of VMware Tools vary, either 9.4.0 9.4.5 build-1585188, build-1598834 or 9.4.10 build-2068191.

    Google missed most of the time. I can't find any information on what concrete this virtual device is or what it does in particular, except that it may be involved in the creation of snapshots suspended.

    In addition, the device seems to be attached to the vmrawdsk service, which does not exist on the server. These virtual machines were not P2V, they have been created since iso win.

    One guess what it is and how I might be able to fix it?

    I got it on a working server my copy on the file vmrawdsk.sys missing a server well-known, uninstall VMware Tools, restart, reinstall it and restart again. Then the VMware Vista support physical disk device / service vmrawdisk are working normally.

  • VDR 2.0.1 / dev/sdb /-physical disk not rise, destinations

    Hi all

    I have a problem with my VDR 2.0.1 last backup has been the failure due to power and after that problems on VDR destinations where I had destination normally one network, stay another one, physical disk no rise/dev/sdb /. I can not remove from vClient cause it says "destination is in use", but there is not any visible running task. This physical disk is exactly the same size as one of my VM who began with backup when possible failure has occurred. Also, under the VDR icon in vClient I see the same VM hard file.

    That's happened? How can I mage it?

    Concerning

    Kris

    Remove the disc from VDR-VM-mixer under 'Edit Settings' with Remove.

    That make a snapshot of the virtual machine affected and after that delete all the snapshots of this virtual machine.

    Normally this will solve these problems, if VDR was interrupted during backups.

    Paul

Maybe you are looking for