Could you elaborate which database you referring to? The broker or the directory service one? There are different answers for each.
Thomas
Hi
Right now it is the Broker, but in future SOA projects the Directory DB will also be used.
Could you help out with a answer for this ?
There is very little value in performing a backup of a broker database because it just contains snapshots of messages going through the broker which are gone a few milliseconds later. So any backup will be worthless the same amount of milliseconds later. The right way to deal with messaging resilience is to use replicated broker pairs (CAA).
The story is different for the DS though. Since it contains configuration information that you typically do not want to loose it makes sense to backup the underlying db. That can actually be done in online mode (see dsAdmin.bat(sh)). So best is to plug dsAdmin into a script that is executed before NetApp gets at the data so you will be sure to have a transactionally consistent view of the db (it consist of multiple files which need to be backed up as a set).
Thomas