What would be my best bet as far as upgrading? Will 7.2 know what to do if I popped it in the cd drive and told it to upgrade?
That will almost certainly fail. I remember there were certain update instructions for upgrading from 6.x to 7.x releases. One of them was to remove all contribs installed on the machine as well as the custom templates in templates-custom and templates-user-custom (
http://forums.contribs.org/index.php?topic=38543.msg174737;topicseen#msg174737).
It might be wise to not upgrade your system straight away as there have been some major problems with some people upgrading.
I suggest you make a backup of your server in the current state (just a safety feature I always do before making major changes). After that remove all installed contribs and custom templates and make an other backup, this backup will be used to restore later on a new fresh install.
Shutdown the server and take out the old hard disk, mount a new clean hard disk and do a clean install of SME Server 7.2 (on this new disk), after that restore the 2nd backup (without the contribs/custom-templates) on this new system.
Make sure you use a backup routine that is implemented in the server as this will take care of dumping and restoring configuration parameters like users as well as MySQL data. Unfortunately I am not sure if the backup options for SME Server 6.0 and SME Server 7.2 (latest release) are the same, but to have all critical stuff a so called minimal backup would include at least the following elements:
etc/e-smith/templates-custom
etc/e-smith/templates-user-custom
etc/group
etc/gshadow
etc/passwd
etc/samba/secrets.tdb
etc/samba/smbpasswd
etc/shadow
etc/smbpasswd
etc/ssh
etc/sudoers
home/e-smith
To make sure you also have a valid dump of the MySQL data you can execute the following command before backing up your files:
signal-event pre-backup
This command should make a dump of your MySQL data and store it in /home/e-smith/db/mysql/ with a file for each database. If you make a backup with the build-in SME Server backup features (if possible due to file size limits) this should already been done automatically (as well as a restore of these files on your new install). If you do things manually you will probably have to install the dump files yourself as well (and probably need to reset yor root password as well).
Please do not install on your current harddisk as it will be hard to recover from a failed installation and you run a great risk of ending up with a non running server as well. By setting apart the extra hard disk (with the running 6.x system) you have an easy way of restoring a running system. If the update/installation fails you can easily take out the drive with the failed install and replace it with the old drive. Boot up your server and you should have your old copy running again. This way you have a fall back build in, in case thing go haywire.