SOLVED

Journaling and longterm storage

%3CLINGO-SUB%20id%3D%22lingo-sub-1101175%22%20slang%3D%22en-US%22%3EJournaling%20and%20longterm%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1101175%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20searched%20a%20bit%20but%20having%20trouble%20finding%20the%20answer%20regarding%20the%20best%20way%20of%20storing%20old%20yearly%20journaling%20mailbox%20and%2For%20databases.%3C%2FP%3E%3CP%3ELet%20say%20i%20have%20my%20journaling_mailbox%20in%20a%20journaling_database%20that%20receives%20all%20the%20traffic.%3C%2FP%3E%3CP%3EHow%20those%20that%20use%20journaling%20manage%20the%20ever%20expand%20growth%20%3F%3C%2FP%3E%3CP%3EOf%20course%20my%20databases%20and%20backed%20up%20follows%20proper%20procedures%20but%20i%20would%20like%20to%20have%20the%20contents%20of%20previous%20year%20in%20a%20database%20that%20i%20could%20dismount%20and%20move%20somewhere%2C%20so%20the%20new%20year%20have%20only%20its%20content%20in%20a%20new%20database.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20this%20make%20sense%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EShould%20i%20just%20create%20a%20new%20journal2020_mailbox%20and%20put%20in%20a%20new%20journal2020_database%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1101175%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1125042%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20and%20longterm%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1125042%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F513323%22%20target%3D%22_blank%22%3E%40sbarros%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYes.%26nbsp%3B%20Make%20new%20JRNL%20mailboxes%20and%20cut%20the%20rule%20over%20to%20the%20new%20recipient%20on%20an%20annual%20basis.%3C%2FP%3E%0A%3CP%3EIf%20you%20decide%20to%20make%20a%20new%20DB%20to%20host%20that%20jrnl%20mailbox%2C%20that's%20fine.%26nbsp%3B%20That's%20an%20organizational%20decision.%3C%2FP%3E%0A%3CP%3EWhat%20you%20do%20with%20%22old%20data%22%20depends%20on%20the%20requirements%20for%20that%20mailbox%20to%20be%20online%20and%20searchable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1127290%22%20slang%3D%22en-US%22%3ERe%3A%20Journaling%20and%20longterm%20storage%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1127290%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F529996%22%20target%3D%22_blank%22%3E%40chrisream%3C%2FA%3E%3CBR%20%2F%3Ethanks%2C%20your%20post%20gives%20me%20peace%20of%20mind%20about%20my%20procedure.%3CBR%20%2F%3Echeers%20mate.%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi,

 

I searched a bit but having trouble finding the answer regarding the best way of storing old yearly journaling mailbox and/or databases.

Let say i have my journaling_mailbox in a journaling_database that receives all the traffic.

How those that use journaling manage the ever expand growth ?

Of course my databases and backed up follows proper procedures but i would like to have the contents of previous year in a database that i could dismount and move somewhere, so the new year have only its content in a new database.

 

Does this make sense ?

 

Should i just create a new journal2020_mailbox and put in a new journal2020_database ?

 

Thanks

2 Replies
Highlighted
Best Response confirmed by sbarros (New Contributor)
Solution

@sbarros 

Yes.  Make new JRNL mailboxes and cut the rule over to the new recipient on an annual basis.

If you decide to make a new DB to host that jrnl mailbox, that's fine.  That's an organizational decision.

What you do with "old data" depends on the requirements for that mailbox to be online and searchable.

Highlighted
@chrisream
thanks, your post gives me peace of mind about my procedure.
cheers mate. :)