Posts Tagged ‘database’

Backup and restore of iOS devices running mobilEcho 3.5, 3.5.1, and 3.5.2

Monday, March 19th, 2012

Versions 3.5, 3.5.1, and 3.5.2 of the mobilEcho iOS app use an encrypted database to manage the files stored within the mobilEcho app’s on-device storage. The information required to access this database is stored in the iOS keychain. For security reasons, mobilEcho’s keychain items are not restored to the new device during the backup and restore process.

When this method of backup and restore to a new device is performed with a device that has mobilEcho 3.5, 3.5.1, or 3.5.2 installed and configured, the keychain item required to open the encrypted file database is not restored to the new device. This causes mobilEcho to be unable to access the restored file database and the on-device files it manages.

A workaround for this limitation of the ‘backup and restore to new device’ process will be included in mobilEcho 3.5.3, and all future versions of mobilEcho.

To work around this mobilEcho / iOS backup and restore situation:

1. Backup any needed local files to a server-based location before moving to your new device.

  • If you have already restored to a new device using a standard iTunes backup and restore process, mobilEcho will not function properly on the new device and will not include the on-device files from your old device. If you still have your old device, you will need to use that device to save your files to a server-based location, so they can be downloaded to mobilEcho on your new device.

2. Remove mobilEcho from the new device, reinstall, and reconfigure.

  • Tap and hold the mobilEcho app icon. Once it appears, tap the “X” in the corner of the app icon to remove the app.
  • Visit the App Store and install mobilEcho again:
  • Add your mobilEcho server(s) within the app, or if you are using a managed mobilEcho client, request a new enrollment invitation from your IT administrator and follow the included instructions to reenroll your mobilEcho client app. This enrollment process will reconfigure all the servers and folders that you previously had access to.
  • You can now copy the files you backed up to the server back down to the new device using the mobilEcho app.

How Do I Repair MySQL Tables?

Tuesday, August 3rd, 2010

On Windows

First back up your database as follows

Once the backup is complete:

  1. – Click on Catalogs in the MySQL Administrator
    –┬áSelect mtdatabase in the Schemata window on the left
    – Click the Maintenance button
    – Select Repair Tables option
    – Select Use FRM options
    – Click the Repair Tables button
  2. Redo the backup
  3. Restart MassTransit.

On Mac

First back up your database as follows

Once the backup is complete:

  1. – Click on Catalogs in the MySQL Administrator
    – Select mtdatabase in the Schemata window on the left
    – One by one, highlight a table
    – Click Table Actions at the bottom
    – Select Repair Table
    – Select Use FRM
  2. Make another backup
  3. Restart MassTransit.

Optimizing MassTransit Databases

Tuesday, September 15th, 2009

From time to time you may need to repair or optimize your MassTransit databases. You can do so easily by using the MySQL Administrator that came with your MySQL installer package.

Optimizing For Windows

  • Log in to the MySQL Administrator
  • Select Catalogs
  • Select the mtdatabase schema
  • Highlight the table(s) you wish to optimize

MySQL Admin - Catalogs

  • Click the Maintenance button at the bottom right
  • The Tables Maintenance box will pop up
  • Select Optimize Tables
  • Click Next
  • Click Optimize

Tables Maintenance

Once completed you will see a list of tables and what optimizations took place.

admin 3