To help assure a clean migration, please address any *.bad files before proceeding with the migration process.
- Not doing so can introduce long delay times during migration and/or prevent a clean migration.
Ultimately, determining whether to delete or retain the files is a business decision but here are some items to help you make that determination.
- Check the current version's incident folder.
- Identify if any incident files should be moved and/or deleted prior to the migration.
- *.INC files
- Minor version upgrades do not impact incidents.
- A minor version upgrade, for example, would 15.7 to 15.8 or any MP upgrades between those minor versions.
- The migration will manage the move to the new directory.
- These incidents will process after the upgrade and services are restarted.
- *.BAD files
- These files should be moved and/or deleted PRIOR to the migration process.
- For more information on how *.bad files are caused, see the link below.
- Determine whether you will move the files and later rename to *.inc files or delete the *.bad files.
- Moving the files means you may choose to reintroduce into the incident folder, rename and attempt to be processed.
- For more information on reintroducing *.bad files, see the link(s) below.
- Deleting files is a permanent solution, but in many cases, *.bad files will be unprocessable.
- Some key factors to consider for deletion.
- Aging of *.bad files
- Depending on your remediation cycles, older incidents will not be addressed.
- Size of *.bad files
- Is there adequate space to store them in a different location?
- Quantity of *.bad files
- If there is a large number of files, all dated the same, was there an event that likely corrupted incidents, etc.
- How long will it take to move the number of files?
- Again, if these are aged files in large quantities, these are unlikely to be viable incidents.
- Test a few by changing to *.inc files.
- If they revert to *.bad, they are likely unusable.