I was able to move my calendar to a new host. I used "tar cvf" to archive the old calendar. The archive was moved using the Mac OS Finder to a USB drive. Then a Remote Access copy to the new computer on a different network. I unpacked the archive on the new host. My calendar had already been established on the new host. I put the old .ics files into my calendar/username folder. I ran "ls -l@" and all the old xattrs were present. The username and group had changed however, so I set them back to _calendar:_calendar. I refreshed the calendar on the client and the appointments appeared. This is great. Moving and restoring files is simple if all the attributes are intact. Next I'd like to set up some rsync scripts for backup. If anybody has some sample scripts please post. Best regards, -- jmca On Dec 20, 2007, at 10:23 AM, Cyrus Daboo wrote:
Hi John,
--On December 20, 2007 1:36:56 AM -0500 John McAdams <johnemac@tekserve.com
wrote:
Are you using OS X server with an OpenDirectory accounting system, or the open source server with xml files for accounts?
OS X Server. The pre-production server was connected to an OD Master. All the user accounts have calendar enabled on the OD Master. We will use the same OD Master in production.
OK, in all likelihood you should not have a problem if you switch the ip/hostname. However, you will probably need to restart that machine and/or possibly re-bind it to the OD master if you used authenticated binding.
Let me know if you run into any problems with this.
If using OS X and you change the hostname, you may need to re-enable calendaring for each user for the new host.
If using XML accounts, then you should not need to change anything.
-- Cyrus Daboo
I was wondering about the xattr on the files. When I run ls -l@ I see some webdav acls. I'd like to learn more about backing up and restoring the files and repairing their permissions in case something goes wrong.
For backup/restore you definitely need to make sure any tool you use is capable of backing up the xattrs. Most command line tools have been enhanced to support that (tar for example).
WRT repairs - right now we do not have any specific tools for doing that. You can manually list or change xattr's using the xattr command line utility, though a recent change we did to the server where we store compressed values in xattrs, will mean you cannot easily do this. However, we do have our own version of the xattr tool on theopen source site that includes an option to deal with the compression.
Obviously we are keen to know what sort of admin tools are going to be required in use, so if you run into a need for anything please let us know. In the short term at least, we can probably help out with a python script to fix things up if needed.
-- Cyrus Daboo