Cloning ASM diskgroups through EMC - Automatic Storage Management

When we clone luns in ASM diskgroup to another set of luns through EMC we were not able to do the following
1. Rename the diskgroup
2. Rename the OMF directories esp the SID directory.
Is there any workaround/solution for this ? 

Not sure what you mean...rename diskgroup...there's no such command.
Are you mounting the clones to the same host? This currently is not possible. 

As explained above renaming a disk group is not possible. Not able to understand your 2nd question.

You cannot rename system dierctories, but you can make aliases and catalogue these aliases (rman catalog). But you need to determine if this is really worth the effort 

Please post more details about your plan ( how you planning the clone, same instance or different instance etc), hope i can explain the detail step. recently i have finished the cloning of ASM database for oracle application.


ASM Instance data files, rman, backup

Forgive my ignorance:
- Are there any ASM files that need to be backed up? In other words should I, can I backup the ASM instance? I am using ASM with a single instance of 10G; no RAC. I installed/configured ASM with DBCA and it ended up on my Windows 2003 Server C:\...
Should I, can I, manage whatever needs to be managed - with regard to ASM - using RMAN? I have the DBConsole (OEM) installed and can see the single instance and ASM detail. But, I see no way of managing any ASM files, storage - basically managing it as a 'true' data base, from OEM?
I've been reading thru the 10G Admin guides and Oracle articles and for some reason I can not find anything that provides succint steps for managing ASM - my bad ;{
Appreciate any pointers here.
Thanks in advance. 
There are no ASM files to backup, just ASM metadata that is persistent on ASM disk structures and gets recreated when you restore a DB backup. This is the same concept as other file systems (you don't back up UFS...).
RMAN is Oracle's preferred method of managing backups and works exactly the same on ASM as any other file system. RMAN is the primary interface to DB backup/restores on ASM.
ASM offers 3 different alternatives for managing the ASM disk groups and files and directories within the disk groups: SQL*Plus interface, OEM and ASMCMD (unix-like commands).
ASM admin guide is the right source of information to manage ASM disk groups, ASM disks and files & directories and the ASM instance.
Other best practices WP can be found on 
Thank you for being clear and direct. What resonated the most with me was your very first line... same concept as other file systems...
Thanks again. 
You might periodically backup the spfile used by ASM to a safe location. Just makes it easier if you have to rebuild the entire node from scratch. 
Hi rh,
How can I backup spfile if its there in ASM.
Is it possible through RMAN or what ?
from metalink , and to approve all said before
An ASM instance is NOT backed up. ASM instance itself does not contain any files but manages the metadata of the ASM disks. Just as you cannot backup or restore this sort of information for a filesystem, you cannot do so for ASM. ASM metadata is triple mirrored, which should protect the metadata from typical failures. If sufficient failures occur to cause the loss of metadata, the diskgroup must be recreated.
Data on the ASM disks is backed up using RMAN. In case of failure, once the diskgroups are created the data (such as database files) can be restored using RMAN.
In other words, The ASM instance is just another volume manager like VxFS. You would not backup the VxFS information just reinstall and rebuild if a failure occurs. This is the same situation with ASM. Also, the disk partitions used by ASM comprise multiple databases. When any action performed will overwrite the database information of all databases making use of this ASM instance.
If a DBA would like to retain information on the ASM system, they can keep record of the settings for the init.ora parameters asm_diskgroups and asm_diskstring. A register document can be created, which essentially would be a spool of the information in V$ASM_..... views.
btw, I beleive all this is covered in the ASM Best Practices guide. 
As an aside, one of the new features in 11g (allegedly!) is the ability to backup ASM disk group metadata. I'm curious what peoples' thoughts are on this. What recovery scenarios could/would require recovery of ASM metadata? Isn't it thrice-mirrored within ASM already? 
Currently if an ASM disk group is lost then it is possible to restore the lost datafile unsing RMAN but you have to manually re-create ASM disk group and any required USER directoreis and templtes.
ASM disk group metadata backup and restore funstionality provides the ability to re-create a pre-exisiting ASM disk group with the same disk paths, disk names, failure groups, attributes, templates, and alias directory structure.
Hope this explains.. 
It does.
I can see the alias backups being helpful. I suppose this is something else to add to the backup/recovery process once 11g rolls around.

ASM Failure / recovery

We have a two node RAC with asm and 2 diskgroups, one for data and one for backups. If we loose ASM on both nodes, will we be able to add the disk/diskgroup to another server and retrive the files there through a new ASM instance? 
Yes, very much. As long as you have disks intact you can recover every bit of it as the ASM metadata is stored on disks itself.
It will simplify the process if you have ASM_DISKString value and ASM disk group value from old SERVER ASM init file. ( but they are not the show stoppers). 
that sounds reassuring.
Could you please elaborate on what steps are required to do this operation?
Thank you. 
In order to mount the ASM diskgroups on another host, the steps look like the install steps where you first configured ASM.
1- Present the SAN/shared-storage to the new host
2- Install drivers if needed
3- chown the raw disks to oracle, chmod them 660
4- Start the ASM instance if it's not already started
5- MOUNT the diskgroups
That's all you have to do. I've been doing it a lot lately and it works great. ASM will do the log replay if needed (at ASM filesystem level).

EMC Snapview clone on ASM LUN on Prod. then bring up clone LUN on Dev.

Hi everyone,
I was able to use EMC Snapview clone to clone of the ASM LUN on the Production server. This LUN is label as ASM5 in the disk group. I fracture the clone and assigned the clone LUN to the Development server. But, when I tried to add the clone LUN to the ASM disk group as ASM11. I get an error said ASM5 is already assigned to the disk group. Any suggestion what I'm doing wrong or the solution to my problem?
First, I think what you are trying to do is a bad idea (unless i misunderstood you). You need to clone ALL of your ASM luns. One at a time is going to mess up your database. <br>But to answer your question:<br>I take it you are using asmlib? If so, you should try /etc/init.d/oracleasm renamedisk<br><br>Hope this helps. Dave.<br> 
thanks for your replied Dave. I understand what you are saying. But, all our databases are assigned to the single ASM disk that is on an individually LUN. For example, if GPROD is on ASM5 and ASM5 is LUN5 on my SAN. Can I just clone LUN5? When I fracture the clone LUN and assigned it to my Dev server. Will that work?
As for renaming ASM disk, can I rename ASM disk before I can add it to the ASM disk group? 
I have worked with organizations who are doing that. They fracture the mirror and then copy the diskgroup to the DR site. If you have the lun comprising an entire diskgroup, this should work. (However if you are only taking a portion of the diskgroup, i still think you will find that it doesnt work. )
You should be able to rename the disk using asmlib before the disk is mounted. This is the Linux library that you will call from the command line. 
Ok, I was able to rename the LUN to the ASM signature I want. But, when I tried to add it to the diskgroup I get this error.
"Failed to commit: ORA-15018: diskgroup cannot be created ORA-15072: command requires at least 1 failure groups, discovered only 0"
I haven't tried the process you're following, but just incase you haven't seen them, there are several whitepapers on using EMC to create ASM clones online at Nitin Vengurlekar is Oracle's foremost expert in this area and has had a hand in authoring all of them. He also co-authored a book on ASM. I haven't read it yet, but I would expect it may have some helpful hints for this type of operation as well--at least for understanding the things happening behind the scenes. 
would highly appreciate... if you Can provide the white paper as i can am not able to find white paper.. 
if you cloned all disks (of one diskgroup) to another server, then you don't need to recreate the diskgroup. Actually it should be sufficient to simply mount it on the development server.
However it is important on the development server that there does not already exist a diskgroup with the same name (otherwise you need to rename the diskgroup before adding it to the development server. There is a new feature in 11.2 to rename diskgroups).
So if you
- Took a snapshot off all disks in a diskgroup and
- cloned and presented the disks to the development server
Then log into the ASM instance and try to see if you can see all (cloned) disks on the development server:
SQL> select * from v$asm_disks
If not: Is your discovery string set correctly?
If you see all, try to mount the diskgroup. (alter diskgroup XXX mount).
What message do you get?
Thanks Sebastian for quick response...Will verify the your instructions and revert back soon with the outcome..
What i am trying is to copy ASM disks from current server (10g r2.0.4 running on linux 4) as a snap-clone (from emc-Nevisphere) and present clone disks to new server ( 11g r2 running on linux 5). the ASM will be new 11gr2 but i will use database version same as using storage option ASM 11gr2. All luns are presented with simmillar configurations.
The only doubt that i have is how ASM on new servers understand the new clone disks are grouped with which disk group name...where is this information stored??(is it in ASM diskheader file?? or somewhere else??).
Is it just the disk string or some other metadata information is required to copy from source to target...
Thanks in advance for excellent assistance.. 
all this information is stored in the first few bytes on the disk (the ASM disk header).
What the ASM instance needs is the correct disk string to find the disks and the correct permissions to be able to access them.
All the rest is then discovered/grouped/organized by the diskheader information.

ASM Storage related questions

I am in the process of moving all my RAC instances with db on veritas volume manager to Oracle ASM.
I have few questions on the entire process and the operational efficiency after the conversion..
I need help in setting up the standard framework around the ASM.
1. on cluster filesystem, i have the entire oracle structures mounted on different filesystems. If i have to move to ASM what should my layout look like...How many diskgroups, directories i need to create so as to optimize the performance and resources?
2. whats the best Backup/Restore plan? In otherwords Should i place the backups in ASM or to disk or to tape? What are its advantages and disadvantages?
3. How often i need to backup the ASM metadata?
4. Where should my ASM instance configured? Same Oracle_home as that of the database instance or not? If in a different oracle_home, should that be in a separate filesystem?
Are there any end-to-end best practise document available, i searched metalink but couldnt find one..
Thanks in Advance
Search OTN for ASM best practices.
1. on cluster filesystem, i have the entire oracle structures mounted on different filesystems. If i have to move to ASM what should my layout look like...How many diskgroups, directories i need to create so as to optimize the performance and resources?
Create different diskgroup for database files. Also configure one diskgroup for FRA to store archivelog's and database backups.
3. How often i need to backup the ASM metadata?
How do you intend to do it?
2. whats the best Backup/Restore plan? In otherwords Should i place the backups in ASM or to disk or to tape? What are its advantages and disadvantages?
Just ensure that you configure FRA with different ASM disk from your datafile disks. Also you will be required to move to tape to take care of your disk's going bad.
4. Where should my ASM instance configured? Same Oracle_home as that of the database instance or not? If in a different oracle_home, should that be in a separate filesystem?
It can be in same ORACLE_HOME or different one.If there are going to be multiple databases on same server, then it will be good if there is separate ASM_HOME. Consider a case that one of db requires a one-off patch to be applied which requires shutdown. In case all db's are sharing same ASM_HOME, then we will have to bring down all databases.

Moving data from local disk to Asm Diskgroup and viceversa

Hello All, I have two node rac setup and now i want to move data from local disk to ASM DiskGroup.Is it feasible, if yes then please mention the way of it. Regards,Ronak
It is possible check below documets, when you said local disk in two node rac, is it NFS shared? Osama Mustafa Oracle Blog: Migrate the database From File System to ASM
Also have a look at
I'm not sure which DB version you are using, it's always good practice to provide all details in question, so that community folks can answer appropriately.  Following note will help you to achieve this from to version, Steps To Migrate/Move a Database From Non-ASM to ASM And Vice-Versa (Doc ID 252219.1) Hope this helps. Thanks!! -Abhijit
Hi,Apology for not providing all details. I am using Two node RAC setup using ASM with ORacle release i have only question like , If i have one text file say "ABC.txt" and now i want this file to be moved or copied to "ASM DiskGroup" then how it can be done ?? Regards.
Adhoc(Non- Oracle) OS files are not supported in ASM.
ACFS is the proper target for non-Oracle files  (like ABC.txt)  in a RAC configuration.  Hemant K Chitale
Hi , Not only normal non-oracle files ,even you can create acfs filesystem on top of ASM diskgroup and keep database files too on ACFS filesystem. + Make sure compatible.advm is or above at ASM diskgroup level ,this will allow to resize acfs filesystem infinite times. Similar concepts is in use in ODA environment. Regards,Aritra
I'm not sure if you just want to check on moving files (e.g. archivelogs) out of ASM, or you're looking to move a tablespace from ASM -> non-ASM or visa versa. Here's an Oracle BLOG on the very subject, albeit you just have to move the other direction:
Hi, What kind of data you want to move from FS to ASM, because if you have a 2Node Rac setup, you would have a ASM diskgroups for OCR (11gr2 or later)  and diskgroups for datafiles, or you are using some certified Cluster File System? generic files or binary files ( NOT Oracle Files like, Datafiles, Controlfiles, archives, redologs, spfile, backup pieces) cannot be stored on Diskgroups normally. You can save generic files in Diskgroups Using ACFS or DBFS and the deploy an New FS base on advm, this is util to store persistence files for Forms and reports HA, or for another Oracle Database issues. i hope this helps.
I want to take backup using datapump on Diskgroup and then want to move that backup to external tape. Is it possible to do ?? Regards
Hi All, Thanks. Found that its possible using package, "DBMS_FILE_TRANSFER". Regards,Ronak
The best way is to use RMAN. Just make a Backup Image then switch database to copy. Much more simple and have few steps compared with any other way.