XDMP-JOURNALARCHIVEBADRESTOREFOLDER
Message Text
Expecting full backup folder and journal archive folder to have the same timestamp when restoring. Got variable1 for full backup folder. Got variable2 for journal archive folder.
Cause
You can store your archived journals and full database backup data in separate locations using the admin API. This message occurs when the restoring from separate full database backup and journal archiving locations. It indicates the journal archive folder does not have a timestamp that matches the full backup folder, which means that it is likely that full backup and archived journals are from separate backups.
Response
When restoring from a full database backup, the system will choose the earliest timestamped backup folder from the restore-to-time value. For the journal archiving path, unless the folder timestamp is explicitly specified, the timestamp chosen for the full backup path will be applied to the journal archiving path.In the case of a flash backup, it is possible for the full database backup folder and the journal archive folder to have different timestamps. In this case, you must specifically select the journal archive timestamped folder when restoring with the admin API.Ex:Error if timestamps don't match - xdmp:database-restore(xdmp:forest("Documents"),"/space/backup",(),true(),"/space/ja")Ok if timestamps don't match - xdmp:database-restore(xdmp:forest("Documents"),"/space/backup",(),true(),"/space/ja/20120206-1152597588850")If you are not trying to restore from flash backup, it is likely that the two folders contain unrelated data. Therefore, modify your journal archiving path to find a folder containing journal archiving data with the correct timestamp. If you did not explicitly choose a different journal archiving location, then the journal archives are likely stored in the same path as the full backup.
Stack Overflow: Get the most useful answers to questions from the MarkLogic community, or ask your own question.