If using no archive log mode, it means no module is used (like NMDA). It also means that backup you would do would be kind of snapshot and then fs backup of the snapshot (and restore would be crash consistency restore in Oracle view).
I use previous method with PowerSnap and Oracle module. I would strongly suggest to enable archive logs as that is also Oracle suggestion and nowadays I can't imagine why would anyone run it without archive logs turned on.
NetWorker will do whatever you instruct it to do. Question is not if NetWorker supports it, but if Oracle supports it. With NSM - to go back to your original question - and no archivelog mode, this is not consistent and you may get lucky and may not. I doubt this will work ever for busy DB so forget it in such case (as you can't do shutdown due to availability requirements). If this is DB you can shutdown, then yes, it will be quick as snapshot takes little bit of time and you can either use RMAN approach or simple FS backup of the volume - it's your call. I would still insist t enable archive logs and do it "properly".
jeff_browning
2 Intern
•
256 Posts
3079
1
Posted April 23rd, 2014 05:00
Simon:
When in noarchivelog mode, you cannot backup the database hot. You will need to do a cold backup. Networker can be used for that, though. See:
http://dbaworkshop.blogspot.com/2012/07/how-to-backup-database-in-noarchivelog_31.html
Regards,
Jeff