RE: Backup

If you are going to backup datafiles to disk without using any kind of compression, then yes you need enough space in the backup directory to hold the full size of the datafiles. If you use RMAN, the incremental backups should require less space than the complete datafiles. I'm not sure about full backups with RMAN, but they probably require the full size of the datafile (unless RMAN is smart about empty space).

If you don't have adequate disk space to duplicate your production database, you can backup directly to tape. This is what many sites with large databases do (including mine).

HTH,
Sara Wasserman

> -----Original Message-----
> From: Slamet Fusianto [SMTP:yangken_at_cbn.net.id]
> Sent: Friday, July 21, 2000 12:25 AM
> To: Multiple recipients of list ORACLE-L
> Subject: Backup
>
> Thank you (Peter and Eric) who answered my question.
>
> I know that price of tapeback is inexpensive compared to losing data. So,
> as you
> suggested it is better to predict the growth of data for one year (perhaps
> more
> and less I think) ?
> However, as I looked into backup example in metalink, I found out that
> each time
> we do backup (either it is cold or hot backup), the datafile is copied to
> backup
> directory. I am just wandering if that is the case, the server should have
> storage at least same as all datafiles. For example if I have datafiles
> for
> tablespace user which is 500 MB, it means that the server which will be
> 'backup
> destination' should have free space at least 500 MB.
> When the tablespace can contains about 20 GB (for example), how is the
> copy
> process ? I am sorry if the question is so basic, it is because I have not
> faced
> database so huge.
>
> Thank you.
>
>
Received on Fri Jul 21 2000 - 20:19:47 CDT