I have two computers running Snow Leopard backing up to a 2nd generation (regular)Drobo attached to one of the computers. They both used to back up to sparsebundles onto the Drobo built by an app called TimeTamer, used to control how much space the back-ups will take. Eventually, both machines no longer backed up to the sparsebundles and I was forced to back up directly to the Drobo.
One machine (a desktop) is directly hooked up to the Drobo and back ups via a Firewire 800 cable.
The other machine (a laptop) mainly is backed up to the drobo via USB 2.0. Both machines can not be hooked up at the exact same time to the drobo, but one of the other machines can go in via wireless networking.
After upgrading my Laptop to Snow Leopard a few weeks ago, I hooked it up to the Drobo to back up yesterday. It said my sparsebundle backups for this particular machine were not valid and it would delete them and make new backups. I said OK. It took 3/4 of a day to move 221 Gigabytes of data onto the drobo.
Today I told my laptop to back up to the drobo using the desktop's LAN connection and with the Drobo as a native AFP share, this time via my laptop's wireless internet connection. BUT instead of using the database it created yesterday on the root of the drobo's drive, It created a sparsebundle on the drobo featuring the machines name and ending in ".tmp.sparsebundle" and wanted to back up the 221 Gigabytes of data AGAIN over the wireless network, which would take a lot longer than doing it by USB. I turned off the Time Machine on my laptop and tried to move the backups from the root of the drobo into the temporary sparsebundle. No luck, it wouldn't budge.
If it helps, the laptop is on 10.6.4. and the desktop is on 10.6.3, because it refuses to update to 10.6.4 without totally messing up mail; I've tried it twice, same thing happened both times (messed up mail), don't bother suggesting updating the desktop, unless 10.6.5 comes out miraculously overnight.
I am frustrated about this and my stress level is over 9000 right now!
What could be causing all this trouble?
One machine (a desktop) is directly hooked up to the Drobo and back ups via a Firewire 800 cable.
The other machine (a laptop) mainly is backed up to the drobo via USB 2.0. Both machines can not be hooked up at the exact same time to the drobo, but one of the other machines can go in via wireless networking.
After upgrading my Laptop to Snow Leopard a few weeks ago, I hooked it up to the Drobo to back up yesterday. It said my sparsebundle backups for this particular machine were not valid and it would delete them and make new backups. I said OK. It took 3/4 of a day to move 221 Gigabytes of data onto the drobo.
Today I told my laptop to back up to the drobo using the desktop's LAN connection and with the Drobo as a native AFP share, this time via my laptop's wireless internet connection. BUT instead of using the database it created yesterday on the root of the drobo's drive, It created a sparsebundle on the drobo featuring the machines name and ending in ".tmp.sparsebundle" and wanted to back up the 221 Gigabytes of data AGAIN over the wireless network, which would take a lot longer than doing it by USB. I turned off the Time Machine on my laptop and tried to move the backups from the root of the drobo into the temporary sparsebundle. No luck, it wouldn't budge.
If it helps, the laptop is on 10.6.4. and the desktop is on 10.6.3, because it refuses to update to 10.6.4 without totally messing up mail; I've tried it twice, same thing happened both times (messed up mail), don't bother suggesting updating the desktop, unless 10.6.5 comes out miraculously overnight.
I am frustrated about this and my stress level is over 9000 right now!
What could be causing all this trouble?