On Tue, 2012-11-06 at 16:06 +0000, Pete Biggs wrote: > > I thought it was the suggested was of migration between disparate > > releases? > > If I want to move an 'x' Evolution release to say a 'y' release, what > > way would there > > be of doing it without backup/restore? > > The same as you backup and restore all the rest of your data - there is > code in Evo to migrate old settings, so just restoring your backed up > home directory to a new machine will also copy over all the Evolution > settings and data. > > How do you migrate all the data for all the rest of your applications?? > > P. >
Pete, To me it depends on what the application is. If I'm using a database, I would tend to use the databases backup and restore utility (as I do for Informix and Postgresql). If I'm backing up my own applications, I know where the data is and what the implications are, so will happily backup the structure and restore it. Basically, if the application provides a backup and restore, I would tend to use that rather than backing up a 'structure' - as the problem with backup up a structure is in knowing where all the data is. I would assume that the product knows where all its data is, and by using the products backup/restore can't end up with mismatched or missing data/settings. > _______________________________________________ > evolution-list mailing list > [email protected] > To change your list options or unsubscribe, visit ... > https://mail.gnome.org/mailman/listinfo/evolution-list
_______________________________________________ evolution-list mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-list
