Every time I have to recover my old 8.1 system from backup, I have to go back out to the web and pull down a large number of updates. Recently, I trashed it when I was trying to create a disaster recovery backup so I could move up to the latest SuSE version. There are over 60 package updates out there that I now have to pull down, mostly security related. Some time over the past 2 /12 years, there were two YOU package updates. It seems like lots of things (maybe everything) that were patched after those updates are not recoverable from a YAST backup (at least I think that's the cause of this). I'm wondering if there's a way to backup ALL of my packages separately so that I can recover them from that backup after I recover my system itself. That would sure save me a lot of time and effort in my recovery process. I may very well trash this thing again before I get this disaster recovery process in place and I will want to test that recovery before I move on to a later version, so I could very well trash it then. I looked into some of the RPM commands, but didn't find one to back up packages. I would think there would be a way to do that built right into RPM (but maybe I'm wrong). Packages SEEM to be spread out through multiple directories instead of all being in one single location (isn't that true?). If (when) I hose myself again, I would like for the recovery to be a little less painful. Any help appreciated. Greg Wallace
On Tuesday 03 May 2005 12:37 am, Greg Wallace wrote:
Every time I have to recover my old 8.1 system from backup, I have to go back out to the web and pull down a large number of updates. Recently, I trashed it when I was trying to create a disaster recovery backup so I could move up to the latest SuSE version. There are over 60 package updates out there that I now have to pull down, mostly security related. Some time over the past 2 /12 years, there were two YOU package updates. It seems like lots of things (maybe everything) that were patched after those updates are not recoverable from a YAST backup (at least I think that's the cause of this). I'm wondering if there's a way to backup ALL of my packages separately so that I can recover them from that backup after I recover my system itself. That would sure save me a lot of time and effort in my recovery process. I may very well trash this thing again before I get this disaster recovery process in place and I will want to test that recovery before I move on to a later version, so I could very well trash it then. I looked into some of the RPM commands, but didn't find one to back up packages. I would think there would be a way to do that built right into RPM (but maybe I'm wrong). Packages SEEM to be spread out through multiple directories instead of all being in one single location (isn't that true?). If (when) I hose myself again, I would like for the recovery to be a little less painful. Any help appreciated.
Greg Wallace
/var/lib/YaST2/you/mnt/i386/update/9.2 (adjust for 8.1) is where all the info is stored IF you aren't selecting the delete-after-download option when running YOU. Somewhere in the list archives and online at Novell.com you'll find info on how to create the patch CD to do what you want without Internet access. Stan
On Tuesday 03 May 2005 01:37 am, Greg Wallace wrote:
Every time I have to recover my old 8.1 system from backup, I have to go back out to the web and pull down a large number of updates. Recently, I trashed it when I was trying to create a disaster recovery backup so I <big snip>
You should be able to run your current packages off to a CD or other location. I don't do that but I do use the packages on one machine to update others.... Here's the script I use: #!/bin/sh rsync -auvzr -e ssh <mastermachn>:/var/lib/YaST2/you/mnt/i386/update/9.2/ /usr/local/update/i386/update/9.2/ (note, there are two lines to the above script... watchout for folding in your email program) The thing to note above are the directory structures. <mastermachn> is the machine that gets updated from SuSE sites directly. The /var/lib/YaST2........... structure is where the packages are kept (along with a lot of info about the updates) By copying that structure and its files to another machine, using the /usr/local/update/...... structure, I can point YOU to the copied structure using the "user defined" update site and can then update another machine without any more downloading of packages. Questions?
On Tuesday, May 03, 2005 4:54 AM Bruce Marshall wrote:
On Tuesday 03 May 2005 01:37 am, Greg Wallace wrote:
Every time I have to recover my old 8.1 system from backup, I have to go back out to the web and pull down a large number of updates. Recently, I trashed it when I was trying to create a disaster recovery backup so I <big snip>
You should be able to run your current packages off to a CD or other location.
I don't do that but I do use the packages on one machine to update others....
Here's the script I use:
#!/bin/sh rsync -auvzr -e ssh <mastermachn>:/var/lib/YaST2/you/mnt/i386/update/9.2/ /usr/local/update/i386/update/9.2/
(note, there are two lines to the above script... watchout for folding in
your email program)
The thing to note above are the directory structures. <mastermachn> is the machine that gets updated from SuSE sites directly. The /var/lib/YaST2........... structure is where the packages are kept (along with a lot of info about the updates)
By copying that structure and its files to another machine, using the /usr/local/update/...... structure, I can point YOU to the copied structure using the "user defined" update site and can then update another
machine without any more downloading of packages.
Questions?
Bruce: Looks like my downloads are going to the following directory -- /var/lib/YaST2/you/discontinued/i386/update There are 3 directories under that directory -- 1) patches -- lots of files. Many have today's date. 2) rpm -- contains 3 directories, i586, noarch, and i686. i686 has one file, the other directories contain lots of files. Many of these files contain today's date. 3) scripts -- contains one file, rpmupdate-postscript.sh I'm still trying to get the patches back to my machine and installed. Every time I try, at least one patch has a signature error and the update fails. This last time, only the adminguide failed to download. If at least one package fails to download, none of them are installed. I'm going to try tomorrow and leave that one package out (I think I can safely put everything else in and not have any dependency failures). Then, all of these should automatically install. Looks like that download put things into all of the above 3 named places. Do I need what's in all of these directories? The next question -- how would I install all of these patches manually, without running YOU. Would running the rpmupdate-postscript script in the scripts folder install them all? Thanks, Greg Wallace
On Tuesday, May 03, 2005 @10:49 PM, I wrote:
On Tuesday, May 03, 2005 4:54 AM Bruce Marshall wrote:
On Tuesday 03 May 2005 01:37 am, Greg Wallace wrote:
Every time I have to recover my old 8.1 system from backup, I have to go back out to the web and pull down a large number of updates. Recently, I trashed it when I was trying to create a disaster recovery backup so I <big snip>
You should be able to run your current packages off to a CD or other location.
I don't do that but I do use the packages on one machine to update others....
Here's the script I use:
#!/bin/sh rsync -auvzr -e ssh <mastermachn>:/var/lib/YaST2/you/mnt/i386/update/9.2/ /usr/local/update/i386/update/9.2/
(note, there are two lines to the above script... watchout for folding in
your email program)
The thing to note above are the directory structures. <mastermachn> is the machine that gets updated from SuSE sites directly. The /var/lib/YaST2........... structure is where the packages are kept (along with a lot of info about the updates)
By copying that structure and its files to another machine, using the /usr/local/update/...... structure, I can point YOU to the copied
structure using the "user defined" update site and can then update another
machine without any more downloading of packages.
Questions?
Bruce: Looks like my downloads are going to the following directory -- /var/lib/YaST2/you/discontinued/i386/update
There are 3 directories under that directory --
1) patches -- lots of files. Many have today's date. 2) rpm -- contains 3 directories, i586, noarch, and i686. i686 has one file, the other directories contain lots of files. Many of these files contain today's date. 3) scripts -- contains one file, rpmupdate-postscript.sh
I'm still trying to get the patches back to my machine and installed. Every time I try, at least one patch has a signature error and the update fails. This last time, only the adminguide failed to download. If at least one package fails to download, none of them are installed. I'm going to try tomorrow and leave that one package out (I think I can safely put everything else in and not have any dependency failures). Then, all of these should automatically install. Looks like that download put things into all of the above 3 named places. Do I need what's in all of these directories? The next question -- how would I install all of these patches manually, without running YOU. Would running the rpmupdate-postscript script in the scripts folder install them all?
Thanks, Greg Wallace
Looks like the timestamp on the ones in /patches are when I first connected to the SuSE site and the timestamps on the ones in the /rpm directory matches the time of the download. If a download is successful, does it then copy the packages over to patches? Greg Wallace
participants (3)
-
Bruce Marshall
-
Greg Wallace
-
Stan Glasoe