Hi, as it works now (V6), it will give an error if you try to retrieve (or move) a file stored on Glacier. V6 does not have the functionality to retrieve Glacier files. It's not going to re-copy the file if it doesn't need to. So basically you can use V6 to backup to S3 (and have it store them on Glacier) but you cannot use V6 to retrieve files stored on Glacier. This has implications on versions (as you cannot version a file stored on Glacier as you cannot move a file stored on Glacier).
The beta version of V7 works differently with Glacier stored objects. We've made a lot of changes to it will work with Glacier objects on S3. For example, if you need to retrieve a file stored on Glacier then it will make the request to S3 to retrieve it. You then need to run the profile again later to actually retrieve the files (as Glacier can take hours to retrieve a file). This even works with versioning (something S3 itself doesn't even support when using Glacier).
In other words, no need to panic. It works the same way as it used to and V7 will work perfectly with S3 & Glacier.
The beta version of V7 works differently with Glacier stored objects. We've made a lot of changes to it will work with Glacier objects on S3. For example, if you need to retrieve a file stored on Glacier then it will make the request to S3 to retrieve it. You then need to run the profile again later to actually retrieve the files (as Glacier can take hours to retrieve a file). This even works with versioning (something S3 itself doesn't even support when using Glacier).
In other words, no need to panic. It works the same way as it used to and V7 will work perfectly with S3 & Glacier.