4 Replies Latest reply: Dec 28, 2010 2:57 AM by Wycliffe
Wycliffe Level 1 Level 1
I am running Parallels build 6.0.11828 on my MBP.

I do not have the option of backing up the virtual machine selected in the Parallels settings.

For some reason, on every backup after the initial one on my Time Capsule, my MBP is backing up 3.97GB of data (the same amount each time), even when nothing on the MBP has changed or has been used - as you can imagine, over a very short period of time, the Time Capsule becomes full with my data.

Has anyone ever had this issue?

17" MacBook Pro Core Duo, Mac OS X (10.6.5)
Reply by Bob Timmons on Dec 23, 2010 6:31 AM Helpful
Welcome to the discussions, Wycliffe!

This is a Parallels thing and the same thing occurs in VM Fusion, Aperture, Entourage and any type of application that uses a "monolithic" type of database for operations. Any change at all is interpreted by the application as a complete change to the database, so the entire database gets backed up on each pass. This can fill a drive very quickly.

The only viable solution is to "exclude" the item that is being backed up on each pass and manually copy over the database when you need to backup.

See #8 and #9 in Pondini's excellent Time Machine - Frequently Asked Quesions
Reply by Pondini on Dec 24, 2010 8:44 AM Helpful
Wycliffe wrote:
Thanks Bob and Happy Holidays!

I exclude the Parallels VM from my backup, but will try your suggestions and see what happens.


See #A2 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum), for a couple of 3rd-party apps that will show exactly what's getting backed-up.

All replies

  • Bob Timmons Level 10 Level 10
    Welcome to the discussions, Wycliffe!

    This is a Parallels thing and the same thing occurs in VM Fusion, Aperture, Entourage and any type of application that uses a "monolithic" type of database for operations. Any change at all is interpreted by the application as a complete change to the database, so the entire database gets backed up on each pass. This can fill a drive very quickly.

    The only viable solution is to "exclude" the item that is being backed up on each pass and manually copy over the database when you need to backup.

    See #8 and #9 in Pondini's excellent Time Machine - Frequently Asked Quesions
  • Wycliffe Level 1 Level 1
    Thanks Bob and Happy Holidays!

    I exclude the Parallels VM from my backup, but will try your suggestions and see what happens.
  • Pondini Level 8 Level 8
    Wycliffe wrote:
    Thanks Bob and Happy Holidays!

    I exclude the Parallels VM from my backup, but will try your suggestions and see what happens.


    See #A2 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of the +Time Machine+ forum), for a couple of 3rd-party apps that will show exactly what's getting backed-up.
  • Wycliffe Level 1 Level 1
    I used Backup Loupe to discover it was a faulty Carbonite install that was causing the issue - thanks for the help!