Updated: Glacier objects stored in S3 are ignored
I don't see what has changed here. I put 1 file in a folder, and backed up to S3, which has a lifecycle policy to move to Glacier.
The next day, the file went to Glacier.
I re-ran the profile. It said "no differences".
That IS how I want it to work! But, your changelog makes it seem like it should have re-copied that file to S3 because "Glacier objects stored in S3 are ignored." now.
I also tried this on 6.3, before this change was made in 6.4 and it had the exact same result.
So...... What is the meaning of that in the changelog exactly? What is SyncBack SUPPOSED to be doing? Should it re-copy after it is in Glacier? Or should it see it in Glacier and NOT re-copy it?
I would prefer that it NOT re-copy, but the changelog creates confusion on this point.
I don't see what has changed here. I put 1 file in a folder, and backed up to S3, which has a lifecycle policy to move to Glacier.
The next day, the file went to Glacier.
I re-ran the profile. It said "no differences".
That IS how I want it to work! But, your changelog makes it seem like it should have re-copied that file to S3 because "Glacier objects stored in S3 are ignored." now.
I also tried this on 6.3, before this change was made in 6.4 and it had the exact same result.
So...... What is the meaning of that in the changelog exactly? What is SyncBack SUPPOSED to be doing? Should it re-copy after it is in Glacier? Or should it see it in Glacier and NOT re-copy it?
I would prefer that it NOT re-copy, but the changelog creates confusion on this point.