Backup - ASM vs regular cooked file system

Use Oracle 11g on Linux.
The disk system is ASM. For instance, the FRA is configured based on a ASM disk group +FRA (along withe multiplexed logs and control files). This is one place for the backup and multiplexing.
Now, I intend to place the multiplexed files also to a second location (disk). For this disk, I have two choices: 1) Use the ASM diskgroup 2) Use the regular datafile (/u01/oracle/oracdata/back).
Good thing about the cooked file system ( I can think) is that I can see the location of the file by going to the file manager and locate the directory of the files, kind of transparent.
For doing so, will it incur the opertion cost in the future? (As compared to the ASM diskgroup, though files somewhat hidden from the view, but Oracle will take care of "everything").
So, any comment on the file system of the second disk? (Oracle ASM vs regular cooked file system).
Thanks

I suggest you continue using ASM and use the ACFS feature.
From 11.2.0.3 I don't use FRA on ASM only, I'm using FRA under ASM/ACFS mount point.
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a multi-platform, scalable file system, and storage management technology that extends Oracle Automatic Storage Management (Oracle ASM) functionality to support customer files maintained outside of Oracle Database. Oracle ACFS supports many database and application files, including executables, database trace files, database alert logs, application reports, BFILEs, and configuration files. Other supported files are video, audio, text, images, engineering drawings, and other general-purpose application file data.
Starting with Oracle Automatic Storage Management 11g Release 2 (11.2.0.3), Oracle ACFS supports RMAN backups (BACKUPSET file type), archive logs (ARCHIVELOG file type), and Data Pump dumpsets (DUMPSET file type).

Similar Messages

DNFS with ASM over dNFS with file system - advantages and disadvantages.

Hello Experts,
We are creating a 2-node RAC. There will be 3-4 DBs whose instances will be across these nodes.
For storage we have 2 options - dNFS with ASM and dNFS without ASM.
The advantages of ASM are well known --
1. Easier administration for DBA, as using this 'layer', we know the storage very well.
2. automatic re-balancing and dynamic reconfiguration.
3. Stripping and mirroring (though we are not using this option in our env, external redundancy is provided at storage level).
4. Less (or no) dependency on storage admin for DB file related tasks.
5. Oracle also recommends to use ASM rather than file system storage.
Advantages of DNFS(Direct Network File System) ---
1. Oracle bypasses the OS layer, directly connects to storage.
2. Better performance as user's data need not to be loaded in OS's kernel.
3. It load balances across multiple network interfaces in a similar fashion to how ASM operates in SAN environments.
Now if we combine these 2 options , how will be that configuration in terms of administration/manageability/performance/downtime in future in case of migration.
I have collected some points.
In favor of 'NOT' HAVING ASM--
1. ASM is an extra layer on top of storage so if using dNFS ,this layer should be removed as there are no performance benefits.
2. store the data in file system rather than ASM.
3. Stripping will be provided at storage level (not very much sure about this).
4. External redundancy is being used at storage level so its better to remove ASM.
points for 'HAVING' ASM with dNFS --
1. If we remove ASM then DBA has no or very less control over storage. He can't even see how much is the free space left as physical level.
2. Stripping option is there to gain performance benefits
3. Multiplexing has benefits over mirroring when it comes to recovery.
(e.g, suppose a database is created with only 1 controlfile as external mirroring is in place at storage level , and another database is created with 2 copies (multiplexed within Oracle level), and an rm command was issued to remove that file then definitely there will be a time difference between restoring the file back.)
4. Now familiar and comfortable with ASM.
I have checked MOS also but could not come to any conclusion, Oracle says --
"Please also note that ASM is not required for using Direct NFS and NAS. ASM can be used if customers feel that ASM functionality is a value-add in their environment. " ------How to configure ASM on top of dNFS disks in 11gR2 (Doc ID 1570073.1)
Kindly advise which one I should go with. I would love to go with ASM but If this turned out to be a wrong design in future, I want to make sure it is corrected in the first place itself.
Regards,
Hemant

I agree, having ASM on NFS is going to give little benefit whilst adding complexity. NAS will carrying out mirroring and stripping through hardware where as ASM using software.
I would recommend DNFS only if NFS performance isn't acceptable as DNFS introduce an additional layer with potential bugs! When I first used DNFS in 11gR1, I came across lots of bugs and worked with Oracle Support to have them all resolved. I recommend having read of this metalink note:
Required Diagnostic for Direct NFS Issues and Recommended Patches for 11.1.0.7 Version (Doc ID 840059.1)
Most of the fixes have been rolled into 11gR2 and I'm not sure what the state of play is on 12c.
Hope this helps
ZedDBA

Opinion on non-clustered file system to offload backups

3 node 11.2 rac using ASM on SAN.
All of the RMAN backups go to +FRA. Any node can initiate RMAN and create backups.
I want to offload the backups from +FRA to a filesystem. Our current backup system can only read cooked file systems.
This LUN also comes from the same SAN. It will have a file system, ext4. It will be visible to all 3 nodes and will be mounted to ONLY the first node. First node will be the one to copy from asm to this filesystem.
If first node is out of commission, I can mount the backup lun to one of the other remaining nodes.
Does this sound like a decent plan or should I go with a clustered file system?
Thanks for you opinions!

Have you looked at using ACFS? Create a very big diskgroup, then create an ACFS volume and finally an ACFS filesystem. create a path on all nodes on which the ACFS filesystem will be mounted.
Example: Using asmca do the following
mkdir /d01/FRA on all systems
DGFRA (4disks at 500G)
Create ACFS volume 1.8T
Create ACFS filesystem mount point of /d01/FRA
set your db_recovery_file_dest=/d01/FRA scope=both sid='*'
Now any node can backup to this FRA location AND any node can copy files to tape or where ever...
This is "supported" as of 11.2.0.3 ( I have used it on 11.2.0.1 and 11.2.0.2 for testing)

ASM Vs File System - Who is best, Why and How ..

How the ASM is better than traditional file system ..? What is the reason behind oracle recommends ASM when we can achieve the same performance in traditional file system ...? Can some one throw some lights on this to understand the purpose of ASM in a better ways when comparing traditional file system.

ASM is better for two basic reasons.
Management and administration. It allows the DBA far better control, with features not found, when using a cooked file system. For example - you need to move the database from an old drive to a newly installed drive on the server. With ASM you can do this while the database is up, running and in-use.
Performance. ASM disks are block devices that are accessed using direct I/O. This bypasses a lot of moving parts that you will typically find in a cooked file system. Raw/direct disk I/O is faster than doing I/O via a kernel file system driver (that may or may not write that data to file on disk).
The con is that ASM is another s/w layer that needs to be installed, and which needs server resources to run. On the modern server, that is not a problem. It's not like running on a couple of sub Ghz CPUs with only 4Gb of system RAM. PCs today have more resources and faster resources than servers of a decade ago.
So there is not much reason for not using ASM.
I'm using ASM on all my database servers. From very small (dual core standalone) to large (12 node RAC). ASM has numerous times saved the proverbial day when there was storage issues, and required storage changes. I would need a lot of sound and hard convincing not to use ASM by default for an Oracle database in today's environment.

Copy Orace file-system database to ASM

Hi,
We are planning to use ASM and migrate of file-system database
How do you move/copy oracle datafiles,logfiles,controlfiles,*.dbf to ASM?
The docs said ASM does not allow OS copy commands :(
Thanks a lot

Thanks a lot Hussein, Arnoud :) I like those docs very short/summarized and easy to understand, unlike other oracle manuals which gives you lots of choices/platforms/versions/ and confusion mixed in one.
By the way I am planning to install a new set of 64-bit EBS R12 on ASM/RAC and leave alone our EBS R12 32bit(filesytem) running. I dont like to migrate it because it so critical
and sensitive to touch.
Just a little clarification :).....When I run EBS R12 installer (database tier side) It ask for
home directories like: /u01/app/orace
My question is I want my database files (.dbf) to be directed to an ASM disk
How do I input it in the Rapidwiz installer? I did not see any options there to use ASM disk.
Thanks again

ASM vs ext3 File system(mount point)

Please suggest which one is better for small databases.
ASM or ext3 File system(mount point)?
Any metalink note.

ASM better if you do not want to play with I/O tiuning, (if you tune ext3 file system it woud be the same from performace view),
but it more compilcated for admininstering database files in ASM then in ordinary file system.
Oracle is recomending to use ASM for database file system.
I woud think if you have some development database and nead a lot of cloning, moving of datafiles its better to use ordinary file system,
so you can use copy OS comands, not so complicated.
If you nead some striping, miroring, snapshoting from ext3 you can use LVM on unix/linux.
I am not sure but I think what striping or miroring is better on ASM then on LVM, becouse ASM is doing it better for databse I/O.

File system in 9i RAC

ASM is recommended for file system and oracle clusterware in 10g RAC, what is the recommended filesystem/cluster in 9i RAC, and which one is commenly used in 9i RAC Environment,

which filesystem and clusterware is recommended while installing 9i RAC?
what would be the best practice for using raw devices, as shared storage. Like keeping different file like controlfile, logfile , datafile and backups of different raw devices?
What could be best practice for LUN configuration for raw devices, like how many LUNs for How many raw devices?
What is the alternative of OCR, VOTING DISK in 9i RAC?
Can i manage 9i RAC while i am connect to OEM as standalone?
lol...too many questions i am asking........

How to convert from ASM to regular filesystem

Hi All,
On our RHEL 5.5 machine we have one disk partition managed by ASM (11.2.0.1.0). We wan't to convert it to regular file system. How can we do it?
Regards,
Vinod

Open a Terminal window and paste the following:
# su - oracle
$ . oraenv
ORACLE_SID = [oracle] ? +ASM
The Oracle base has been set to /u01/app/oracle
$ kfod disks=all
Disk          Size Path                                     User     Group
================================================================================
   1:       9214 Mb ORCL:ASMDISK1                            <unknown> <unknown>
   2:       9214 Mb ORCL:ASMDISK2                            <unknown> <unknown>
ORACLE_SID ORACLE_HOME
================================================================================
      +ASM /u01/app/oracle/product/11.2.0/grid
The above will either show you the device, e.g. /dev/..., or the diskname (ORCL) in case you use ASMLib
$ su - root
# /etc/init.d/oracleasm querydisk -p ASMDISK1
Disk "ASMDISK1" is a valid ASM disk
/dev/sde1: LABEL="ASMDISK1" TYPE="oracleasm"
# /etc/init.d/oracleasm querydisk -p ASMDISK2
Disk "ASMDISK2" is a valid ASM disk
/dev/sdf1: LABEL="ASMDISK2" TYPE="oracleasm"
U sing the info from the previous output, the following will permanently remove devices from ASM and create a file system (ext4) that you can mount. When using fdisk or parted, be sure to use the device name, e.g. /dev/sde and not the partition (/dev/sde1).
# parted -s /dev/sde mklabel msdos mkpart primary 1 -- -1
# parted -s /dev/sdf mklabel msdos mkpart primary 1 -- -1
# mkfs.ext4 -L testdrive /dev/sde1
# mkfs.ext4 -L testdrive /dev/sdf1
You can then mount the file systems, for example:
# mkdir -p /u02
# mount /dev/sde1 /u02
All previous information on the devices will be lost.

IS RAW DEVICES SUPPORTED OVER A CLUSTER FILE SYSTEM

Can raw partions be defined for datafiles after having choosen Cluster file system as storage option for database while creating fresh database using
DBCA?

> Do update on how the partitions have to be defined in either cases?
For both ASM and OCFS, a partition must exist on the disk - it can be of any partition type. Does not matter. Simply that the s/w references a partition and not an entire disk.
So for example, /dev/sdaf and dev/sdag are two shared devices on the cluster (LUNs on the SAN or whatever).
You create a partition on each. E.g
# fdisk -l /dev/sdaf
Disk /dev/sdaf: 36.5 GB, 36573020160 bytes
255 heads, 63 sectors/track, 4446 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdaf1 1 4446 35712463+ 83 LinuxTo use the first device as a OCFS device, you need to build an ocfs file system on it using mkfs.
And then it can be mounted as a "normal" cooked file system mount. Remember that /etc/fstab needs to be updated for mounting it on startup.
To use the second device for ASM, you have two choices. If you have the ASMlib kernel module installed, you can use that to configure a volume label and assign it for use by ASM.
Alternatively, you simply map the device (partition) to a raw device for detection by ASM. E.g.
# raw /dev/raw/raw1 /dev/sdag1Of course, you also need to make this permanent by updating the raw device list config file so that this mapping is performed on reboot. On Linux, this is the /etc/sysconfig/rawdevices file. Also remember that the user and group access for the logical raw device created, must allow ASM full access to it (e.g. use chmod oracle.dba /dev/raw/raw1).
In a nutshell, this is how to raw devices are used as ocfs and asm volumes. (on RHEL specifically, but I expect no major differences in this approach on other o/s's)

ASM RMAN backup to File System

Hi all,
I have a rman backup (datafile and controlfile) which was took in an ASM instance (not a RAC) ORACLE 11.2.0.2 in a Linux server, now I want restore the backup in a new database in windows/Linux OS using general File System storage (single instance rdbms) instead of ASM.
Is this possible?
Can I restrore an ASM rman backup in a file system storage mechanisim in a new server?
Kindly clarify my question.
Thanks in Advance..
Nonuday

Nonuday wrote:
Hi Levi,
Thanks for your invaluable script and blog.
can you clarify me on this query:
I have a RMAN backup taken from ASM and the backup is database and controlf file backup which contains datafiles and controlfiles.
Now I need to restore this on my system and here I dont use ASM or archive log, I use single instance in no archive log mode database.
I have restored the control file from the RMAN controfile backup.
Before restoring the control file I have checked the orginal pfile of the backup database which had parameters like
'db_create_file_dest',
'db_create_online_log_dest',
'db_recovery_file_dest_size',
'db_recovery_dest',
'log_archive_dest'.
Since I am not gng to create a DB in no archive log mode, I didnt use any of the above parameters and created a database.
Now my question is:
If i restore the database and the datafile will get restored and after renaming all the logfiles, database will be opened.
I want to know whether this method is correct or wrong and will the database work as it was working previously. Or do i need create the db_file_recovery and other parameters also for this database.About Parameter:
All these parameters should reflect your current environment any reference to the old environment must be modified.
About Filesystem used:
Does not matter what Filesystem you are using the File (datafile/redolog/controlfile/archivelog/backuppiece) are created on Binary Format which depend on Platform only. So, The same binary file ( e.g datafile) have same format and content on raw device, ASM, ext3, ext2, and so on. So, to database it's only a location where file are stored, but the file are the same. ASM has a different architecture from Regular Filesystem and need be managed in a different manner (i.e using RMAN).
About Database:
Since your database files are the same even using different filesystem what you need is rename your datafiles/redofiles on controlfile during restore, the redo files will be recreated.
So, does not matter if you database are noarchivelog or archivelog, the same way which you will do a restore on ASM is the same way to restore on Regular Filesystem. (it's only about renaming database file on controlfile during restore)
On blog the post "How Migrate All Files on ASM to Non-ASM (Unix/Linux)" is about move the file from filesystem to another. But you can modify the script used to restore purposes;
## set newname tell to RMAN where file will be restored and keep this files location on memory buffer
RMAN> set newname for datafile 1 to <location>;
### swich get list of files from memory buffer (rman) and rename on controlfile the files already restored.
RMAN>switch datafile/tempfile all ;With database mounted use this script below:
I just commented three lines that are unnecessary in your case.
SET serveroutput ON;
DECLARE
vcount NUMBER:=0;
vfname VARCHAR2(1024);
CURSOR df
IS
    SELECT file#,
      rtrim(REPLACE(name,'+DG_DATA/drop/datafile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
    FROM v$datafile;
CURSOR tp
IS
    SELECT file#,
      rtrim(REPLACE(name,'+DG_DATA/drop/tempfile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
    FROM v$tempfile;
BEGIN
-- dbms_output.put_line('CONFIGURE CONTROLFILE AUTOBACKUP ON;'); ### commented
FOR dfrec IN df
LOOP
    IF dfrec.name != vfname THEN
      vcount      :=1;
      vfname     := dfrec.name;
    ELSE
      vcount := vcount+1;
      vfname:= dfrec.name;
    END IF;
-- dbms_output.put_line('backup as copy datafile ' || dfrec.file# ||' format "'||dfrec.name ||vcount||'.dbf";'); ### commented
END LOOP;
dbms_output.put_line('run');
dbms_output.put_line('{');
FOR dfrec IN df
LOOP
    IF dfrec.name != vfname THEN
      vcount      :=1;
      vfname     := dfrec.name;
    ELSE
      vcount := vcount+1;
      vfname:= dfrec.name;
    END IF;
    dbms_output.put_line('set newname for datafile ' || dfrec.file# ||' to '''||dfrec.name ||vcount||'.dbf'' ;');
END LOOP;
FOR tprec IN tp
LOOP
    IF tprec.name != vfname THEN
      vcount      :=1;
      vfname     := tprec.name;
    ELSE
      vcount := vcount+1;
      vfname:= tprec.name;
    END IF;
    dbms_output.put_line('set newname for tempfile ' || tprec.file# ||' to '''||tprec.name ||vcount||'.dbf'' ;');
    END LOOP;
      dbms_output.put_line('restore database;');
    dbms_output.put_line('switch tempfile all;');
    dbms_output.put_line('switch datafile all;');
    dbms_output.put_line('recover database;');
    dbms_output.put_line('}');
---   dbms_output.put_line('alter database open;'); ### comented because you need rename your redologs on controlfile before open database
    dbms_output.put_line('exit');
END;
/After restore you must rename your redologs on controlfile from old location to new location:
e.g
## use this query to get current location of redolog
SQL> select group#,member from v$logfile order by 1;
## and change from <old_location> to <new_location>
SQL > ALTER DATABASE
RENAME FILE '+DG_TSM_DATA/tsm/onlinelog/group_3.263.720532229'
           TO '/u01/app/oracle/oradata/logs/log3a.rdo' When you change all redolog on controlfile issue command below:
SQL> alter database open resetlogs;PS: Always track database in real time using alert log file of database.
HTH,
Levi Pereira

ASM or Regular File System?

I have read few threads regarding ASM/non-ASM file system. I am thinking ASM is easy to maintain when configured, but hard to maintain when move of database to non-ASM etc. can you suggest?
Thanks.

I dont think so.. The question of chosing ASM or not dosn't depend how hard or easy it is, the main thing to know id what is the actual requirement. If you use ASM then it means its raw devices managed by oracle and definitely in order to deal with the ASM files you have to through oracle interface (RMAN) and that disks cannot be seen from OS.
There are plenty of docs available online to move database from ASM to non-ASM and vice versa, if you are good in RMAN then it shouldn't be a problem plus how many time are you gonna move your database?
Daljit Singh

ASM Vs File system

1. With file system, we were able to set some threshold alerts at the OS mount point level. Is this possible with ASM since it is a raw device at the OS level?
2. The ASM directories are logical and is visible ONLY at the oracle ASM level. True?
3. Is cold backup an option with ASM?
4. Is RMAN the only solution with ASM disks?
5. Are there any suggested Hardware snap/clone available for ASM storage?
Thanks for your insight on this.

KR wrote:
1. With file system, we were able to set some threshold alerts at the OS mount point level. Is this possible with ASM since it is a raw device at the OS level?
2. The ASM directories are logical and is visible ONLY at the oracle ASM level. True?
3. Is cold backup an option with ASM?
4. Is RMAN the only solution with ASM disks?
5. Are there any suggested Hardware snap/clone available for ASM storage?1. Not possible from an OS point-of-view. See earlier reply for workaround;
2. Yep, or use asmcmd (from the ASM ORACLE_HOME) or ftp
3. If you use RMAN to cold-backup: yes. You cannot use a regular backup to back up your devices, unless you have designated files as 'disks' to ASM (But who would want that?). In this case you should shut down ASM and backup the file system where these files reside.
4. Yes, it is.
5. That depends on your hardware configuration. It is possible to run ASM on concurrent/shared, host based mirrored volume groups/volumes. If you use SAN technology, you can always verify whether these options are available from the storage manufacturer. However, I would be really careful with these, always taking things down before taking snapshots/flashcopies/clones/whatever you call them.
HTH.
Arnoud Roth

Why would anyone want to use ASM Clustered File system?

DB Version: 11gR2
OS : Solaris, AIX, HP-UX
I've read about the new feature ACFS.
http://www.oracle-base.com/articles/11g/ACFS_11gR2.php
But why would anyone want to store database binaries in a separate Filesystem created by Oracle?

Hi Vitamind,
how do these binaries interact with the CPU when they want something to be done?
ACFS should work with Local OS (Solaris) to communicate with the CPU . Isn't this kind of double work?ACFS dont work with .... but provide filesystem to Local S.O
There may be extra work, but that's because there are more resources that a common filesystem.
Oracle ACFS executes on operating system platforms as a native file system technology supporting native operating system file system application programming interfaces (APIs).
ACFS is a general purpose POSIX compliant cluster file system. Being POSIX compliant, all operating system utilities we use with ext3 and other file systems can also be used with Oracle ACFS given it belongs to the same family of related standards.
ACFS Driver Model
An Oracle ACFS file system is installed as a dynamically loadable vendor operating system (OS) file system driver and tool set that is developed for each supported operating system platform. The driver is implemented as a Virtual File System (VFS) and processes all file and directory operations directed to a specific file system.
It makes sense you use the ACFS if you use some of the features below:
• Oracle RAC / RAC ONE NODE
• Oracle ACFS Snapshots
• Oracle ASM Dynamic Volume Manager
• Cluster Filesystem for regular files
ACFS Use Cases
• Shared Oracle DB home
• Other “file system” data
• External tables, data loads, data extracts
• BFILES and other data customer chooses not to store in db
• Log files (consolidates access)
• Test environments
• Copy back a previous snapshot after testing
• Backups
• Snapshot file system for point-intime backups
• General purpose local or cluster file system
• Leverage ASM manageability
Note : Oracle ACFS file systems cannot be used for an Oracle base directory or an Oracle grid infrastructure home that contains the software for Oracle Clusterware, Oracle ASM, Oracle ACFS, and Oracle ADVM components.
Regards,
Levi Pereira

RMAN copies to ASM and file system

I am on 11g Rel 1 trying to do an RMAN backup with 2 copies of my backup. One copy should go to ASM storage and the other should go to a regular file system.
My RMAN script is:
run {
configure default device type to disk;
set backup copies 2;
configure device type disk parallelism 16 backup type to compressed backupset;
configure channel device type disk format = '+ASMDG2/backups/%d_%T_%U_dump0.bck, /orabackups/oracle/%d_%T_%U_dump0_offload.bck' MAXPIECESIZE 60G;
configure controlfile autobackup on;
backup incremental level=0 database plus archivelog;
delete noprompt obsolete redundancy 1;
exit;
When the backup runs I get:
RMAN-03009: failure of backup command ....etc.
ORA-15124: ASM file name '+ASMDG2/backups/%d_%T_%U_dump0.bck, /orabackups/oracle/%d_%T_%U_dump0_offload.bck' containd invalid alias name...
What is the correct syntax to get the copies to be able to go to ASM disk and regular disk locations?

OK, I see that in the documentation this time. I'll try that for tonights backup and let you know how it works. I'm a bit concerned still because it looks like it wrote fine to the +ASMDG2 location. I would have thought the whole backup would fail but I guess it was able to read the first path...

RAC 10gr2 using ASM for RMAN a cluster file system or a Local directory

The environment is composed of a RAC with 2 nodes using ASM. I have to determine what design is better for Backup and Recovery with RMAN. The backups are going to be saved to disk only. The database is only transactional and small in size
I am not sure how to create a cluster file system or if it is better to use a local directory. What's the benefit of having a recovery catalog that is optional to the database?
I very much appreciate your advice and recommendation, Terry

Arf,
I am new to RAC. I analyzed Alejandro's script. He is main connection is to the first instance; then through sql*plus, he gets connected to the second instance. he exits the second instance and starts with RMAN backup to the database . Therefore the backup to the database is done from the first instance.
I do not see where he setenv again to change to the second instance to run RMAN to backup the second instance. It looks to me that the backup is only done to the first instance, but not to the second instance. I may be wrong, but I do not see the second instance backup.
Kindly, I request your assistance on the steps/connection to backup the second instance. Thank you so much!! Terry

Backup - ASM vs regular cooked file system

Similar Messages

Maybe you are looking for