Re: Journaling and Disaster Recovery -- 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.

The restore order should be Journals, Files, Journal Receivers. Full save and restore is done alphabetically.

Years ago, we put Journals in a library named $JOURNALS. The $ sorts before A on the sav/rst.

The other way to deal with this is to manually restore the journal library first. Then run the full restore.

On 11/17/2009 08:53 AM, Mike Cunningham wrote:

We recently did a full backup from one system and restored to a new one (same serial number) and discovered after the restore that none of our files where being journaled. (SQL insert errors alerted us to this problem). Our journals are in a library named JOURNALS and our files are in FILES (aren't we creative in our naming). FILES was restored prior to JOURNALS.

Is the best way to prevent this from reoccurring to rename JOURNALS as SSJOURNALS or move the journals into FILES? We put them in their own library in case someday we put them in their own ASP and so we could easily backup just journals if needed. Or we just know that this will occur, document it and be prepared to restart journaling after a full restore. Any words of wisdom for best practice?

Thanks

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.