You need to clarify what you mean when you say you're taking incrementals
that you keep for 60 days and a monthly full that is kept for 2 years.  Do
you mean that you do nightly incrementals (the mgmt class being set to keep
extra versions for 60 days) and a monthly full ARCHIVE that is kept for two
years?  Or is your monthly full just a 'selective', in which case how are
you setting it to keep files for two years?  You can't just change the mgmt
classes on sundays and then back again on monday - the files will simply
rebind and you won't be any further ahead.

Keep in mind that ADSM doesn't really work on the concept of fulls with
incrementals.  ADSM backup works on an incremental ALWAYS theory.  You never
do a full after the first backup.  This is why under normal circumstances
you'll end up with 83 tapes to mount.  You could force a selective backup
once per month, but this won't get you your 2 year retention if the mgmt
class is changed to 60 day retentions for extra versions the next day.

What you really want to do, as someone else pointed out is an Archive once a
month, as opposed to a backup.  Send the archive to a 2 year mgmt class, and
you'll have your monthly snapshot that sticks around for 2 years, without
effecting your normal incremental backups.  Then make sure you do a retrieve
instead of a restore, to get back the archive copy instead of the backup
copy.  If archive is what you're using for your monthlys already, then the
problem is that you did a restore instead of a retrieve - backup=restore,
archive=retrieve.

The other thing you can do is go colocated, but you'll eat up more tapes.
If library space isn't an issue, then this'll get you much faster restores.
If tapes are an issue, then your archive will at least let you get your
snapshot quickly.  Then after you retrieve your archive, if you need to go
further forward, do a restore on top of it, and only the files that have
changed since the archive was taken will be restored.  This should greatly
reduce the # of mounts.

Later...

Paul