tracker issue : CF-3348487

select a category, or use search below
(searches all categories and all time range)

[ANeff] ER for: Updaters should always create a .car file

| View in Tracker

Status/Resolution/Reason: To Fix//

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 10/17/2012

Components: Installation/Config, Hotfix Installer

Versions: 10.0

Failure Type: Enhancement Request

Found In Build/Fixed In Build: Final /

Priority/Frequency: Minor / Some users will encounter

Locale/System: English / Platforms All

Vote Count: 3

Updaters should _always_ create a .car file of all settings.

As we've seen w/ Update 3 (all tasks deleted on CF start), it should've created a .car file so that people can restore back their scheduled tasks.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3348487

Reason:	BugVerified

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:



Users did not know that creating new tasks would cause their previously-defined tasks to be deleted from neo-cron.xml - b/c users did not know that their previously-defined tasks still existed in neo-cron.xml (b/c Updater 3 hid the tasks in CF Admin). Worse, Standard Edition still lacks the .car creation/deploy feature. I thought there were public rumors that this would be fixed in CF10, but that didn't happen. So these customers likely did not have a .car file containing their scheduled tasks. If they'd already created new tasks (b/c Updater 3 hid them in CF Admin), then these customers experienced data loss as a result of an Updater. That is NOT GOOD! It is *very important* that Updaters ALWAYS create a .car file of all CF Admin settings at the start of the update process. It is also important that Standard Edition include the "Packaging & Deployment > ColdFusion Archives" option in CF Admin starting w/ CF11. Customers who purchased Standard Edition should never again have to suffer due to data loss caused by an Updater.
Comment by External U.
17480 | October 21, 2012 01:34:44 PM GMT
Definitely. Especially given as we've just found out the update process itself cannot be trusted. -- Adam
Vote by External U.
17481 | October 22, 2012 01:56:46 AM GMT
Creating a backup of Coldfusion settings should be part of any upgrading process. This would help for crashes, redeploys, upgrades, downgrades, disaster recovery, configuration testing, etc. So the standard set of configurations can easily be applied to a new server, or restore setting from a failure.
Vote by External U.
17482 | October 22, 2012 06:14:19 AM GMT
I agree that an update should not take us days of lost time to fix what it did when a simple solution would be to actually backup everything before updating anything so it is a very simple rollback should anything happen.
Vote by External U.
17483 | October 22, 2012 11:22:44 AM GMT