I hope this helps:
Note: If you have any Service Guard Clustering there are some manual things that you have to do to enable SMO to do its magic. I will not go into that unless you have a ServiceGuard Cluster environment.
If SG clustering is not your situation things should be easier -- ( I say won't straight forward)
A new database install is the best situation, so I'll start there.
1) Make sure your volumes are sized properly.
2) Make sure to brake your data base up into parts:
- Lun for CTRL files
- Lun for data files
- Lun for archive files
- Lun for temp files
Depending on what you choose for your space management software on your server:
2) A disk files system setup
These choices will determine what SMO has to do to take snapshots and restore the the database.
SMO can do either one its just in my experience, I have had to deal with ServiceGaurd Clustering which makes things a bit more complicated in terms of restoring luns to a previous backup in an LVM configuration. There are specific commands used for clustered filesystems when using HP LVM. This is my current issue I need to find out where SMO create the scripts to export and import VG's. Its seems now that SMO is building a script but to handle serviceGuard is missing an option in the command.
However if you do not have SG to deal with you should be fine. SMO works great! But you have to be sure you include the DBA in all discussions as they will be the ones using and having to really understand whats going on behind the scenes.
I had to have multiple meetings to explain the snapshot technology with the database team. We also created a test database to allow the Database folks an opportunity to get used to the technology and eventually come to like it.
Thats all I got ...
Ask questions as you get them --- and hopefully I can help further.