Deb,
Yes, SMO can do backups of databases in NOARCHIVELOG mode, and it automatically does an offline backups in this case. This is an option that can be set within the scheduler or at the time of the manual backup. (Below is the CLI statement syntax but it is also also an option in gui.)
backup create -profile <profile> {-online | -offline | -auto} {-full | -files <files> [<files> ...] | -tablespaces <tablespaces> [<tablespaces> ...]} [-label <label>] [-comment <comment>] [-protect | -noprotect] [-retain <-hourly | -daily | -weekly | -monthly | -unlimited>] [-verify] [-force] [-quiet | -verbose]
SMO also uses the snaprestore functionality in the case of a restore. SMO is a little picky about there being other files in a mountpoint which it may not know about. If there are other files which are non oracle (even something as simple as a vi or emacs # or .swp file) it will default back to single file snap restore if applicable, or copy the files out of a mounted snap. Not a full quick volume snap restore. It will warn you at the time of profile creation if this is the case.
backup restore -profile <profile> {-label <label> | -id <id>} {-files <files> [<files> ...] | -tablespaces <tablespaces> [<tablespaces> ...] | -complete | -controlfiles} [-recover {-alllogs | -nologs | -until <until>} [-using-backup-controlfile]] [-restorespec <restorespec> | -from-secondary [-temp-volume <temp_volume>] [-copy-id id]] [-force] [-fast [-require | -override | fallback | off]] [-preview] [-quiet | -verbose]
