ASM New Features for Release 12.2

Transcription

1

2 ASM New Features for Release 122 Uwe Kirchhoff

3 ASM 122 Features 1 2 Flex Disk Group Extended Cluster

4 Why the Flex Diskgroup? Deployment inflexibility Storage administrator must choose disk group redundancy before database administrator deploys the database Space consolidation inflexibility Different redundancy needs can be satisfied only by multiple disk groups No easy method to consolidate space across disk groups

5 Flex Disk Group Overview ASM DISKGROUP DB-1 FILE-1 FILE-2 FILE-3 DB-2 FILE-4 FILE-5 FILE-6 FILE-7 DB-3 FILE-8 FILE-9 QUOTA GROUP-1 QUOTA GROUP-2

6 Flex Disk Group Creation A new disk group type: FLEX Requirement for compatibleasm and compatiblerdbms: 122 Minimum number of failure groups: 3

7 Flex Disk Group Migration Migration possible from these disk group types: NORMAL and HIGH Requirement for compatibleasm and compatiblerdbms: 122 Minimum number of failure groups: 3 Disk group must be mounted restricted in the duration of the migration

8 Minimum Compatibleasm Value Applies to EXTERNAL, NORMAL, and HIGH redundancy disk groups Ensure customers have a minimum set of ASM functionality Upgrade to 122: CVU pre-check fails if compatibleasm <

9 Flex Disk Groups 1 2 File Groups Quota Groups

10 File Group A File Group describes a collection of files belonging to a particular database, CDB, or PDB Within a disk group, a database, CDB, or PDB has a one to one relationship with a File Group

11 Deployment Scenario Existing CDB + 1 PDB in a Flex Disk Group Create 2 nd PDB Blog File Group Blog automatically created with client name Blog

12 Query the File Groups Query result from joining V$ASM_FILEGROUP and V$ASM_QUOTAGROUP: FILEGROUP NAME CLIENT QUOTAGROUP PRIORITY POWER_LIMIT DEFAULT_FILEGROUP GENERIC MEDIUM 1 1 MCDB MCDB GENERIC MEDIUM 1 2 MCDB_PDB$SEED MCDB_PDB$SEED GENERIC MEDIUM 1 3 BLOG BLOG GENERIC MEDIUM 1

13 File and File Group Relationship FILEGROUP CLIENT_NAME FILE_NAME FILE_TYPE REDUND FG_REDUND MCDB Current CONTROLFILE HIGH HIGH 1 MCDB SYSAUX DATAFILE MIRROR MIRROR 1 MCDB SYSTEM DATAFILE MIRROR MIRROR 1 MCDB TEMP TEMPFILE MIRROR MIRROR 1 MCDB UNDOTBS DATAFILE MIRROR MIRROR 1 MCDB USERS DATAFILE MIRROR MIRROR 1 MCDB group_ ONLINELOG MIRROR MIRROR 1 MCDB group_ ONLINELOG MIRROR MIRROR 2 MCDB_PDB$SEED SYSAUX DATAFILE MIRROR MIRROR 2 MCDB_PDB$SEED SYSTEM DATAFILE MIRROR MIRROR 2 MCDB_PDB$SEED TEMP TEMPFILE MIRROR MIRROR 2 MCDB_PDB$SEED USERS DATAFILE MIRROR MIRROR 3 BLOG SYSAUX DATAFILE MIRROR MIRROR 3 BLOG SYSTEM DATAFILE MIRROR MIRROR 3 BLOG USERS DATAFILE MIRROR MIRROR 3 BLOG TEMP TEMPFILE MIRROR MIRROR

14 File Groups Representation ASM DISKGROUP MCDB MCDB_PDB$SEED BLOG Current256 group_1257 group_2258 SYSAUX262 SYSTEM259 TEMP265 SYSAUX269 SYSTEM268 TEMP271

15 PDB Blog becomes more important ALTER DISKGROUP DG1 MODIFY FILEGROUP blog SET 'power_limit'='32'; ALTER DISKGROUP DG1 MODIFY FILEGROUP blog SET 'priority'='highest'; FILEGROUP NAME CLIENT QUOTAGROUP PRIORITY POWER_LIMIT DEFAULT_FILEGROUP GENERIC MEDIUM 1 1 MCDB MCDB GENERIC MEDIUM 1 2 MCDB_PDB$SEED MCDB_PDB$SEED GENERIC MEDIUM 1 3 BLOG BLOG GENERIC HIGHEST 32

16 PDB Blog becomes more important (cont ) ALTER DISKGROUP DG1 MODIFY FILEGROUP blog SET 'datafileredundancy'='high'; FILEGROUP CLIENT_NAME FILE_NAME FILE_TYPE REDUND FG_REDUND BLOG SYSAUX DATAFILE MIRROR HIGH 3 BLOG SYSTEM DATAFILE MIRROR HIGH 3 BLOG USERS DATAFILE MIRROR HIGH 3 BLOG TEMP TEMPFILE MIRROR MIRROR

17 PDB Blog After Rebalance FILEGROUP CLIENT_NAME FILE_NAME FILE_TYPE REDUND FG_REDUND BLOG SYSAUX DATAFILE HIGH HIGH 3 BLOG SYSTEM DATAFILE HIGH HIGH 3 BLOG USERS DATAFILE HIGH HIGH 3 BLOG TEMP TEMPFILE MIRROR MIRROR

18 File Group Creation PDB and File Group are associated by PDB name and GUID File Groups can be manually created to customize properties prior to PDB creation During PDB creation if a File Group with the same PDB name and GUID exists, it is used Otherwise a new File Group is created automatically

19 File Group Redundancy Redundancy specification File Group level File Group and File Type level UNPROTECTED, MIRROR, HIGH Data availability maintained after temporary double failures for MIRROR files, for example: ASM enforces disk online ordering to avoid data loss ASM prevents manual offline of disks that will result in data loss

20 Flex Disk Groups 1 2 File Groups Quota Groups

21 PDB Blog Needs More Space ALTER DISKGROUP DG1 ADD QUOTAGROUP blog SET quota =200T; ALTER DISKGROUP DG1 MODIFY FILEGROUP blog SET quota_group = blog ; FILEGROUP NAME CLIENT QUOTAGROUP PRIORITY POWER_LIMIT DEFAULT_FILEGROUP GENERIC MEDIUM 1 1 MCDB MCDB GENERIC MEDIUM 1 2 MCDB_PDB$SEED MCDB_PDB$SEED GENERIC MEDIUM 1 3 BLOG BLOG BLOG HIGHEST 32

22 Move File Group to a Quota Group ASM DISKGROUP MCDB Current256 group_1257 group_2258 MCDB_PDB$SEED SYSAUX262 SYSTEM259 TEMP265 BLOG SYSAUX269 SYSTEM268 TEMP271 GENERIC (50TB) BLOG (200TB)

23 Move File Group to a Quota Group ASM DISKGROUP MCDB Current256 group_1257 group_2258 MCDB_PDB$SEED SYSAUX262 SYSTEM259 TEMP265 BLOG SYSAUX269 SYSTEM268 TEMP271 GENERIC (50TB) BLOG (200TB)

24 Move File Group to a Quota Group ASM DISKGROUP MCDB Current256 group_1257 group_2258 MCDB_PDB$SEED SYSAUX262 SYSTEM259 TEMP265 BLOG SYSAUX269 SYSTEM268 TEMP271 GENERIC (50TB) BLOG (200TB)

25 Quota Management With 122, ASM provides Quota Management Quota Group represents the permissible space usable for a collection of File Groups Every File Group belongs to a Quota Group Default Quota Group when one is not specified Quota enforced on file creation, file resize, redundancy change, and database clone

26 Access Control List ACL must be enabled SYSASM can create, drop, or modify any File Group SYSDBA can create, drop, or modify File Groups it owns SYSASM can change ownership of a File Group Only SYSASM can create, drop, or modify Quota Groups Only SYSASM can assign a File Group to a Quota Group

27 Access Control List Access Control Lists are not enabled by default ACLs do prevent a database owner from inadvertently deleting an ASM file in the same disk group belonging to another database when properly configured ASM Compatibility must be set to 112 or higher Job role separation must be implemented for ACls The ACL uses the OS id and groups to control file access privileges ACLs can be managed with SQL or ASMCMD commands, or through Enterprise Manager

28 ASM 122 Features 1 2 Flex Disk Group Extended Cluster

29 What is an Extended Cluster? A geographically separated cluster for high availability Nodes and storage associated with each site Oracle ASM is used to mirror data between independent storage arrays 3 rd Voting File configured on NAS

30 Extended Cluster Motivation No integrated support for Extended Cluster pre 122 Customers configured clusters following procedures in Oracle White Papers No support for Extended environment using Oracle Engineered Systems Lack of support for an Extended Cluster is a barrier to entry in EMEA

31 Extended Cluster Overview Extended Cluster is a choice in 122 Standalone Cluster Install Support for 3 sites [122010] Site identified by Name Site Name are case insensitive and have same restrictions as a Cluster Name INSTALL flow allows: Associate nodes with a site Associate storage (failure group) with a site Disk Group redundancy can be EXTENDED, FLEX, NORMAL, or HIGH EXTENDED disk group must have 3 sites

32 Extended Cluster Architecture NODE 1 NODE 2 Standalone Extended Cluster NODE 3 NODE 4 DB1 DB2 DB3 DB4 +ASM1 +ASM2 QFG +ASM3 +ASM4 SITEC SWITCH FG1 FG2 FG3 FG4 FG5 FG6 SITEA SITEB

33 Extended Cluster ASM CSS Integration Supports more than 5 CSS voting files (VF) Existing CSS VF flat voting file approach does not handle all failures CSS VF uses hierarchical voting Access to majority VFs in the site gets a Site vote [SITE LOCAL] Need majority Site votes [GLOBAL] VF discovery informs CSS about the Site where it is configured

34 Extended Cluster CSS Voting File Loss of all VFs on a Site Standalone Extended Cluster NODE 1 NODE 2 GLOBAL VOTES 2/3 DB1 DB2 NODE 3 NODE 4 DB3 DB4 +ASM1 +ASM2 QFG +ASM3 +ASM4 SITEC 1/1 SWITCH FG1 FG2 FG3 FG4 FG5 FG6 SITEA 0/3 SITEB 3/3

35 Extended Cluster CSS Voting File Tolerate Loss of 4 VFs Standalone Extended Cluster NODE 1 NODE 2 GLOBAL VOTES 2/3 DB1 DB2 NODE 3 NODE 4 DB3 DB4 +ASM1 +ASM2 QFG +ASM3 +ASM4 SITEC 1/1 SWITCH FG1 FG2 FG3 FG4 FG5 FG6 SITEA 0/3 SITEB 2/3

36 Extended Cluster CSS Voting File Loss of VFs from 2 Sites Standalone Extended Cluster NODE 1 NODE 2 GLOBAL VOTES 2/3 DB1 DB2 NODE 3 NODE 4 DB3 DB4 +ASM1 +ASM2 QFG +ASM3 +ASM4 SITEC 0/1 SWITCH FG1 FG2 FG3 FG4 FG5 FG6 SITEA 2/3 SITEB 3/3

37 Extended Cluster CSS Voting File Loss of 3 VFs from 2 Sites Standalone Extended Cluster NODE 1 NODE 2 GLOBAL VOTES 1/3 DB1 DB2 NODE 3 NODE 4 DB3 DB4 +ASM1 +ASM2 QFG +ASM3 +ASM4 SITEC 0/1 SWITCH FG1 FG2 FG3 FG4 FG5 FG6 SITEA 1/3 SITEB 3/3

38 Extended Cluster ASM CRS Integration ASM instance default cardinality is 4 CRS will try to distribute ASM instances across sites Support storage split resolution QUARANTINE one of the sites ALL ASM clients on the QUARANTINED site are stopped and disabled User can ONLINE a site when storage access has been restored

39 Extended Cluster ASM Exadata Integration Typical configuration is 3 sites 2 Exadata data Sites with compute and storage 1 quorum Site on NAS CELLCLI support to associate a CELL to a Site %cellcli -e alter cell sitename= <site name> CELLCLI support to change the site GUID %cellcli -e alter cell siteid= <site GUID> Root Scripts discover this association and configure disk groups

40 Extended Cluster Conversion A 121 stretch cluster can be converted to EXTENDED after upgrading to 122 using a documented procedure

41