Refreshing a running Calendar Server instance with latest build
Newbie alert -- please be gentle. I have a home Calendar Server instance that's been happily running on Leopard since November 2007, serving three Leopard iCal clients. For the most part it's been running fine but there have been some odd quirks in calendar event creation lately. It strikes me that it would be prudent to refresh this with the latest build. Here's what I plan to do: 1. Shut down the existing instance 2. Back up my master CalDav directory and all the current calendar data 3. Execute this Subversion command to obtain the latest build 4. Recompile and restart the instance Is this a valid approach? Do I need to worry about any XML metadata changes between the existing calendar data and the current build as of May 23? Regards, Steven
Be careful about usingvtrunk right now as we are doing a lot of work there and some things may break. Use one of the latest Release branches instead for any production system. There should not be any issues with data migration. But bare in mind migration is only one way so you won't be able to downgrade to an older rev after running the newer one. So you may want to take a snapshot of your data directory before the upgrade. -- Cyrus Daboo (Tapped out on my iPhone) On May 23, 2008, at 5:06 PM, Name Withheld <bookondesk@gmail.com> wrote:
Newbie alert -- please be gentle.
I have a home Calendar Server instance that's been happily running on Leopard since November 2007, serving three Leopard iCal clients. For the most part it's been running fine but there have been some odd quirks in calendar event creation lately. It strikes me that it would be prudent to refresh this with the latest build.
Here's what I plan to do: Shut down the existing instance Back up my master CalDav directory and all the current calendar data Execute this Subversion command to obtain the latest build Recompile and restart the instance Is this a valid approach? Do I need to worry about any XML metadata changes between the existing calendar data and the current build as of May 23?
Regards, Steven _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
When you say release branches the only one I see is the 1.3. Do you also mean the prop-? On May 24, 2008, at 8:53 AM, Cyrus Daboo wrote:
Be careful about usingvtrunk right now as we are doing a lot of work there and some things may break. Use one of the latest Release branches instead for any production system.
There should not be any issues with data migration. But bare in mind migration is only one way so you won't be able to downgrade to an older rev after running the newer one. So you may want to take a snapshot of your data directory before the upgrade.
-- Cyrus Daboo (Tapped out on my iPhone)
On May 23, 2008, at 5:06 PM, Name Withheld <bookondesk@gmail.com> wrote:
Newbie alert -- please be gentle.
I have a home Calendar Server instance that's been happily running on Leopard since November 2007, serving three Leopard iCal clients. For the most part it's been running fine but there have been some odd quirks in calendar event creation lately. It strikes me that it would be prudent to refresh this with the latest build.
Here's what I plan to do: Shut down the existing instance Back up my master CalDav directory and all the current calendar data Execute this Subversion command to obtain the latest build Recompile and restart the instance Is this a valid approach? Do I need to worry about any XML metadata changes between the existing calendar data and the current build as of May 23?
Regards, Steven _______________________________________________ calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
Look under /tags/release and grab the 1.2 release there. That location will contain stable releases of the server code. -- Cyrus Daboo (Tapped out on my iPhone) On May 24, 2008, at 10:50 AM, Scott Buchanan <dscottbuch@mac.com> wrote:
This message cannot be displayed because of the way it is formatted. Ask the sender to send it again using a different format or email program. text/plain
Thanks for the tip, Cyrus. Boy, am I glad I backed everything up. This was an interesting failed experiment. After screwing up my initial svn checkout (pulling the trunk instead of the stable release), I killed my existing production directory completely and checked out the CalendarServer-1.2 build into a completely new folder. I then manually copied my backed up data and conf directories into the new CalendarServer directory and attempted to do a ./run -s. At this point, all manner of smoke and springs popped out of the machine, with python complaining about various Build 1.2 objects being mismatched against trunk. Figuring that I couldn't do much worse damage than I had already wreaked, I fired up iCal. Existing calendar data for the existing DCS accounts seemed to be inaccessible, even though I could get responses directly to the DCS port via a browser. Weird. Restored the Nov 2007 instance from backup and everything's running again, albeit on old code. <shrug> I guess I should paddle back over to the shallow end of the pool before I hurt myself. I'll wait until trunk is deemed stable and give this another try then. Regards, Steven On Sat, May 24, 2008 at 11:44 AM, Cyrus Daboo <cdaboo@apple.com> wrote:
Look under /tags/release and grab the 1.2 release there. That location will contain stable releases of the server code.
-- Cyrus Daboo (Tapped out on my iPhone)
On May 24, 2008, at 10:50 AM, Scott Buchanan <dscottbuch@mac.com> wrote:
This message cannot be displayed because of the way it is formatted. Ask the sender to send it again using a different format or email program. text/plain
calendarserver-users mailing list calendarserver-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/calendarserver-users
participants (3)
-
Cyrus Daboo
-
Name Withheld
-
Scott Buchanan