Help - QlikView lost. Raid controller faulty, old backup of server.
Hello,
We have run on this issue, and need some answer until our client come up with some more info. The client didnt install the app so cannot help us until the app vendor gets in touch with our client.
We had a hardware refresh two months ago and the backup team hasnt been informed that the change was over, so they didnt restart the backups.
Monday the server which had the app installed on C, had an raid controller failure. Now we cannot boot, or do anything else.
So we are in the situation that we have a full backup of the server which is two months old and a new server with broken data.
My question is what to do in this situation, so we do not lose any data for this application. Maybe some insight on how the app works and what to be careful with? like databases, where are they kept, or any usefull information?
On first sight, I would think that the data is not that important. It can be recreated if your data sources do not reside on the same partition of the same "broken" server.
Your backup can give you an idea about the QlikView architecture, the different data stages (QlikView documents and connectors that grab data and transform it into something that can be used/loaded by the end-user QVW documents), the load/refresh strategy (incremental, local copy of history, etc.), the method used to store data marts (QVDs or QV docs) and the end-user documents themselves.
Now you know the architecture and the important pieces. Check whether any usable more recent copies are available on the "broken" system. The data stores can be checked for corruption. Try to run the data stages from the bottom up, and note where they are broken/need replacements.
That way you may be able to recover as much as possible from the crashed environment. Experienced QlikViewers should be able to execute this strategy without too much delay. Do you have any available?
