I setup a LAMP instance with daily backups. Yesterday I installed some PEAR modules and then decided I didnt really want them. I did a restore to a version before PEAR was installed and to my suprise the module still fired up on the next reboot. Is this user error on my part(I assume) or is there some design reason as to why this module was survive the restore?
After deciding to rollback I went to TURNKEY HUB found the backup from the day before. (At the time it was the last backup) so I ran this command line.
tklbam-restore 2 reboot
Everything looked okay before I restarted the instance. It did tell me the restore was done. After the reboot I went to command line and typed PEAR and I was dumbfounded to find that it responded. I thought maybe this backup was taken after I installed PEAR so I went back one more day
tklbam-restore 2 --time 2011-11-01T06:25:21 reboot
Same thing.. PEAR responded after the reboot.
I am assuming this is operator error on my part, just not sure where. Is it correct to assume that if I were to rollback to before a module was installed that module would be removed from the system?