Hello;

No.

You should run RMAN just like before.

Do you want to rm old archive from the standby? I would use FRA to do it.

http://emrebaransel.blogspot.com/2009/03/delete-applied-archivelogs-on-standby.html

And

Emre Baransel - Oracle Blog: Recover Dataguard With Lost Archivelogs

Best Regards

mseberg

Hello;

If you need to reduce load on the Primary than run it on the Standby. Otherwise just run it on the primary side. But one of the other, no need for both.

This white paper may help:

http://www.oracleimg.com/technetwork/database/features/availability/rman-dataguard-10g-wp-1-129486.pdf

Best Regards

mseberg

Hello again;

CONFIGURE ARCHIVELOG DELETION POLICY and use the FRA area for Archive and backups on both sides.

This may help:

http://joordsblog.vandenoord.eu/2011/05/rman-configuration-in-data-guard.html

Best Regards

mseberg

If you set the deletion policy you can also just run something like this too:

delete noprompt ARCHIVELOG UNTIL TIME 'SYSDATE-8';

If the Archive is still needed it will throw a warning.

Best Regards

mseberg

Here are a few things to consider....

> Since I am confident that I have a standby running, I stopped running RMAN backup anymore. Is this a good practice, to rely only on standby?

I do know DBA's that do that. But my general feeling is the more backup's the better (within reason of course).

Have you documented your recovery requirements? The reason I ask is depending on what you may be required to recover from, you might need that RMAN backup. Some companies have to be able to get to data from last year for compliance reasons. So they need to be able to recover from last year's backup. Your standby won't handle that situation.

> Where should I run RMAN backup? on Primary or Standby or both?

First and foremost, that depends on where you would need that backup.  If you need it to restore for compliance purposes, as I suggest above, then you would want the backup physically located at the site where you would perform the restore. For many companies, this is the primary data center. For my company and some others, we keep our non-production environment at our DR site. So we would restore at the DR site and I would want the backup at that location. I would hate to have my backup of my multi-terabyte database at one site and need to restore it at the other site. I would then have to figure out how to ship my multi-terabyte backup between sites.

Cheers,
Brian

If you have active dataguard license then you do not need to back from production at all. Do your backup from standby database.

For archivelog deletion you can add something like below to your backup script, do cross check first.

RMAN> delete archivelog all backed up 2 times to sbt;

RMAN> configure archivelog deletion policy to backed up 2 times to device type sbt;

Thanks

Monowar

Since I am confident that I have a standby running, I stopped running RMAN backup anymore. Is this a good practice, to rely only on standby?

I sit good practice....no.  RMAN is for backups and dataguard is typically for diaster recovery.

If data is deleted from the primary database (I seem to remember this happening recently), this would be replicated to the standby, in which case having a standby would not help you (unless you have an apply lag).  Having RMAN backups would.