The Blind Spot in Every iCluster Refresh
If you've ever kicked off a refresh for a large object and wondered, "Is this going to take 10 minutes or 3 hours?", you're not alone. Until now, iCluster gave you no way to know. There's no duration in the event log, no historical reference, and no way to plan based on past experience.
That creates real problems:
- Scheduling refresh operations is pure guesswork.
- You risk running multi-hour refreshes during business hours.
- There's no data-driven basis for batching or sequencing refreshes.
What Changed
iCluster now logs the actual refresh duration for every object 100 MB or larger, directly to the Event Log on your backup node automatically, after each refresh completes. This works across both Save/Restore and Record-by-Record refresh methods, and covers all object types - databases, programs, IFS files, documents, and more.
No guessing. No surprises. Just real numbers from real refreshes.
Why This Matters
- Plan with confidence - Know whether your refresh will finish within the maintenance window.
- Find slow objects - Quickly identify which objects take the longest.
- Meet recovery goals - Provide accurate evidence for audits and compliance.
- Decide faster in a crisis - Trust the numbers when you need to failover.
No Configuration Needed
This feature works automatically. No new settings, no commands to change. Once you upgrade, your event log immediately starts showing accurate refresh times (HH:MM:SS) for every object 100 MB or larger on the backup side.
Ready to Stop Guessing?
Available from iCluster 9.4.1 onwards. Let your next refresh speak for itself.
