Re: Moving Journal Receivers to a separate library, any tips, tricks or pitfalls? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

On 1/25/2011 8:48 AM, Charles Wilt wrote:

Currently, the journal receivers for are application are in the main
application data library...

Which means that we really can't easily track our actually application
data growth, given that our current tracking system just tracks total
size of all objects in each library.

Considering moving the journal receivers into their own library.

Note the *JRN object itself will stay in the same library as the files.

I believe there are some save/restore implications....
1) Our daily SWA save should save the journal receiver library last?
2) During a restore, the journal receiver library should be restored
before the object library?

With respect to #2, saw a post from Rob Berendt mentioning that his
journal receiver library starts with # to encourage the system to
restore it first.

Does anybody know of any additional thoughts, tips, tricks or
pitfalls with having the journal receivers in a different library than
the objects being journaled?

Thanks!
Charles

Disclaimer: we currently use Journaling for investigative purposes, not for data base recovery...
We have our Journals and Journal receivers in a different library.
We save the receivers separate from our nightly backups (twice a day).

-gerald

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.