Copy sample exports into a separate folder and ask a reviewer to locate and open the text, images and attachments. Repeat the checks offline and record gaps. Readable local files do not imply one-click restoration into Feishu.
A restore drill asks a practical question: if only the archive were available, could another person find and use a specific document? This exercise checks local files. It does not promise automatic import into Feishu or restoration of permissions, comments and version history.
Define the sample before starting
Choose a representative batch with a text document, an image-rich document and an important attachment. Record the expected version and a known passage or data point. For a large wiki, include nested folders and documents with identical titles.
Use only material you are authorized to retain. Work in a separate folder without overwriting current files. Let the reviewer find the archive using the inventory; the exporter can help if a problem occurs.
Reconstruct a usable local copy
- Note the start time and locate the batch from the inventory.
- Copy its archive into a drill folder and extract that copy.
- Find each sample and confirm its source and export time.
- Open the text in the reader your team actually uses. Check the known passage, tables and code blocks.
- Open saved images and important attachments, checking that they contain usable content rather than only a name or download link.
Successful extraction is only one check. Missing assets, unreadable attachments and incomplete text should each be recorded as gaps.
Repeat the checks offline
Disconnect the network and reopen the local documents and images. This helps distinguish saved assets from resources that were loading from the web. Keep sensitive files out of online conversion services during the drill.
Check important links individually. A relative link that opens a local target can pass the offline check. Links to Feishu or another website should be marked as requiring network access and possibly an account. A link or snapshot of an interactive component has different capabilities from the original; document that limit.
Keep a short result log
| Item | Evidence to keep |
|---|---|
| Batch and samples | Archive folder, source URLs and local paths |
| Lookup time | Time needed to find the requested files |
| Content checks | Known text, images and attachment results |
| Offline checks | Local assets versus online dependencies |
| Follow-up | Gap, owner and retest date |
A passed sample does not establish that an entire wiki is complete. Review critical documents individually and expand sampling according to the value and risk of the remaining material.
Repair and retest
For missing images, check whether the asset files were saved with the document. Ask an authorized owner to download missing attachments. If files are difficult to locate, improve the batch names and inventory. Repeat the failed checks after repair.
If the goal is to return content to Feishu or move it into another service, test the destination’s supported import method with a few files in a test space first. Check permissions, comments, revision history and internal links separately before using the process on production material.