Is there any Mediaflux documentation on how to implement asset (store) backups?

[Stephen Crawley]

I'm looking for some simple recommendations on using the asset.backup and asset.restore services as part of a Mediaflux backup scheme.  (Or alternatively, recommendations on how to implement disaster recovery for a Mediaflux store.)

The only things I can find are the respective service "help" ... which assumes deep knowledge, and offers a plethora of complicated options ... and a section of the Mediaflux Administration Manual that says "Asset Backup and Restore - (not implemented yet)"

[Neil Edward Killeen]

Stephen

we operate a separate disaster recovery mediaflux instance.

assets are replicated to it on a regular basis via internal scheduled

jobs.    multiple primary Mediaflux instances replicate to this DR instance

It’s hard to recover with just file system ‘rsync’s e.g. as you don’t know what files to

recover if a user should destroy something by mistake

regards

Neil

On 4 Feb 2014, at 1:00 pm, Stephen Crawley <crawley...@gmail.com> wrote:

I'm looking for some simple recommendations on using the asset.backup and asset.restore services as part of a Mediaflux backup scheme.  (Or alternatively, recommendations on how to implement disaster recovery for a Mediaflux store.)

The only things I can find are the respective service "help" ... which assumes deep knowledge, and offers a plethora of complicated options ... and a section of the Mediaflux Administration Manual that says "Asset Backup and Restore - (not implemented yet)"

--
You received this message because you are subscribed to the Google Groups "mediaflux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mediaflux+...@googlegroups.com.
To post to this group, send email to medi...@googlegroups.com.
Visit this group at http://groups.google.com/group/mediaflux.
For more options, visit https://groups.google.com/groups/opt_out.

[Brian O'Connor]

Hello Stephen

This is out of date ... sigh we are in the process of getting better at
documentation :)

In the mean time this is a section from a recent training session we had;

-----
Backup Operations
Asset content should be backed up as usual with enterprise level file
system backup tools. (This is considered outside of Mediaflux’s
responsibility)

The server.database.backup service streams the content of the XODB
database to a compressed archive which can then be restored at a later
date. This service can perform post- backup restoration and validation
of the database at the object level. The compressed database backup can
be created using the following service

> server.database.backup :out file:/path/to/backups/mflux-1234-db.aar

The compressed database backup can be restored using the following service

> server.database.restore :in file:/path/to/backups/mflux-1234-db.aar

The database will be locked while the backup and/or restore this is
happening. (i.e read only)

The following service call creates a special scheduled job called
“database- backup” that will run at 2am.

> server.database.backup.scheduled.create :when < :hour 2 > :url
/mnt/backups :retain 5

The backups are placed in the specific folder and a retention policy has
been added to keep the last five backup files created.

Additional operations can generate notification emails on success and
failure, these require SMTP server properties to be configured.

In addition to the scheduled backup to a compressed binary archive of
the database an additional service exists to create an alternate
recovery archive.

> server.recovery.archive.scheduled.create :when < :hour 2 > :url
/mnt/backups :retain 5

When used with recovery.jar this archive can extract to a human-readable
file-system with XML links to the content files per asset in a structure
that mirrors the Namespace hierarchy.
This solution has largely been replaced by the Desktop Export Wizard
capability but is still supported for good old fashioned “belt and
braces” backup
------------

So;

-Backup the content using normal procedures, how often depends on how
often the content changes
-Backup the mediaflux home dir whenever you change the config
-Backup the database as often as you can afford it to be locked.

You should also schedule a file level backup of the database backups.

The other way to do this is as Neil suggests have a separate replica

--

*Brian O'Connor*
*ARCITECTA*
5/26-36 High Street
Northcote Victoria
Australia 3070
T:+61 3 86838523
M:+61 417746452
http://www.arcitecta.com

[Neil Edward Killeen]

I should also comment that ‘soft delete’ is now available in Mediaflux.
This offers some protection aginst user error. With a DR system as well
you can consider

- Primary : hard delete soft-deleted assets 1 week after soft delete
- DR : hard delete soft-deleted assets 1 month after soft delete

> server.property.get
:property -name "asset.soft.destroy" -default "false" “false"




Neil

[Stephen Crawley]

Correction: the services are "asset.archive.create" and "asset.archive.restore" ...