Moving to S3 with kb3067 - A way to check progress?

[Cuebid-Fredrik]

Hi,

For a customer we helped set up new jobs to S3, we also helped migrate the old SMB repo to a sort of archive in S3 using the script from kb3067.
It was quite a rocky start until we got a good balance of threads and cores vs. bandwidth and target performance, not to mention the hangs with "Detecting..." as status.
Anyways, it's 36TB SMB and has been running for about four months now(yes months...) and I can see 24TB S3 on the target.

My questions are:
1. Can we expect any compression on the S3? The normal jobs do about 40%, but I guess we're past that.
2. Is there a way to check progress? Like checking how many users/sites/Teams are left to migrate on the SMB.

Appreciate any help.
/Fredrik

[Mike Resseler]

Hi Fredrik,

1. It still would give you some compression as we don't just copy/paste but we need to move the data and transform them into objects, similar to what a regular job does
2. Unfortunately not, in v8 we are working on a big improvement on this, with a new method of migrating from jet DB repository to OSR

[Cuebid-Fredrik]

Thank you Mike, for a speedy reply.
We'll just keep it running then and hopefully it's soon done
Looking forward to v8!

Kind regards,
/Fredrik