1739 Views 4 Replies Latest reply: Dec 28, 2010 2:57 AM by Wycliffe
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
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.