The answer is going to depend on your application.

After the data is collected, is it updated?

If there are no updates, then a mix of partitioning
and read-only tablespaces could save on backups. This
also saves on recovery time as well because the
application can be made available quickly while the
read-only information is being restored in parallel.

Hot backups with RMAN and a good media management
layer are almost a necessity with the size and
complexity of this type of implementation.

Cold backups with a product that can split your
storage mirrors are a solution, but I wouldn't want to
do a 5TB cold backup unless I absolutely had to.

Kevin

--- Yves
<oracledba-ezmlmshield-x29164736.[Email address protected]
wrote:

> Gurus, we are planning the storage and backup
> requirement for a new system.
>
> The system will accumulate 5TB of data over a 4-5
> months period. Now my question is : What kind of
> backup strategy should we implement? The system can
> not be down for more than 1 day if
> Something happens. Should we do a mix of cold and
> hot backups or rely only of hot backup or something
> else?
>
> I've never been in charge of supporting such a large
> system, so any help would be appreciated.
>
> Merci / Thanks
> Yves Leonard,
> Chef de Projet / Project Leader,
> DDS / SDD,
> RH Coats, 13-I
> Téléphone / phone : 613-951-3233,
> couriel / email : yves.[Email address protected]
>
>
>
>
> --------
> website: http://www.LazyDBA.com
> Please don't reply to RTFM questions
> Oracle documentation is here:
> http://tahiti.oracle.com
> To unsubscribe: see
> http://www.lazydba.com/unsubscribe.html
> To subscribe: see http://www.lazydba.com
> By using this list you agree to these
> terms:http://www.lazydba.com/legal.html
>
>


Oracle LazyDBA home page