We are evaluating ResourceSpace 11 for approximately 1.45 million assets and 15 TB of originals currently managed by Extensis Portfolio on Synology. Our proposed self-hosted architecture uses cloud Linux/MariaDB with cloud-local previews, a read-only Synology StaticSync tree for frozen legacy originals, and a separate writable Synology mount for new ResourceSpace-managed originals using $originals_separate_storage.
Has anyone operated this combination of read-only StaticSync legacy resources and native managed uploads in the same installation? After the initial catalog and freeze, is leaving StaticSync unscheduled a supportable pattern? We would also appreciate current experience with MariaDB search performance near this scale and operational safeguards when a remote originals mount becomes unavailable.