I am having a problem reconciling two opposites - not stopping activity on primary database, and creating backup which should be loaded into different (cross) platform. Cross platform migration has a requirement that database which has to be dumped need to be transactionaly quiescent, but I Sybase document ASE-to-ASE Replication Quick Start Guide, in chapter Materialization and Resynchronization, Scenario 3, is saying that "It is assumed that activity cannot be stopped at the primary database while the database dump is in progress."
So, what to do in this situation?