I was asked to deliver a backup-script for a windows-database. However I'm not a o.s.-scripting guru at all and certainly not on Windows, I came to the following script. It looks a lot like the one I use on Linux, just translated it into a .cmd-file. The challenge was to get it in one-command file.
Consider this, you've got no DataGuard at your disposal. Single node, relying on your RMAN-backup on disk, which is fortunately copied to tape. Now your complete node is burning down. What's is left is your RMAN-backup. In a bad scenario you'll have to restore this to another node.
It is considered a skill every DBA should have, cloning / duplicating a database with RMAN. My own basic checklist through an example: Cloning of the DEVDB on the node LARRIE to node ELLISON, new database name DEVDBNEW
Zo’n 6 keer uitgevoerd op een ontwikkel-database: restoren via rman naar een bepaalde tijd. 7e keer gaat het restore-gedeelte goed, recovery niet: RMAN-06053, missing log – terwijl die er toch echt is naar mijn bescheiden mening. Database versie 10.2.0.3 op Suse 9.
A proper backup is the base for a well and relaxed administration of yout databases.What follows is a backup-script which I use for several customers. It's backing up all in the same directory and I tested the restore frequently.