We are trying to figure out if SMO would help us more than SnapCreator. In our environment we do not have archive mode enabled on any of our Oracle databases. So first question does SMO require archiving to be enabled to take a snapshot? SnapCreator Oracle plug-in does not require this.
Next question can SMO shutdown the Oracle database to do a cold snapshot? In our SnapCreator configs we use APP_QUIESCE_CMS01 and APP_UNQUIESCE_CMD01 to stop and start the databases. We also use PRE_EXIT_CMD'S to start the database and listener in the event SnapCreator has an error code.
Third question will SMO help us with database recovery more than SnapCreator. We now just use the snap restore command to recover back to a snapshot.
Any feedback you can provide would be greatly appreciated.
I have passed this thread along to some SMO experts so they can add inputs. I am not sure if SMO supports non-archive log mode. SMO does provide more recovery options than Snap Creator so that could be helpful if you dont want to do recovery manually.
SMO definately overall provides more features for oracle than SC but in the end it is up to the customer to decide what is better, it is certainly nice to have choices
I will say if you dont care about the features SMO offers which SC doesnt have, SC is a lot easier to deal with. This is just my personal experience so others may have a different opinion.
1. Smo can take cold/offline backups. It's an option via the GUI/cli of SMO depending on what is needed.
2. SMO can shutdown the db based on your requirements. If the db is up, it will shutdown the db. It doesn't necessarily deal with the listener.
3. Smo will allow the user to designate the type of recovery. For example, restore data files and control files both, just data files. Other options are available. But since this is a cold backup, those options are not necessary to discus here.
Another option with SMO is its ability to interact with the host os or file systems, luns , an it's ability to clone a database. But as keith mentioned earlier, it depends on customers requirements. And that's it's good to have options.
Another thought is to ensure that the customers storage design and infrastructure can support the functions of SMO as well as meet IMT requirements.
Hope this helps
Thumbed this on the itty bitty keyboard from Greg's iPhone.
What can we do for Snap Creator to help you and make things easier / provide more value? We can certainly add option to backup to handle cold backup which would remove need to do it yourself with APP_QUIESCE_CMDs, APP_UNQUIESCE_CMDs, and PRE_EXIT_CMDS but what else do you need? How do you want things to work?