RMAN, how to schedule a backup of the huge table? [message #207138] |
Mon, 04 December 2006 04:46 |
dendroid66
Messages: 4 Registered: September 2006 Location: Belgium
|
Junior Member |
|
|
Hello,
I have a huge table (300 Gb) which stands for keeping some statistical data. It is partitioned to keep last 90 days statistic, partitions are ranged by time, so one day - one partition, located in one TABLESPACE. With time being all outdated partitions would be dropped and the new ones would be created.
1. Could you advise which kind of backup can be applied that the daily backup will not last more than two, maximum 3 hours (I have SUN V440).
2. Should I do a refactoring of my data model? (like putting each partition in each own TABLESPACE).
3. Can I use TSPITR without FULL DB BACKUP?
4. Is it possible to backup only a certain number of partitions?
P.S. For instance, I can do daily backup of 3,3Gb which lasts
about 20 min. with RMAN to local disks.
|
|
|
|
|
Re: RMAN, how to schedule a backup of the huge table? [message #207181 is a reply to message #207177] |
Mon, 04 December 2006 08:06 |
dendroid66
Messages: 4 Registered: September 2006 Location: Belgium
|
Junior Member |
|
|
I have Oracle 9i.
Ok, suppose each partition is located in a separate tablespace,
like TS0001,TS0002, ... ,TSXXXX.
CREATE TABLESPACE TS0001
DATAFILE 'ts0001.dbf' SIZE 10M DEFAULT STORAGE (INITIAL 1M NEXT 1M PCTINCREASE 0) ONLINE;
CREATE TABLESPACE TS0002 DATAFILE 'ts0002.dbf' SIZE 10M
DEFAULT STORAGE (INITIAL 1M NEXT 1M PCTINCREASE 0) ONLINE;
CREATE TABLESPACE TS0003
DATAFILE 'ts0003.dbf' SIZE 10M DEFAULT STORAGE (INITIAL 1M NEXT 1M PCTINCREASE 0) ONLINE;
CREATE TABLE tstest
(ri NUMBER(10), updt NUMBER(10)) PARTITION BY RANGE (updt)
(PARTITION P01112006 VALUES LESS THAN (10000) TABLESPACE TS0001 ,
PARTITION P02112006 VALUES LESS THAN (20000) TABLESPACE TS0002 ,
PARTITION P03112006 VALUES LESS THAN (30000) TABLESPACE TS0003 );
The data is not supposed to be modifed (only INSERT and SELECT).
All the partitions prior to the current date are only for SELECT (but actually they are not in the READONLY state).
So I have a couple of questions.
1. What should be done to backup my "tstest" table ?
2. Is it sufficent to do the next as a daily backup procedure:
rman nocatalog
connect target;
run {
allocate channel ch1 type disk format='bu1/%u.%p';
backup tablespace TS0001; #TS0001 is a subject of calculation...
copy
datafile 26 to 'bu1/df_1.f',
current controlfile to 'bu1/cf.f';
}
How to determine the datafile number automatically (26 in this case)?
3. Do I really need my control file being backed up daily (to restore the table structure)?
4. How do I restore the data after erroneously dropped tablespace, table or partition ?
5. Is there a way to do a backup incrementally, so the first time it will do the full table backup, next time - only the difference
6. How to restore with p.5 (if possible) taking into account p.4.
|
|
|
|
|
|