the 900gb that it is now reporting, I have 2x 1TB drives running in RAID 1). Should the size of the HDD that timemachine sees be the size of the sparsebundle created (ie the 300gb for computer one and 150gb for computer 2)? Or will it detect the entire size of the HDD (ie. I switched back to my first computer, and it suddenly showed the HDD as 900gb! I have retried creating the shares and sparsebundles multiple times, but each time now, timemachine detects the "size" of the networked drive as 900gb? I'm not sure if this is right or not.
When I tried it on my second macbook (150gb limit) and separate timemachine share, I pointed timemachine to the share, but then it showed it as a 900gb HDD. The first time I created a sparsebundle (300gb limit) and timemachine share, I pointed timemachine to the networked drive, and it correctly detected the "size" of the drive as 300gb. I have followed the instructions posted on this forum, as well as many others on the net found by google. I have 2 macbooks and am trying to run timemachine on them both. I have just gotten my QNAP TS-209 II up and running. Hi, Thanks for everyone's help in advance. So I suggest that you follow the switch order in the version of OSX that you are running. It does seem to make a difference to the creation if you follow the order suggested in the man entry.
The latest Macbook pro seems to use a slightly different suggested switch order in the hdiutil to that given in the original post. This saves you having to rename the computer. BTW - you can create a name with spaces in the sparsebundle by setting a system variable like IMAGE_NAME="Computer Name with Spaces" and then reference $IMAGE_NAME in the hdiutil command. This avoided having to rename the computer. Creating the sparsebundle with a name without the apostrophe then re-naming it once it was transferred to the NAS worked. The apostrophe in the computer name caused the hdiutil command to fail with an error message like "cannot create multiple volumes at once".
First, the computer that I was trying to back-up had a name like "Jo Smith's Macbook". I helped me to get timemachine working with great success I had a couple of complications that I solved for my TS-409 which I thought I would share. So I see 2 odd things: 1) in the log above I first of all get an error regarding the filesystem case sensitivity (I read some forum post about restarting would fix but didn't work) 2) My share is called TimeMachine, but the -1 is added to the name, and fast switching is turned off Above is the information I have at the moment, I hope it is enough to get started on this issue! Thank you! /Peter Jan 5 23:33:22 Christinas-MacBook /System/Library/CoreServices/backupd: Ejected Time Machine network volume. Jan 5 23:33:18 Christinas-MacBook /System/Library/CoreServices/backupd: Backup failed with error: 23 Jan 5 23:33:19 Christinas-MacBook /System/Library/CoreServices/backupd: Ejected Time Machine disk image. With Linux and ZFS, QuTS hero supports advanced data reduction technologies for further driving down costs and increasing reliablility of SSD (all-flash) storage.Code: Select all Jan 5 23:32:58 Christinas-MacBook /System/Library/CoreServices/backupd: Backup requested by user Jan 5 23:32:58 Christinas-MacBook /System/Library/CoreServices/backupd: Starting standard backup Jan 5 23:32:59 Christinas-MacBook /System/Library/CoreServices/backupd: Mounted network destination using URL: Jan 5 23:32:59 Christinas-MacBook /System/Library/CoreServices/backupd: Backup destination mounted at path: /Volumes/TimeMachine-1 Jan 5 23:33:12 Christinas-MacBook hdiejectd: running Jan 5 23:33:12 Christinas-MacBook /System/Library/CoreServices/backupd: Disk image /Volumes/TimeMachine-1/Christinas-MacBook_001b63be39d2.sparsebundle mounted at: /Volumes/NAS_TM_BACKUP Jan 5 23:33:12 Christinas-MacBook /System/Library/CoreServices/backupd: Backing up to: /Volumes/NAS_TM_BACKUP/Backups.backupdb Jan 5 23:33:13 Christinas-MacBook /System/Library/CoreServices/backupd: Filesystem of Macintosh HD is case sensitive, but the backup disk is not. QuTS hero is the operating system for high-end and enterprise QNAP NAS models. WIth Linux and ext4, QTS enables reliable storage for everyone with versatile value-added features and apps, such as snapshots, Plex media servers, and easy access of your personal cloud. QTS is the operating system for entry- and mid-level QNAP NAS.