Please point me to 1.2.0 -> 1.3.4 for Centos 6.7 upgrade docs/guide.
-
@BardWood Building another new set, just waiting for them to complete their compression cycles.
I’ll let you know, and again thanks for all the help so far.
-
Updated init’s are up again.
-
@Tom-Elliott When I wrote this, I had only tried to capture once, many RCs ago. I just tried again and it did work. I love the new status bar in the web interface showing progress, size, and estimated task time.
-
@BardWood Progress isn’t new, persay, I just have it always showing now.
-
Any luck on the deploy?
-
@Tom-Elliott No. Also, yes. Initiating ‘Plan B’.
I still had the CentOS 7 VM from a prior BETA of 1.3 so I dusted it off and installed 1.3.5. Did some tests with new images (just a junk, non-prepped image) and that worked. So please tell me how feasible this is:
I currently have 2 FOG servers on CentOS 6.7 and 7.3. I want to keep the 7.3 but it has no (real) images.
I’d like to roll the 6.7 back to 1.2.0, write the images to like hardware, re-direct clients to 7.3 and do fresh captures. The images themselves could use an update so if I can’t roll back to 1.2.0 it’s not a huge deal but would save some time. Is it as simple as just running the 1.2.0 install script?
-
@BardWood If you still have the original backup file from when you upgraded the server originally, this would be your best bet. It should be in /home/fogDBbackups
It typically is time stamped.
Once you reinstall 1.2.0, you’ll need to use the backup sql file to restore it as a lot changed in the DB between the two.