• Bakup oncesinde database Shutdown NORMAL ya da IMMEDIATE ile kapatilmali.
• Otomatize edilebilecek guvenilebilir bir procedure hazirlayin.
• Parameter ve Password file;lar da backuplanmali.
• Read-only tablespace’lere ait datafile’lar backup’a dahil edilmemeli.
• Database’in kapali oldugundan emin olun aksi takdirde bakup gecersizdir.

1. Backuplanmasi gereken tum file;lari listeleyin:

Svrmgrl> Select * from V$DATAFILE;

Svrmgrl> Select * from V$LOGFILE;

Svrmgrl> Select * from V$CONTROLFILE;

DBA_DATAFILES datafile byte, blok, autoextensibility, status, tablespace ve karakteristik bilgisi verir.

2. Oracle Instance’ini kapatin:

Svrmgrl>Shutdown [NORMAL|IMMEDIATE]

3. Isletim sistemi utilitilerini kullanarak Backup:

• Datafiles
• Control Files
• Redolog Files
• Parameter Files & Password Files

1. Oracle Insatnce’i baslatin

• Archive log mode actif olmali.
• ARCH processi manuel olarak ya da database acildiginda otomatik olarak baslatilmis olmali.

Archivelog modda tek bir datafile ya da birkac datafile’dan olusan tek bir tablespace backuplanabilir. Backup processi bitene dek Checkpoint processi calisamaz. Oracle bloklarindaki ile datafile header’indaki SCN farkli olacaktir. Bu duruma Fuzzy state denir.

1. ALTER TABLESPACE <Tablespace> BEGIN BACKUP;
2. Isletim sistemi utilitilerini kullanarak backup al.
3. ALTER TABLESPACE <Tablespace> END BACKUP;

NOT: SYSTEM, TEMPORARY ve ROLLBACK SEGMENTS’de ayni sekilde backuplanir.

V$BACKUP: File Number, status bilgisi verir. Ornegin:

SVRMGR> select * from V$BACKUP;

FILE# STATUS CHANGE# TIME

---------- ------------------ ---------- --------------------

1 NOT ACTIVE 42048232 02/27/01 04:16:31

2 NOT ACTIVE 42048259 02/27/01 04:16:54

3 NOT ACTIVE 42047471 02/27/01 04:11:13

4 NOT ACTIVE 42048251 02/27/01 04:16:44

5 NOT ACTIVE 42043851 02/27/01 03:59:53

6 NOT ACTIVE 42043852 02/27/01 03:59:53

7 NOT ACTIVE 42048251 02/27/01 04:16:44

8 NOT ACTIVE 42049566 02/27/01 04:30:09

9 NOT ACTIVE 42049055 02/27/01 04:25:23

10 NOT ACTIVE 42048605 02/27/01 04:20:21

11 NOT ACTIVE 42048624 02/27/01 04:20:43

12 NOT ACTIVE 42045547 02/27/01 04:05:19

13 NOT ACTIVE 42049007 02/27/01 04:24:36

V$DATAFILE: Hangi file number’in hangi datafile’a ait oldugunu gosterir

SVRMGR> select file#, name from V$DATAFILE;

FILE# NAME

---------- ------------------ ---------- --------------------

1 /oracle/TIP/sapdata1/system_1/system.data1

2 /oracle/TIP/sapdata1/temp_1/temp.data1

3 /oracle/TIP/sapdata1/roll_1/roll.data1

4 /oracle/TIP/sapdata4/btabd_1/btabd.data1

5 /oracle/TIP/sapdata1/ddicd_1/ddicd.data1

6 /oracle/TIP/sapdata5/poold_1/poold.data1

7 /oracle/TIP/sapdata4/btabd_2/btabd.data2

8 /oracle/TIP/sapdata4/user1d_1/user1d.data1

9 /oracle/TIP/sapdata2/clud_1/clud.data1

11 /oracle/TIP/sapdata4/loadd_1/loadd.data1

12 /oracle/TIP/sapdata3/clui_1/clui.data1

13 /oracle/TIP/sapdata5/docud_1/docud.data1

• Instance startup edildiginde gereklidir..
• Instance ya da Media recovery esnasinda gereklidir.

• ALTER DATABASE [ADD|DROP] LOGFILE
• ALTER DATABASE [ADD|DROP] LOGFILE MEMBER
• ALTER DATABASE [ADD|DROP] LOGFILE GROUP
• ALTER DATABASE RENAME FILE
• ALTER SYSTEM [ARCHIVELOG|NOARCHIVELOG]
• CREATE TABLESPACE
• ALTER TABLESPACE [ADD|DROP|RENAME] DATAFILE
• ALTER RABLESPACE [READ-WRITE|READ ONLY]
• DROP TABLESPACE

• Controlfile backup’i da kendi gibi binary’dir.Asagidaki sekilde backuplanir:

• Trace:

• Init.ora icinde CONTROL_FILE parametresinde control file isimlerini ve lokasyonlari belirtilmeli ve mutaka birden cok ve farkli diskler uzerinde yaratilmalidirlar.

• READ-ONLY tablespace sadece hasara ugramissa recover edilmesi gerekir.
• Eger statusu READ-WRITE’a cekildiyse regular bakuplarla bakuplanmasi gerekir.
• Controlfile READ-ONLY tablespacei tanimiyor ise recovery gerekebilir.