Top 5 Tips for Optimizing Shoviv NSF Merge Performance
1. Prepare and clean source NSF files
- Remove corrupted or incomplete NSF files beforehand (Shoviv can’t merge corrupted DBs).
- Delete unnecessary folders (Trash, All Documents) or use the tool’s option to exclude them to reduce input size.
- Compact/repair NSF files in IBM Notes to reduce I/O and speed processing.
2. Use filtering and duplicate-removal options
- Apply date/folder/item filters to process only needed data.
- Enable duplicate-item removal to avoid extra processing and a larger final NSF.
3. Merge in batches, not all at once
- Split very large sets into smaller groups and run multiple merges (e.g., 10–50 NSF files per batch) to lower memory and CPU spikes and simplify error recovery.
4. Optimize the environment
- Run Shoviv on a machine with sufficient RAM and CPU (preferably ≥8 GB RAM for large merges).
- Use fast local storage (SSD) and avoid network-mounted NSF files — copy them locally before merging.
- Close unrelated apps and ensure IBM Notes is properly configured/updated.
5. Use the demo/process options and verify results
- Test first with the demo (50 items/folder) to confirm settings.
- After a merge, export/save the report and validate folder hierarchy, metadata, and contact merge (names.nsf).
- If issues arise, merge smaller subsets and check logs to isolate problematic files.
If you want, I can convert these into a short checklist or a one-page runbook tailored to your typical NSF sizes and system specs.
Leave a Reply