Is there any way to maintain manually for Time Machine more than one sparse bundles (in case here: 2) on same network share? SMB as protocol is used.
In one of those 2 sparse bundles Time Machine backups are stored (one single Mac, 10.9 only) which were generated last (appx) 3 years. This backup will from now on be used only in passive way, means only for data recovery, as in the meantime Mac was upgraded to macOS 10.12 and Time Machine backups are going to start from scratch and flow to new dedicated sparsebundle.
The another sparse bundle is going to be even used for purpose already mentioned above: macOS 10.12 Time Machine backups (one single Mac, only 10.12) and from-scratch backup building.
The old one is already present on SMB network share. System Preferences > Time Machine can connect to that and one can complete backup verification, one can surf backup increments using Finder on Star Wars screen. I do not aim to start new increment due to mentioned reasons.
Another sparse bundle has been created using Disk Utility on same SMB network share. The attempt to connect it to Time Machine fails:
completes with error stressing about some conflict with already registered backup destination.
Is there way to have these two backup destinations connected to Time Machine at least in interchangeable way? A procedure of manual switching from one to another will be acceptable as described situation and goal are valid for next few weeks. In the meantime old backup will be saved to some usb external drive and the actively maintained T.M. backup only will be stored onto mentioned network share > single network share - single T.M. backup destination. However this minute is interim phase of two backup destinations on same network share.
On the mac here Time Machine never runs in automatic mode. All backup increments are started manually. There are no plans to change it in future, neither short nor middle term.
[doublepost=1507237111][/doublepost]
Myself believes to had found searched proceeding. Handling on level of network share with sparse bundles on it is needed. All below applies to Time Machine backup destination on SMB network share. Not tested with AFP instead of SMB. That is:
-)rename old sparse bundle with existing (old) backups to harmless name, e.g. to TMSparseBundle-A, this way it won't conflict anymore with sparsebundle created by Time Machine for from-scratch backups in next step plus 1 (Time Machine ignores and does not touch in any extent these data)
-)do not create new sparse bundle for new backup destination manually (means using DU or other) as it is nothing nor nobody else what/who determines the name of sparse bundle image and who/what initiates it
-)let the Time Machine instead to create new sparse bundle as new backup destination, there is no other way as that
-)connect Time Machine to network share
-)start backup, it will be initial backup (with creation of sparsebundle for backup destination in beginning) into sparse bundle created by tm in previous step minus two - thus backup process of remarkable duration
-)let new backup to complete, verify it, test it, maintain it, use it
-)if some time later one needs to access the old backup in old sparsebundle rename sparse bundle currently used to yet another harmless file name e.g. to TMSparseBundle-B, prior to this disconnect time machine from backup destination
-)rename TMSparseBundle-A to its original name, it is <Mac name>.sparsebundle
-)connect time machine to network share
-)use backup as aimed
Procedure works when Time Machine never in automatic mode and seems to show high automation level. It works best way if for surfing backup history "Enter Time Machine.." the plain-mode Finder does not mount neither underlying network share nor backup sparse bundle.
My strategy is to use time machine backup in passive fashion (only for data recovery) if operating system major version (that one behind digits 10.) differs between backup destination and source. Use backup in usual way (additionally increments generation) if same operating major version on both backup destination as well on backup source side.
In one of those 2 sparse bundles Time Machine backups are stored (one single Mac, 10.9 only) which were generated last (appx) 3 years. This backup will from now on be used only in passive way, means only for data recovery, as in the meantime Mac was upgraded to macOS 10.12 and Time Machine backups are going to start from scratch and flow to new dedicated sparsebundle.
The another sparse bundle is going to be even used for purpose already mentioned above: macOS 10.12 Time Machine backups (one single Mac, only 10.12) and from-scratch backup building.
The old one is already present on SMB network share. System Preferences > Time Machine can connect to that and one can complete backup verification, one can surf backup increments using Finder on Star Wars screen. I do not aim to start new increment due to mentioned reasons.
Another sparse bundle has been created using Disk Utility on same SMB network share. The attempt to connect it to Time Machine fails:
Code:
sudo tmutil inheritbackup <path to sparse bundle on smb network share>Is there way to have these two backup destinations connected to Time Machine at least in interchangeable way? A procedure of manual switching from one to another will be acceptable as described situation and goal are valid for next few weeks. In the meantime old backup will be saved to some usb external drive and the actively maintained T.M. backup only will be stored onto mentioned network share > single network share - single T.M. backup destination. However this minute is interim phase of two backup destinations on same network share.
On the mac here Time Machine never runs in automatic mode. All backup increments are started manually. There are no plans to change it in future, neither short nor middle term.
[doublepost=1507237111][/doublepost]
Myself believes to had found searched proceeding. Handling on level of network share with sparse bundles on it is needed. All below applies to Time Machine backup destination on SMB network share. Not tested with AFP instead of SMB. That is:
-)rename old sparse bundle with existing (old) backups to harmless name, e.g. to TMSparseBundle-A, this way it won't conflict anymore with sparsebundle created by Time Machine for from-scratch backups in next step plus 1 (Time Machine ignores and does not touch in any extent these data)
-)do not create new sparse bundle for new backup destination manually (means using DU or other) as it is nothing nor nobody else what/who determines the name of sparse bundle image and who/what initiates it
-)let the Time Machine instead to create new sparse bundle as new backup destination, there is no other way as that
-)connect Time Machine to network share
-)start backup, it will be initial backup (with creation of sparsebundle for backup destination in beginning) into sparse bundle created by tm in previous step minus two - thus backup process of remarkable duration
-)let new backup to complete, verify it, test it, maintain it, use it
-)if some time later one needs to access the old backup in old sparsebundle rename sparse bundle currently used to yet another harmless file name e.g. to TMSparseBundle-B, prior to this disconnect time machine from backup destination
-)rename TMSparseBundle-A to its original name, it is <Mac name>.sparsebundle
-)connect time machine to network share
-)use backup as aimed
Procedure works when Time Machine never in automatic mode and seems to show high automation level. It works best way if for surfing backup history "Enter Time Machine.." the plain-mode Finder does not mount neither underlying network share nor backup sparse bundle.
My strategy is to use time machine backup in passive fashion (only for data recovery) if operating system major version (that one behind digits 10.) differs between backup destination and source. Use backup in usual way (additionally increments generation) if same operating major version on both backup destination as well on backup source side.
Last edited: