This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Clarification requested about: "date range to scan" when used for GW

Benny DeH over 3 years ago

Hi all,

I've read the documentation, especially archiving.pdf page 163.

I think I understand the "advance timestamp", for every succesfull archived message the timestamp is advanced.

When setting "date range to scan" to "New items", the job only selects messages newer than the timestamp. Not whether or not the message is new (unread) from an enduser perspective.

Now setting "date range to scan" to "Number of day before job start date and newer". This option it's use case isn't clear to me. I see the possibility for items not to be archived. What happens when the previous job and timestamp is further in the past than the "number of days before job start date" ? Does the timestamp gets set to today?
An example: last job and the timestamp was two weeks ago. Now run a new job with "number of days before job start date" to 7 and exists succesfull. Will this job skip all items between two weeks ago and last week? What happens when I change the Job to "New items" after this job has completed. Does this new job also skips all items between two weeks and last week, because the timestamp advanced to today?

Thanks,

Benny

0 Diethmar Rimser over 3 years ago

I prefer this way but we will see other administrators have a different view:
My users will have time to move items to the right folder for 60 days. It is important to explain that a Retain archive is a snapshot. If items are still in my inbox when a retain job archives messages, then these items will be in my archive inbox too. Even if I move a message to another folder afterwards.
In my case above I archive all items between the time gap of 60 days and older. But only back to last archived item (stamp). So if my archive was successful the new time stamp will be at today minus 60 days.

Use "Verified Answers" if your problem/issue has been solved!
Cancel
Vote Up 0 Vote Down

Cancel
0 Andy Konecny over 3 years ago in reply to Diethmar Rimser

I'd think that 60 days would be a problem if you have "don't purge until archived" flag set.
We find out very quickly if a user's timestamp doesn't get advanced for any reason, such as a problem archiving a message, because they can't empty their trash bin. This is with the scope at the default of "New Items" but you've given me thought to talk with the clients about changing this a bit, even if just for a few days.

________________________

Andy of KonecnyConsulting.ca in Toronto
Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.
Cancel
Vote Up 0 Vote Down

Cancel
0 Diethmar Rimser over 3 years ago in reply to Andy Konecny

Yes, you're right,
In some environments I am in a lucky position to use Reload for backing up and "don't purge until backup" flag. And Retain for archiving. So I just have to handle the gap between Reload and Retain .
In this case 60 days will fit.
Nevertheless I run more than one policy. One policy for critical mailboxes - archive as soon as possible. Some more policies using other, longer time frames. These policies are based on GroupWise group memberships; so it's easy to handle.

Use "Verified Answers" if your problem/issue has been solved!
Cancel
Vote Up 0 Vote Down

Cancel

Menu

Retain User Discussions

Verified Answers

Clarification requested about: "date range to scan" when used for GW

Resources