How to troubleshoot missing data

Aidan Fitzpatrick

By Aidan Fitzpatrick

Updated

See how I'm qualified to write this article

If data is not present when a user or operator expects it to be, the following checks should be made, in order.

Confirm that the end-user has a subscription through Reincubate Relay

  1. Look up their user account details or email address in your internal system. Your own database should store their subscription ID. Do they have one? If so, skip to “Confirm that the client integration is working”. If not, go to “Troubleshooting pairing”.

Confirm that the client integration is working

  1. Is your client application successfully listening to data from Reincubate’s aschannel? If you’re using the Open Source components from Reincubate, checking the system and message tables and the listener log files should give you an idea of this. If you’re using your own implementation or a mixture, you’ll have an internal tool for your operators to check. If you see any errors in the logs, be sure to check them against the technical documentation section on hosting and deployment.

  2. Has aschannel streamed any data about that user’s backup? If you’re using the Open Source components from Reincubate, checking the system and message tables should give you an idea of this. If you’re using your own implementation or a mixture, you’ll have an internal tool for your operators to check.

  3. Is there a reported outage on status.reincubate.com?

Confirm that the end-user’s installation is correct

  1. Does the user have Reincubate Relay installed?

  2. Does the user have Reincubate Relay running?

  3. Does Reincubate Relay show that the user has paired with the client’s system? If it says “Start pairing”, then it has not been.

  4. Are you confident that the end-user’s subscription is with the device that they are discussing with you, and not another one? Ie. whether they have installed on both their PC and their laptop.

  5. Does Reincubate Relay show that permission has been given to access the backup, or is it still requesting permission?

  6. If the user’s backups as password protected, has the Reincubate Relay client been provided the password, or is it still asking for one?

  7. Does Reincubate Relay show that an iTunes backup is present and recent?

  8. Has aschannel streamed any data to the client system subsequent to that backup being taken? If you’re using the Open Source components from Reincubate, checking the system and message tables should give you an idea of this. If you’re using your own implementation or a mixture, you’ll have an internal tool for your operators to check.

If some data has been streamed for that backup, yet content is not present in the client system, it indicates that the client integration did not fully capture it, and should be raised to client engineering.

If no data has been streamed for the backup, client engineers should confirm the integration is working and that there is no log data, system message, or message data about that account which may point to an integration problem. If there is no data to indicate this, a ticket should be raised to the support team at Reincubate.

About the author

Aidan Fitzpatrick founded Reincubate in 2008 after building the world's first iPhone data recovery tool, iPhone Backup Extractor. He's spoken at Google on entrepreneurship, and is a graduate of the Entrepreneurs' Organisation's Leadership Academy.

Reincubate's CEO at Buckingham Palace

Pictured above are members of Reincubate’s team meeting HM Queen Elizabeth Ⅱ at Buckingham Palace, after being awarded the UK’s highest business award for our work with Apple technology. Read our position on privacy, safety and security.

How can we help?

Our support team are here to help!

Our office hours are Monday to Friday, 9am to 5pm GMT.

We aim to reply to all messages within one working day.

Get in touch › Our awesome support team

© 2008 - 2019 Reincubate Ltd. All rights reserved. Registered in England and Wales #5189175, VAT GB151788978. Reincubate® is a registered trademark. Privacy & terms. We recommend 2FA. Built with in London.