At a minimum, you will need at least one of the following:
- A .lcmbiar file backup containing the report's instances
- A file system backup of the Output FRS
If you have neither of the above, then you are out of luck - the instances are gone.
If you have an .lcmbiar backup, then you can easily import it back in, and your instances will be there.
If you have a file system backup (from prior to the deletion), then recovery may be possible, but it will be a lot of work.
- If you also have a backup of the CMS from around the same time, then your chances of success are better. If you can afford to lose all of the work that's been done in your BO environment since the instances were deleted, then you can simply recover everything (the CMS and FRS). Your deleted instances should be there. You're essentially turning back the clock to that point in time.
- If you have a backup of the CMS but don't want to lose work that's been done since then, then it's possible but it's a lot of work and very risky. You would need to install BO on a new server, and point it at a recovered instance of the CMS, and a recovered copy of the FRS. If you have a clustered environment, then this does risk impacting your production cluster (I've done it, but in a very controlled environment). Once the temporary environment is up, you can create an .lcmbiar file of the report and its instances, and migrate it to the production environment.
- If you have a backup of the FRS but don't want to muck around with the CMS, you can try to find the actual .wid files for each instance in the FRS backup. You then open the .wid files with WebI Rich Client, re-name them, and publish them to the CMS. Note that each of these will be a base report - not an instance. Since you're not touching the CMS, this method does not risk corrupting your production cluster.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.