I've problems to run DB2 snaps using SnapCreator 3.3.0 to get consistent DB2 snaps. Environment is as follows. SnapCreator is running on a dedicated 2008 x64 VM. DB2 is running on a 2003 Ent x64 VM where also SnapDrive 6.3 is running.
Here the problem I have. The DB2 is not set into the write suspend mode. When the job start to quiesce the DB2 on the DB2 server a dos window opens where it says
'-tvf' is not recognized as an internal or external command,
operable program or batch file.
Same window pops up when the unquises command should run
Also in the db2diag log file no info about suspended tablespaces etc. can be found.
This creates blank dataset. It is up to you to then go into PM and configure dataset. First you need to set protection policy. Then you can either import existing relationships or let PM provision on secondary and setup relationships. Once this is done you must configure DFM_DATA_SET correctly.
If I had in my data set snapcreator_dataset the following: filer1->vol1/qtree1, filer1->vol2/qtree1 it would like like this
You will only ever enter volumes never qtrees in DFM_DATA_SET, SC figures out dataset members on its own.