Re: HELP RMAN Best Practices

Van,

1. You can't use RMAN to make a cold database backup. So it doesn't really make sense to bring a database down from RMAN to do then a cold backup.
2. I would run ARCHIVELOG mode for at least your production databases (even not for all of them) to take advantages of RMAN and online database backup.
3. Instead of RMAN I would use Oracle Enterprise Manager for databases startup/shutdown purposes from the OEM's Instance Manager on Windows PC. That way you can save init parameters of all your remote databases in the Windows' repository and manage them through this tool.
4. I am using OEM's Backup Manager to schedule backup jobs for several production databases through RMAN. It is convenient and works well.

Regards,
Eugene.

Van Messner <vmessnerNOvmSPAM_at_discovernet.com.invalid> wrote in message news:13c59873.d5f7f87d_at_usw-ex0108-063.remarq.com...
> Hi Eugene:
>
> I understand it doesn't matter from the point of what is
> possible. But given the issues I raised in terms of copying
> pfiles etc., which is the "better" approach - #1 or #2. I will
> be running RMAN against 20 or so production databases. Some will
> be 24x7, some I can shut down at night for a cold backup.
>
> Van
>
>
> * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network
*
> The fastest and easiest way to search and participate in Usenet - Free!
>
Received on Mon Feb 28 2000 - 09:08:22 CST