bubbadatrub1emkr
asked on
Restoring Databases with SCOS
Hello,
I am rather new to dealing with Domino servers but need to know if there are any differences in performing a restore of a Lotus databases when SCOS (Shared Copy Object Store) was turned on during the backup period. ArcServe was used for backup and is being used for restoration. Any help is appreciated. Whitepapers and links with further detail would be terrific.
I am rather new to dealing with Domino servers but need to know if there are any differences in performing a restore of a Lotus databases when SCOS (Shared Copy Object Store) was turned on during the backup period. ArcServe was used for backup and is being used for restoration. Any help is appreciated. Whitepapers and links with further detail would be terrific.
Advice: dump SCOS. Never heard of an installation where they did not regret using SCOS.
WHen you use SCOS, the Body field is not delivered to the mail file. Instead, it is delievered to SCOS, and a Body field pointer in the user mail file contains the ID of the SCOS document that has the body.
SCOS corruption issues are common, as the user mail files sometimes get out of sync with the SCOS databases. For restores, that can be especially tricky, especially if you have rebuilt SCOS since the backup you are retrieving. Otherwise, it should work, as the user file restore will contain the same SCOS reference now as it did then, and SCOS will contain the same old Body images.
Unless... here's an additional problem that can occur. SCOS maintainenance includes deleting Body objects that are no longer referenced. So, if a message is delievered to two users, the Body is delievered to SCOS, and the rest of the message is delivered to the two users with a Body reference to the corresponding SCOS document. So, there are two exitsing references to this SCOS document. If one of those users deletes the message, then the other user still has the reference, and there is only one reference to that SCOS document. If the second user deletes the message, then there are no references to this SCOS document.
SCOS maintenance checks for this situation and deletes the SCOS document as well. If you later restore one of those users' files, the SCOS reference will be in the restored dile, but there will be no corresponding SCOS document, and the user will not be able to read that message. The command that does this maintenance is LOAD OBJECT COLLECT. I am not aware of any way to restore the SCOS document.
WHen you use SCOS, the Body field is not delivered to the mail file. Instead, it is delievered to SCOS, and a Body field pointer in the user mail file contains the ID of the SCOS document that has the body.
SCOS corruption issues are common, as the user mail files sometimes get out of sync with the SCOS databases. For restores, that can be especially tricky, especially if you have rebuilt SCOS since the backup you are retrieving. Otherwise, it should work, as the user file restore will contain the same SCOS reference now as it did then, and SCOS will contain the same old Body images.
Unless... here's an additional problem that can occur. SCOS maintainenance includes deleting Body objects that are no longer referenced. So, if a message is delievered to two users, the Body is delievered to SCOS, and the rest of the message is delivered to the two users with a Body reference to the corresponding SCOS document. So, there are two exitsing references to this SCOS document. If one of those users deletes the message, then the other user still has the reference, and there is only one reference to that SCOS document. If the second user deletes the message, then there are no references to this SCOS document.
SCOS maintenance checks for this situation and deletes the SCOS document as well. If you later restore one of those users' files, the SCOS reference will be in the restored dile, but there will be no corresponding SCOS document, and the user will not be able to read that message. The command that does this maintenance is LOAD OBJECT COLLECT. I am not aware of any way to restore the SCOS document.
ASKER
I should have clarified before. We are restoring some data for a client who used SCOS temporarily in the past. Certain tapes have shared mail databases that we will need to pull data from.
Will restoring the individual NSF file also pull the emails/attachments from the shared mail database?
Will restoring the individual NSF file also pull the emails/attachments from the shared mail database?
If the user file you are trying to restore was linked to SCOS at the time of backup, then yu will need to restore both the user file and all SCOS files from that period, and you must restore them (user and all SCOS files) to the same file path locations as they were in originally.
Natuarlly, if you are doing this on a production server, that may be difficult.
Natuarlly, if you are doing this on a production server, that may be difficult.
ASKER
Thank you for your help qwaletee, you're getting me almost there. I have been looking all day for a whitepaper which fully describes this scenario and the variations that can be made, however I have been unsuccessful in finding online assistance, except for EE. I hate to continue with the questoins, but do I need to configure a server identical to the server the nsf was on previously? What needs to be done to push the appropriate attachments and emails to an individuals NSF for restoration? How can I verify that all emails and attachments have been placed into their corresponding NSF?
Thanks again for your answers! If there is a good source of online documentation that I can look at instead that will be just as helpful!
Thanks again for your answers! If there is a good source of online documentation that I can look at instead that will be just as helpful!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
~Hemanth