Time Machine-triggered Open Directory backups not functional
| Originator: | arubdesu | ||
| Number: | rdar://12943815 | Date Originated: | 2 January 2013 |
| Status: | Open | Resolved: | |
| Product: | Mac OS X Server | Product Version: | 2.2, on 10.8.2 |
| Classification: | Serious Bug | Reproducible: | Always |
Summary: Time Machine is now the supported way to archive an Open Directory Master. There seems to be no purging mechanism for the sparseimages created by the process, and the perl script has a comment saying it will not create a new sparseimage while the current one exists. This leaves servers without any backup for new modifications. Steps to Reproduce: 1. Setup 10.8.2 with Server.app 2.2 and Open Directory 2. run Time Machine with no exceptions (besides entire non-boot volumes), sparseimage is created in /var/backups 3. add user to Open Directory, and/or wait 24 hours(since at least one of the postgresql scripts waits 24 hours to reattempt) 4. run Time Machine again Expected Results: Log file is updated to indicate backup, modification date of sparseimage becomes current Old sparseimage is purged, new one is created and copied by Time Machine Actual Results: None of the above, the contents of the existing sparseimage are not updated Regression: Server.app 2.1 had the same symptoms, and possibly all previous Notes: If I could put the perl scripts into debug mode I would be willing to assist engineering with getting this addressed ASAP
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!