Anonymous_User Absent Member.
Absent Member.
955 views

Reduce/Expire on post office - advice needed

My organization has (had) an email retention policy of 30 days for
email and 365 days for appointments.

We have been on legal hold for the last 3 years so I am looking at
roughly that amount of data that will need to be removed when we get
the green light to come off of hold from the legal folks. (I'm told
that is coming soon)

My question is how does the expire/reduce run most efficiently? Should
I just set my 30/365 days settings and let it run or does it run more
effiently (quickly) if I did something like 365/720 then stepped down
to the 30/365, which would require 2 passes through the post office.

I know from observing the initial implementation of the policy, it is
going to take more than a week to get everthing down to size. Also, I
will probably have to run this stand alone so I can start/stop it as
needed. We can't take too much of performance hit if I just start it
from the server and let it run.

Once I get the post office trimmed down, I'll be re-enabling the
nightly scheduled expire/reduce options for maintenence.

Any advice or recommendations are appreciated.

Mark
Labels (2)
0 Likes
3 Replies
Knowledge Partner
Knowledge Partner

Re: Reduce/Expire on post office - advice needed

In article <feesb8tr55cu3qkgg5mr4uq32bjs34gfkr@4ax.com>, Mark wrote:
> My organization has (had) an email retention policy of 30 days for
> email and 365 days for appointments.

That's quite short and might get you in legal trouble. It might be very
worth your while to investigate archival tools such as GWAVA's Retain.

>
> My question is how does the expire/reduce run most efficiently? Should
> I just set my 30/365 days settings and let it run or does it run more
> effiently (quickly) if I did something like 365/720 then stepped down
> to the 30/365, which would require 2 passes through the post office.
> I know from observing the initial implementation of the policy, it is
> going to take more than a week to get everthing down to size. Also, I
> will probably have to run this stand alone so I can start/stop it as
> needed. We can't take too much of performance hit if I just start it
> from the server and let it run.


How long does a full Contents analyze/fix take? You'll be in about that
time frame. What I would do is start with a pass on cleaning up just
trash, then just the appointments, then the mail. How big is this
PostOffice? (#Users & GB/TB?) How many CPUs? If virtual, adding some
more for this reduction would help.

Was that initial implementation done from a stand alone system or agent
based? And what that on the current hardware config?


Andy Konecny
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Reduce/Expire on post office - advice needed

Hi Andy -

Thanks for the input. My industry (without getting too specific)
makes the rules but does not need to follow them if you read through
the lines 🙂

I've had discussions about archiving until I'm blue in the face. I
would get more traction discussing it with my dog.

The size of the post office is roughly 500 user at 380GB. I'll have
to research the lenght of the full contents check that runs on the
weekend. I like the idea of the three runs.

On Tue, 04 Dec 2012 18:49:15 GMT, Andy Konecny
<konecnya@no-mx.forums.novell.com> wrote:

>In article <feesb8tr55cu3qkgg5mr4uq32bjs34gfkr@4ax.com>, Mark wrote:
>> My organization has (had) an email retention policy of 30 days for
>> email and 365 days for appointments.

>That's quite short and might get you in legal trouble. It might be very
>worth your while to investigate archival tools such as GWAVA's Retain.
>
>>
>> My question is how does the expire/reduce run most efficiently? Should
>> I just set my 30/365 days settings and let it run or does it run more
>> effiently (quickly) if I did something like 365/720 then stepped down
>> to the 30/365, which would require 2 passes through the post office.
>> I know from observing the initial implementation of the policy, it is
>> going to take more than a week to get everthing down to size. Also, I
>> will probably have to run this stand alone so I can start/stop it as
>> needed. We can't take too much of performance hit if I just start it
>> from the server and let it run.

>
>How long does a full Contents analyze/fix take? You'll be in about that
>time frame. What I would do is start with a pass on cleaning up just
>trash, then just the appointments, then the mail. How big is this
>PostOffice? (#Users & GB/TB?) How many CPUs? If virtual, adding some
>more for this reduction would help.
>
>Was that initial implementation done from a stand alone system or agent
>based? And what that on the current hardware config?
>
>
>Andy Konecny
>KonecnyConsulting.ca in Toronto
>----------------------------------------------------------------------
>Andy's Profile: http://forums.novell.com/member.php?userid=75037
>

0 Likes
Knowledge Partner
Knowledge Partner

Re: Reduce/Expire on post office - advice needed

In article <1tisb8tk81rrvvo4c93at2jcoj5b3191nq@4ax.com>, Mark wrote:
> I've had discussions about archiving until I'm blue in the face. I
> would get more traction discussing it with my dog.
>

Ah yes, I know those discussions, not unlike with those who refuse to
buckle up in the car. If any of those ended up in email, perhaps
printing them off and keeping them in your files (perhaps with an off
site copy) might be a worthy CYA move, before doing that expire run of
course. Deniers of reality often attack the messenger when said
reality finally smacks them, "why didn't you tell us?", So good to have
proof you told them.

> The size of the post office is roughly 500 user at 380GB. I'll have
> to research the lenght of the full contents check that runs on the
> weekend. I like the idea of the three runs.
>

A client of mine with 100 users on a 800GB PO regularly runs 900 day
expires that only take a couple minutes every week. Retain keeps the
rest, with the expiry just an attempt to keep the PO size manageable.
They hadn't run it at their small office of 25 user until they ran out
of space at 250GB and that first run did take 6.5 hours, but subsequent
weekly runs were minutes. So stepped reductions may well be of value.

Contents checks run about the same time of 5-10 hours for both POs,
showing that they systems they are running on makes a big difference
(OES on new VM vs NetWare directly on old hardware(soon to be
migrated))



Andy Konecny
KonecnyConsulting.ca in Toronto
----------------------------------------------------------------------
Andy's Profile: http://forums.novell.com/member.php?userid=75037


___
Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.