May 31, 201214 yr If: 1) I create a User Share to be used only for Time Machine backups and limit it to say 500GB 2) I create this Time Machine User Share to use only one disk, say disk2 3) say disk2 is already a part of another user share using high water allocation method Will the high water allocation method be smart enough to realize there is another User Share using the particular drive for Time Machine backup and will it take that 500GB limit into consideration--treat it like a 1.5tb hard drive instead of 2tb? Or do I really need to have an entirely separate hard drive for time machine backups? I have an old 60MB/s 7200RPM 250GB hard drive laying around--but it would take a drive bay which kind of stinks. Only other thing that comes to mind is just to include all the disks in the Time Machine share--limited to 500gb--and let it write all the files to any disk but this doesn't seem very ideal. Perhaps there is a good solution--please recommend, thanks!
June 1, 201214 yr Will the high water allocation method be smart enough to realize there is another User Share using the particular drive for Time Machine backup and will it take that 500GB limit into consideration--treat it like a 1.5tb hard drive instead of 2tb? Allocation settings are consulted when writing a new file to a user share. The allocation method has no persistent state. Each time a new file is written to a user share the allocation settings and disk capacities are examined as if they have never been consulted in the past. There is no explicit interaction between user shares. The allocation settings are like a filter and have no further effect once a file has passed through.
June 2, 201214 yr Author So is the best way to use time machine to buy a dedicated hard drive for it?
Archived
This topic is now archived and is closed to further replies.