I'd be interested to hear from current DuraCloud users on how you're
scheduling backups. Are you using the Automatic Sync Changes feature to
backup changes as they happen, or are you running an entire backup on a
regular basis? Maybe a combination of the two?
We're getting ready to sign up with DuraCloud and always assumed we would
want to backup any changes ASAP. But, we started to see some dangers in
this approach, e.g., if a staff member inadvertently changes a metadata
value, that error is captured in the backup. A less frequent backup
schedule might give us a chance to catch the error before it replaces the
correct version of the object.
Thanks for your thoughts on this issue,
Marty
Martin Courtois
Repository Manager
Hale Library
Kansas State University
Manhattan KS 66506
[email protected]
785 532 4428
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-general
