QUESTION OF REDUNDANCY NORMAL ASM

Similar Questions

• Redundancy of the Normal ASM - three stores, three groups of failure

  Hello

  I have a question about groups of failure in ASM. I have an ASM diskgroup with normal redundancy and records of three different preparations. Each storage disks are in separate groups of failure (see screen below). I know what ASM allocates to a point as it allocates a copy of copy and the primary mirror and mirror copy is placed on a different disk that is part of a group of different failure. And it is understood for the configuration with two storage (or controllers) and two different groups of failure. But what with configuration where are three storages and failure groups? My question is: If I failed three groups if new extensions are allocated are mirrored are placed on the other two discs are it is a part of a group of different failure? Or maybe this kind of configuration (with three groups of normal redundancy ASM failure) is not supported?

  

  I know what ASM allocates to a point as it allocates a copy of copy and the primary mirror and mirror copy is placed on a different disk that is part of a group of different failure. And it is understood for the configuration with two storage (or controllers) and two different groups of failure. But what with configuration where are three storages and failure groups? My question is: if I have three groups of failure, if new extensions are allocated are mirrored are placed on the other two discs are it is a part of a group of different failure? Or maybe this kind of configuration (with three groups of normal redundancy ASM failure) is not supported?

  No matter how much you failgroup. Normal redundancy requires at least 2 Failgroup.

  Oracle will allocate primary measure in a failgroup and place the mirror of the scopes in an another failgroup.

  The order does not matter since you always have a copy in a different failgroup.

  See example below (d = data extended)

  FG1 |   FG2 | FG3

  ========|===============|=========
  

  d1      |   d1_copy:

  |   d2          | d2_copy

  d3_copy |               | d3

  When you create a Diskgroup without specifying the failgroup, Oracle will automatically create a failgroup to each diskgroup. So, if you create a normal with normal redundancy Diskgroup and ASMDISK 10, ASM will create 10 failgroups.

  You have 3 warehouses and 3 Failgroup

  If you loss storage (h/f) ASM will tolerate because you measure mirror in any other failgroup (h, l, square).

  If you loss both storage (h/f) or two different storage disk/controller at the same time ASM will not tolerate. (Need to restore a backup database)

  Your point of failure: you must make sure that the two storages/controllers/disks will still be available.

  If your concern is: can I have a situation where two storage can do fail (or cut) at the same time. Then, you need high redundancy, because this configuration will tolerate you two storages loss (h/f) at the same time and Diskgroup will remain active.

• 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

• You would rely on external redundancy for ASM?

  DB version: 10.2.0.4
  Operating system: Sun Solaris 5.10
  
  If you have been setting up a database of critical Production on RAC ASM and equipment storage (Sun or IBM) already has a capacity of RAID10 correct, you would still NORMAL or HIGH redundancy? If so, why?

  no no no.

  A server can have multiple HBA cards. The HBA connects to a storage network that can support multiple storage arrays.

• question about redundancy and failover from one site to tunnel

  First, I create the underside of crypto card,

  crypto IPSec_map 10 card matches the address encrypt-acl
  card crypto IPSec_map 10 set peer 209.165.201.1

  card crypto IPSec_map 10 the transform-set RIGHT value

  card crypto IPSec_map 10 the value reverse-road

  Then I set up a 2nd card statement, corresponding to the same ACL.

  crypto IPSec_map 20 card matches the address encrypt-acl
  card crypto IPSec_map 20 set peer 23.10.10.10

  card crypto IPSec_map 20 set transform-set RIGHT

  card crypto IPSec_map 20 set reverse-road

  My first question is - since Cryptography cards are processed in order, does that mean the first tunnel VPN (map 10) will always be used if its place?

  If so, what happens when the 209.165.201.1 remote peer becomes unreachable? is the tunnel of the 23.10.10.10 peer back automatically?

  What is the best way to reach a VPN site-to-site main and secondary where 209.165.201.1 primary school and 23.10.10.10 is backup and appears only when the primary is down?

  Thank you

  Hello

  As you mentioned that the Cryptography cards are processed in the order.

  If two cryptographic cards have the same "interesting" traffic then the second card encryption is never used (first crypto card is used).

  The best way to get a redundancy is to do the following:

  crypto IPSec_map 10 card matches the address encrypt-acl
  card crypto IPSec_map 10 set peer 209.165.201.1 23.10.10.10

  card crypto IPSec_map 10 the transform-set RIGHT value

  card crypto IPSec_map 10 the value reverse-road

  Note in the example above that you have defined an instance unique card crypto with two counterparts. The first pair will try first and if not answered, the second peer will be used as a backup.

  It will be useful.

  Federico.

• Question of redundancy WLC

  Hello community,

  I have a question about the function of redundancy for both WLC 2106. We have installed on a client 2106 and 6 AP site 2 WLC primary and backup WLC works very well. No customer asks the question if there is an option to copy the guest user of wlan access from the PDC to the backup controller? The entry hall activates a new user on the main controller and if the primary controller fails, so the user did not have access to the WLAN comments.

  Any ideas?

  Thanks for help.

  René

  You can read this question a little differently...

  What, in my view, is mentioned, is that a user GUEST account is enabled on the PDC. When the primary contoller fails to the needs of the user to reauthenicate. If that is the question.

  You must either add comments on both controllers OR purchase WCS and WCS will push the guest on both controllers for you account...

• Questions about SPFILE in ASM 11G

  I did some tests on Oracle 11 G ASM and questions have been raised.
  
  At glance...
  
  I deleted my SPFILE and start the ASM.
  
  echo $ORACLE_HOME
  /U01/app/11.2.0/grid_crs
  
  export ORACLE_SID = + ASM1
  
  sqlplus / as sysasm
  
  Connect to an instance is idle.
  
  SQL > startup
  ORA-00099: WARNING: no file parameter specified for the ASM instance
  ASM instance started
  
  Total System Global Area 283930624 bytes
  Bytes of size 2212656 fixed
  256552144 variable size bytes
  ASM Cache 25165824 bytes
  ORA-15110: none start not mounted
  
  Oracle instance started a mannequin...
  
  SQL > show the dummy parameter
  a modelinstance boolean TRUE
  
  
  Now, I'll create a PFILE file to start the ASM.
  
  VI /home/oracle/asm_init.ora
  * .cluster_database_instances = 2
  ASM1.instance_name =' ASM1'
  ASM1.instance_name =' ASM2'
  * .instance_type = ASM
  *.asm_diskstring='/dev/oracleasm/disks / *'
  *.diagnostic_dest='/U01/app/Oracle '
  * .asm_diskgroups = "DATA".
  * .asm_power_limit = 1
  * .large_pool_size = 12 M
  * .remote_login_passwordfile = "EXCLUSIVE."
  
  
  Now, I'll start instance with new PFILE.
  SQL > startup asm_init.ora = pfile
  ASM instance started
  
  Total System Global Area 283930624 bytes
  Bytes of size 2212656 fixed
  256552144 variable size bytes
  ASM Cache 25165824 bytes
  ASM starts up
  Volume of starts active ASM
  
  
  Now, I create SPFILE from PFILE.
  
  SQL > create spfile ='+ DATA 'from pfile='/home/oracle/asm_init.ora ';
  
  Created file.
  
  From there, one wonders.
  
  I will restart the example using new spfile.
  
  SQL > shutdown;
  Volume of starts disabled ASM
  ASM starts rough
  Shutdown ASM instance
  SQL >
  
  
  I'll check for init in the directory files $CRS_HOME/dbs
  
  LS /u01/app/11.2.0/grid_crs/dbs
  ab_ + ASM1.dat
  hc_ + ASM1.dat
  
  No init file... both nodes
  
  Now, I'll start the ASM with new SPFILE instance.
  
  SQL > startup
  ASM instance started
  
  Total System Global Area 283930624 bytes
  Bytes of size 2212656 fixed
  256552144 variable size bytes
  ASM Cache 25165824 bytes
  ASM starts up
  Volume of starts active ASM
  SQL > show the spfile parameter
  
  VALUE OF TYPE NAME
  ------------------------------------ ----------- ------------------------------
  +DATA/ASM/asmparameterfile/registry.253.732993435 string SPFile
  
  
  
  The most interesting that the second node was also the Forum with model... just restart the ASM to the second node found SPFILE.
  
  
  In GPnP... No SPFILE
  
  $srvctl config asm
  ASM home: /u01/app/11.2.0/grid_crs
  ASM listener: LISTENER
  
  
  
  
  Docs said. ...
  
  
  When an instance of Oracle ASM search a setup initialization file, the search order is:
  
  1. the location of the initialization file parameter specified in the profile of Plug-and-Play (GPnP) grid
  
  2. If the location has not been set in the profile of negotiators, the search order go to:
  
  1. in the instance of Oracle ASM House SPFILE
  
  For example, the SPFILE for Oracle ASM has the following default path to Oracle grid infrastructure home in a Linux environment:
  
  $ORACLE_HOME/dbs/spfile+ASM.ora
  
  2. in the instance of Oracle ASM House PFILE
  
  
  Questions...
  
  How ASM 11 g to find the path of the SPFILE?
  
  When we run the CREATE SPFILE it records the path of the SPFILE in somewhere?
  
  How ASM reads the SPFILE which within a DG who theoretically was not mounted?

  Hi Renon,

  Here's my answer...

  http://aychin.WordPress.com/2011/01/22/Oracle-11gr2-ASM-SPFile-Eng/

  Thank you
  Levi Pereira

• Question of redundancy VPN l2l using 2811 as endpoint devices

  I have a new implementation of VPN L2L passes using two 2811 s than VPN terminal devices. I'll try to use the HSRP address between the public interfaces of both routers as VPN peer address. The problem that I found during the test is that the tunnel will become active and debugs watch the HSRP address as an invalid address to form the tunnel. Have a work-around, or a better plan for redundancy on peering address using similar devices? Thanks in advance.

  Take a look at this doc about IOS IPSec HA.

  http://www.Cisco.com/en/us/docs/iOS/security/configuration/guide/sec_vpn_ha_enhance_ps6922_TSD_Products_Configuration_Guide_Chapter.html#wp1039849

• question of redundency/design interface

  Sorry if this is a stupid question. I went through the forum and a bunch of google searches with no joy.

  I have:

  PIX-active - switch-a

  | ||

  PIX - fo - b switch

  unlikely, I know, but is it possible to configure the network/pix to take account of the active pix & switchb down?

  I was thinking something like backup cmd on IOS, to connect to a network adapter of each pix for both switches.

  Thanks for the research.

  Not a stupid question, but do not forget this: the commercially feasible thing to do when network solutions tolerant for lack of construction is to eliminate the SPFS (single points of failure). In this design, you have no single point of failure. Trying to limit to two points of failure will be very complex to predict behavior impossible. My advice is to move to other areas of your network where you have surely SPFS.  ;)

  HTH

• ASM to the question of the NO - ASM

  DB version: 10.2.0.4.0
  Operating system platform: Solaris 5.10
  
  Currently I have a DB in ASM. Can I take a cold of this DB with RMAN backup and restore it on a machine where the data files will reside in the document to the OS file system format? Does perform additional work required?

  read this links

  use

  (1) backup copy

  (2) switch database

  (3) open

  http://onlineappsdba.com/index.php/2010/03/03/migrating-non-ASM-DB-to-ASM-DB/

  http://download.Oracle.com/docs/CD/B14117_01/server.101/B10734/rcmasm.htm

• Basic question on redundancy as the retention policy enforcement

  DB version: 11 g
  
  I intend to implement a differential incremental backup of my database. My strategy is
  

  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  Tuesday-->     Level 1 backup
  Wednesday-->     Level 1 backup
  Thursday-->     Level 1 backup
  Friday-->     Level 1 backup
  Saturday-->      Level 1 backup
  
  Again, the new weekly backup cycle starts
  Sunday -->     Level 0 backup
  Monday -->     Level 1 backup
  .
  .

  Set on the Recovery window retention policy
  ==========================
  
  I understand that recovery window retention policy: If I set up

  'CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;' 

  This means only these backups that are older than 7 days will be reported as obsolete when executing the command "remove obsolete.
  
  Retention set on redundancy policy
  =============================
  
  But I'm a little confused about the retention set to redundancy policy:
  
  Does

  CONFIGURE RETENTION POLICY TO REDUNDANCY 3;

  say that you keep 3 copies of backups on different locations on disk? How does this fit with my above mentioned incremental backup strategy?

  REDUNDANCY is 'Keep' copies

  The BACKUP is 'Create' copies of

  Copies which exceed the requirement of REDUNDANCY become OBSOLETE.

  Hemant K Collette

• 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.

• WITH REDUNDANCY ASM DISKGROUP

  Hi all

  
  

  REDUNDANCY NORMAL == NEED 2 GROUPS of FAILURE (I'm clear)
  

  
  

  I am trying to create diskgroup with REDUNDANCY NORMAL (only with 2 raw devices).
  

  Command line == > I can't create disk with REDUNDANCY NORMAL group

  Through DBCA == > I can.
  

  
  

  select GROUP_NUMBER, name, ALLOCATION_UNIT_SIZE AU_SZ, STATE, TYPE, TOTAL_MB, FREE_MB, OFFLINE_DISKS from v$asm_diskgroup;
  
  GROUP_NUMBER NAME                                AU_SZ STATE       TYPE     TOTAL_MB    FREE_MB OFFLINE_DISKS
  ------------ ------------------------------ ---------- ----------- ------ ---------- ---------- -------------
             1 ASM_DG_DATA                       1048576 MOUNTED     NORMAL      20472      14142             0
             2 ASM_DG_FRA                        1048576 MOUNTED     EXTERN      10236       7143             0
  
  

  
  SQL> create diskgroup DATA NORMAL REDUNDANCY
    2  failgroup disk1 Disk
    3  '/dev/raw/raw5' name data1,
    4  '/dev/raw/raw6' name data2;
  create diskgroup DATA NORMAL REDUNDANCY
  *
  ERROR at line 1:
  ORA-15018: diskgroup cannot be created
  ORA-15072: command requires at least 2 failure groups, discovered only 1
  
  

  But through dbca, I can create diskgroup only with 2 drives

  

  SQL> select GROUP_NUMBER, name, ALLOCATION_UNIT_SIZE AU_SZ, STATE,  TYPE, TOTAL_MB, FREE_MB, OFFLINE_DISKS from v$asm_diskgroup;
  
  
  GROUP_NUMBER NAME                                AU_SZ STATE       TYPE     TOTAL_MB    FREE_MB OFFLINE_DISKS
  ------------ ------------------------------ ---------- ----------- ------ ---------- ---------- -------------
             1 ASM_DG_DATA                       1048576 MOUNTED     NORMAL      20472      14142             0
             2 ASM_DG_FRA                        1048576 MOUNTED     EXTERN      10236       7143             0
             3 ASM_DATA                          1048576 MOUNTED     NORMAL      40946      40844             0
  
  

  SQL> select a.disk_number, b.group_number, a.path, b.name, b.type from v$asm_disk a, v$asm_diskgroup b 
  where a.group_number=b.group_number;
  
  DISK_NUMBER GROUP_NUMBER PATH                   NAME                           TYPE
  ----------- ------------ ---------------------- ------------------------------ ------
            0            3 /dev/raw/raw6          ASM_DATA                       NORMAL
            1            3 /dev/raw/raw5          ASM_DATA                       NORMAL
            0            2 /dev/raw/raw3          ASM_DG_FRA                     EXTERN
            1            1 /dev/raw/raw2          ASM_DG_DATA                    NORMAL
            0            1 /dev/raw/raw1          ASM_DG_DATA                    NORMAL
  

  ...

  ..

  My question/confusion is only 2 discs,

  I can create a diskgroup (redundancy = normal) using DBCA, but similar operation cannot perform through command line.

  DB version: 10.2.0.5 on RHEL

  Shows your screenshot of the ASMCA you assign disk/dev/raw/raw5 in FailGroup FG1 and disk/dev/raw/raw6 in FailGroup FG2 - two * different * FailGroups. Each disc is in a separate FailGroup.

  Your Interactive SQL command specifies only 1 FailGroup when there is to specify two FailGroups.

  Hemant K Collette

• Remove/add question ASM Disk

  Hi all
  
  I have a small question-
  
  We have an ASM Diskgroup that had 8 drives in it. I removed 2 Diskss and the Diskgroup has been rebalanced. I did not do anything with the disks removed.
  
  They both appear in the target of the DSO as qualified to add in the Diskgroup.
  
  Do I need to re-format/partition/create disc on them before adding them back in? Existing data on the Diskl would cause a problem in the Diskgroup?
  
  This is the first time I'll add back discs that were previously in the Diskgroup.
  
  Thanks in advance for the advice.
  
  Michele

  Hello

  Disks can be assigned to a diskgroup must have the status of 'CANDIDATE' or 'OLD' or 'CONFIGURED '.

  · CANDIDATE - disk is not part of a disk group and may be added to a disk with the ALTER DISKGROUP statement group

  · Provisioned - disk is not part of a disk group and may be added to a disk with the ALTER DISKGROUP statement group. The status of CONFIGURED header is different from the
  Header in the CONFIGURED one CANDIDATE country status means that an additional platform-specific action was taken by an administrator to allow the ASM disk.

  · FORMER - disk was once part of a disk group, but has been removed itself from the group. It can be added to a new group of disks with the ALTER DISKGROUP statement.

  The ALTER DISKGROUP... REMOVE the DRIVE without option statement WAITING returns before the fall and rebalancing are completed. Do not re-use, remove or disconnect drive fell to the HEADER_STATUS column for this disc in the view V$ ASM_DISK changes to the FORMER.

  You can't change anything at the OS level. Oracle will reuse without needs asmdisk perform all administrative tasks at the level of the BONE.

  Kind regards
  Levi Pereira

• The ASM diskgroup in exadata space question

  All,
  
  I have an environment exadata 1 CCR node with 3 knots of strorage.
  
  My RECO ASM diskgroup is constantly showing the problems of space... Always higher than 80%.
  
  I just want to get a Board if I can remove mirroring and recover the space... Even though I know that the result of the deletion of the mirroring...
  
  Can I reduce the diskgroup RECO and create an another diskgroup?
  
  I want just a few ideas to do this without great risk involved...

  You may want to consider these MOS notes for more information on resizing the griddisks:
  Resize diskgroup without downtime to Exadata (Doc ID 1272569.1)
  How to resize the disk drive/grid ASM in environment Exadata (Doc ID 1245494.1)

  As others have mentioned, there is no way to change the level of redundancy in ASM, so you need to delete and re-create the diskgroup if you want to change to redundancy. We strongly discourage the use of EXTERNAL with Exadata redundancy.