EMu Museum Victoria The bird that never sleeps Donna Fothergill David Zhang View from Nicholson St, blades featuring Melbourne Museum venue branding. Photographer: Jennifer McNair Date: June 2007 Source: Museum Victoria MV Images

Overview Why? The decision to make EMu available 24/7 at Museum Victoria How? The Infrastructure making this possible (hardware/scripts/resources) Whats Next? Other Tools Eight-hour day banner, Melbourne, 1856 Date: 1856 Source: Museum Victoria MV Images

The MV EMu Guarantee In the event of: Primary Server Crash System/Database Maintenance EMu upgrades EMu available 24/7 Quote: we can rebuild him, we have the technology -Oscar Goldman

Importance System Integration - MV Images - MVWISE Live Feeds - e.g. The Learning Federation Online collections - e.g. Natural Sciences Core business system EMu Figurine Photographer: David Paul Date: 11/07/2011 Source: Museum Victoria MV Images

+ = EMu Mobile Technology MVWISE EMu in the palm of your hand

MV Images Butterflies on Display: Bugs Alive! Exhibition : Melbourne Museum Photographer: Andrew Curtis Date: 03/09/2010 Source: Museum Victoria MV Images

EMu Core database for all Collection items MVWISE Application for location and inventory control MV Images Digital asset management system for all digital images and audio in the State Collection and other resources Full synchronisation – desktop and handheld devices Data sharing using iMu web services Systems Integration

Live Data Feeds The Learning Federation

Online Collections Search Natural Sciences Collections

Remote Access regardless of connection, location or device

Extending Access Fieldwork Projects/Special Projects Out of Hours Availability Testing environments Where ever Internet Access is available, so too is EMu! Where ever Internet Access is available, so too is EMu! The Moon, from a Photograph taken by the Great Melbourne Telescope, Date: 1874: Source: Museum Victoria MV Images

Primary Server Failure Synchronisation Maintenance/Upgrades Snapshot

Backend processes EMu is synchronised from live server to backup server every hour Full EMu access is available using the EMu client (except during maintenance) Snapshot taken of backup service prior to maintenance During maintenance, the access becomes read-only. Quote: (EMu)... looks good at the front, but has a big backend Anonymous!

Infrastructure Live EMu Server EMu Synchronisation process Changes to live EMu are transported to EMu on the backup server Backup EMu Server notification sent to support staff Data processing is carried out on the backup server for fast synchronisation Primary Server Dedicated 10 GB link and RAM for synchronisation temp space

Synchronisation Performance Tue Aug 30 12:02:05 EST start emu sync to backup server Tue Aug 30 12:02:05 EST stop emu load Tue Aug 30 12:02:11 EST get all the deletions search for new/changed multimedia objects Tue Aug 30 12:02:18 EST start searching new img Tue Aug 30 12:02:19 EST start exporting modified/new records Tue Aug 30 12:02:22 EST move data to backup server Tue Aug 30 12:02:25 EST moving loads directory to backup server Tue Aug 30 12:02:25 EST restart backgroud load Tue Aug 30 12:02:26 EST finish sync on bronte Live EMu service = 75GB

Synchronisation Summary A dedicated private link and RAM for temp space Data processing is deferred to the backup server It takes less than 30 seconds for synchronisation to complete Checks and whistles in place to avoid data corruption

Infrastructure Live EMu Service EMu Snapshot prior to maintenance Backup of live EMu Service Live EMu is synched to the Backup server Backup Server Primary Server Snapshot EMu is read only Snapshot EMu is read only Snapshot created from backup of live EMu Service Service changes from emu to snapshot EMu And back again when maintenance completes Maintenance is carried out on Live EMu Maintenance is carried out on Live EMu

Snapshot Summary Live EMu is synched to backup server The snapshot is taken from the backup live service and placed on the primary server. It is a read only copy of the live service. New connections and/or requests after 5pm are directed to the snapshot When maintenance is complete, the service switches back to the live service. Synchronisation process starts again Camera - Parisio Cantini Empoli, Bellows Glass Plate, circa 1880 Photographer: Taryn Ellis Date: 03/11/2010 Source: Museum Victoria MV Images

Whats Next? Live EMu 24/7 ?

Other Tools Managing our large data files fupdateCompactSort Update load/data file compaction tool fselect Recover Deleted Records getDbRefDetails Delete batches of records in the backend

fupdateCompactSort Example: update 80 fields in 284,297 catalogue records + compaction Example: update 80 fields in 284,297 catalogue records + compaction Data file texload texcompact Index Rebuild Data file Update + Compaction Update + Compaction 1 hour 37 minutes Index Rebuild < 1 minute

getDbRefDetails delete batches of records /usr/local/emu/bin/getDbRefDetails etaxonomy Primary DB = "etaxonomy"; Linked Modules ecatalogue => TaxTaxonomyRef_tab 10 BirCuckooRef 1 IdeFiledAsRef 1 enarratives => TaxTaxaRef_tab 45 SpeLookalikesRef_tab 20 etaxonomy => HisAccNameRef_tab 20 TaxAvailabilityCorrectNameRef_tab 20 HomNameRef_tab 20 TaxAvailabilityCompetingHomRef_tab 20 ClaCurrentNameRef 1 PriTypeAboveSpeciesNameRef 1 ClaHybridParent2NameRef 1 SynNameRef_tab 100

fselect Recover deleted records usage: fselect [options] dbname Options are: -d alternative data file -D print out ins forms -Sstatus record status -c set the status of selected records to current -a analyse -kirn get the records with this irn -un get nth record with this irn -fFile save processed records into File Computer Walking and Talking Photographer: Frey Micklethwait Date: June 2011 Source: Museum Victoria MV Images