-
backup question
Hi all,
I am new to RMAN. I want to do cold backup using RMAN script? How can i do that what will be sample script i should be using?
Please guide!!
Thank
Pat
-
Can do. Google for sample scripts.
Thanks,
Vijay Tummala
Try hard to get what you like OR you will be forced to like what you get.
-
Can i know what is the reason you guys are preffering cold backup?...WHat is the version of database
-
RMAN is a very powerful tool, if your asking such a basic question I would
really STRESS you get a book and read up on the subject. I am not selling
any boks or materials, so its not in my interest if you buy anything or not.
Think about it, what good is a backup, if you don't know how to recover
from it? It's worthless, thats the answer
Having said that, here is a sample script that you can fire off from cron
that does a full backup of your database.
The database being backed up is called "pri" and my rman catalog is kept
in a database called "cat".
To pickup daily changes, you can create another copy of the script and
replace level 0 with level 1.
Good luck
[code]
rman <
connect target sys/sys@GOLD_PRI
connect catalog rman/rman@GOLD_CAT
CROSSCHECK BACKUP DEVICE TYPE DISK;
CROSSCHECK ARCHIVELOG ALL;
RUN {
SQL 'ALTER SYSTEM SWITCH LOGFILE';
BACKUP INCREMENTAL LEVEL 0
FILESPERSET 2 DATABASE
INCLUDE CURRENT CONTROLFILE
PLUS ARCHIVELOG DELETE INPUT;
}
DELETE NOPROMPT EXPIRED BACKUP;
DELETE NOPROMPT OBSOLETE;
EOF
[\code]
-
Hi All,
I would also question why a cold backup is needed. The only reason I have used a cold backup in the past 10 years is when it is more convenient to copy the data files when cloning or upgrading a database. One example of when a cold backup like this is useful is when the two databases are in different vlans, and you can't use RMAN DUPLICATE (version 11g does not have this issue anymore). However, this is rare. That said, here are some tips for using RMAN:
- Use block change tracking. It makes incremental backups very fast
- If RMAN is consuming too much cpu, use the READRATE attribute on the channel to throttle RMAN back
- Use a single, parameterized backup script that applies to all your systems, and push out the files using RedHat Satellite, svn, or some other repository with versioning.
- Be consistent when you specify things in the script, vs. global parameters. Understand the global parameters like REDUNDANCY, AUTOBACKUP, etc, etc. They are really important for your backup strategy.
Hope this helps!
Craig Glendenning
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|