Answer
Journal-based protection is what typically closes the gap between a nightly save and a true low-RPO target. Once critical libraries are journaled, the software can apply journal receivers to roll a restored copy forward to nearly the point of failure rather than losing an entire day of transactions, which matters enormously for order entry, EDI, or manufacturing systems where a full day's rollback is not tolerable. Buyers should ask whether the platform manages journal receiver rollover, offloading, and retention automatically, since manually administered journaling is a common source of production disk fill emergencies.
It also helps to separate the recovery point conversation from the recovery time conversation, because they drive different technical requirements. A tight RPO argues for journaling and frequent incremental saves; a tight recovery time argues for save-while-active techniques that avoid long application outages during the backup window itself, plus a restore process that has actually been timed. Ask vendors to walk through both numbers for a representative workload: how much data would be lost in the worst case, and how long would the full restore realistically take including IFS objects and security data, not just the library saves. Mixed environments often need different schedules for different applications rather than one blanket policy applied everywhere.