Hello,
I will try and explain this simply... I am using latest MacOS 10.12.6 across my home network to a Synology DS215j running DiskStation 6.1 (actually DSM 6.1.3-15152 Update 3).
BC4 is Version 4.2.3 (build 22587).
So using the GUI Interface I have a number of updates / sync sessions that usually update from the Mac to the Synology NAS. Something has happened recently, not sure which update triggered it but this is my typical (manual using the GUI interface) pattern.
I have a fairly large area for our files which has a name that is not Documents or anything like that, lets call it "Possessions" for now, this syncs to the NAS.
It all works well, but there is one new and recent problem, the NAS is set to power down 10 minutes after the last activity, but after using BC4 as I am about to describe, it stays powered up forever... I think I have identified a partial reason, but I don't understand it fully!
So this is what I do, as the "Possessions" area is quite large , I have a number of saved sync sessions ot sync partial areas,
So I start Session 1 with a partial "Possessions" sync (this first sync is where I log in to the "Possessions" mirror on the NAS as it has a different user name and password), then go in BC4 to Session/New Window and fire up another area in "Possessions", perhaps doing this with 3, 4 or even 5 windows open/
All good, the syncs complete, shut the windows one be one and then a cmd Q on the final window to quit BC4.
Now at this point plus 10 minutes the NAS used to shut down, but it doesn't any more... The reason seems to be that the Mac is holding the connection. If I look in /Volumes I find that there are anumber of drives representing the NAS connections, labelled Possessions, Possessions-1, Possessions-2 etc. But these don't clear down when BC exits and this seems to be what keeps the NAS from sleeping.
If I keep a simple "one things at a time" approach then there is only one connection in /Volumes then it clears away and the NAS sleeps?
Any ideas about what I might look at /check next?
Cheers, Derek
I will try and explain this simply... I am using latest MacOS 10.12.6 across my home network to a Synology DS215j running DiskStation 6.1 (actually DSM 6.1.3-15152 Update 3).
BC4 is Version 4.2.3 (build 22587).
So using the GUI Interface I have a number of updates / sync sessions that usually update from the Mac to the Synology NAS. Something has happened recently, not sure which update triggered it but this is my typical (manual using the GUI interface) pattern.
I have a fairly large area for our files which has a name that is not Documents or anything like that, lets call it "Possessions" for now, this syncs to the NAS.
It all works well, but there is one new and recent problem, the NAS is set to power down 10 minutes after the last activity, but after using BC4 as I am about to describe, it stays powered up forever... I think I have identified a partial reason, but I don't understand it fully!
So this is what I do, as the "Possessions" area is quite large , I have a number of saved sync sessions ot sync partial areas,
So I start Session 1 with a partial "Possessions" sync (this first sync is where I log in to the "Possessions" mirror on the NAS as it has a different user name and password), then go in BC4 to Session/New Window and fire up another area in "Possessions", perhaps doing this with 3, 4 or even 5 windows open/
All good, the syncs complete, shut the windows one be one and then a cmd Q on the final window to quit BC4.
Now at this point plus 10 minutes the NAS used to shut down, but it doesn't any more... The reason seems to be that the Mac is holding the connection. If I look in /Volumes I find that there are anumber of drives representing the NAS connections, labelled Possessions, Possessions-1, Possessions-2 etc. But these don't clear down when BC exits and this seems to be what keeps the NAS from sleeping.
If I keep a simple "one things at a time" approach then there is only one connection in /Volumes then it clears away and the NAS sleeps?
Any ideas about what I might look at /check next?
Cheers, Derek
Comment