What about disaster recovery? Assuming I take the approach you suggest and have to restore the cache (with the tested versions) after it's lost in a disaster, is there a way to do that (short of backing it up)? I'd rather be able to keep a list of package versions instead of having to move around entire cache backups across continents.
Thanks,
--Amos
On 11/15/08, Warren Young warren@etr-usa.com wrote:
Amos Shapira wrote:
Is there a way to "freeze" a list of installed packages and exact versions, then tell yum (or any other tool/script) to install exactly these verions either on the same or another systme?
There isn't a need for an explicit feature. Just update one server, test it, then copy all of /var/cache/yum/updates/packages to the other machines. You can then say "rpm -Fvh *.rpm" in that directory to bring that machine up to the same level as the other one.
We don't do it exactly that way. We copy the current package cache to new machines after installation to speed a regular "yum update," as it needs only enough bandwidth to download what's changed since updating the package cache clone. Because of CentOS/RHEL's policy of not upgrading versions, only patching the released version, we haven't had any serious problems by allowing production systems to track the current yum repositories. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos