Hi Andreas,
here's my view on some of your questions:
> Suspend_Logwriter
SnapCreator for MaxDB has a Y/N switch for that, you can choose.
Based on my research until now this would not be necessary for Netapp/NFS and if all data files are on the same volume.
For NFS with data files spread over multiple volumes there would be volume-groups.
I think the suspending of the MaxDB logwriter would be used in cases like a SAN where the storage controller has no visibility of
the file system which in that case is owned by the host OS.
> Automatic Savepoint
Not sure, but I think there is a feature in MaxDB to trigger an automatic Savepoint in less busy databases every <x> minutes.
You could always use a SnapCreator Pre-command for that or just test it:
there must be a DB table like V$Savepoints which stores this information.
> MaxDB Versions
I'm not involved is the development of the plug-in but I would expect it to work with all current versions like 7.6, 7.7 and 7.8.
> Case 2 - Point in time recovery
You executed a "recover log #" so I think it will at the end of that log, start the DB and this is what you requested.
If you need a point in time recovery which does not go to the very latest Savepoint (that's case 1) the syntax
would be something like "db_restart -until <date> <time>".
Best Regards, Norbert Sommer