When you reinitialize the cache... it restarts the computer, but when it restarts the computer, we lose the Z drive because it is run every time the computer boots in a script rather then being apart of the permanent configuration of the computer.

So when the script reboots, it basically starts that drive off fresh with no predefined configuration, since there are no predefined configurations it is not made available to work offline.

Then, when you go to resynchronize the drive it again takes up all of the hard drive space left on the computer leaving it with nothing, the reason it worked with machin1 at first was because it has 10gigs of free space and it uses 7gigs of space while machine2 only has 4 gigs of free space, so the synchronization completely eats the entire hard drive.

Even if the offline cache didn't eat the entire hard drive like machine1, it is safe to say that it eventually will, which will ultimately defeat the purpose anyways.

I guess the solution I am looking for is to enable offline files without downloading the mass of data off of the server onto the hard disk of our machines, so if our server does go down it will continue function normally.

Well if you want it to stay mapped, change that script to persistent:yes

Then it should keep any configuration data you have for the offline settings... as to continue writing to the offline cache I think it's possible, but not necessarily in the way you think. configure the drive not to force a sync if the server goes offline the options under offline file settings - it should, in theory, continue adding info to the offline cache until it resyncs. If you try to add or access more data than there is actually room for it won't work... If you're locking the 7 gigs of data for writing, but only actually changing 2, it will still have the full 7 locked.

Hm. Not sure! But change it to persistent and try tweaking the offline settings.

I'm not entirely sure of your situation, but I'd say configuring the limits of how much space the drive can store would be a good start. You can also configure a custom response for a certain drive going offline, such as not syncing, or even better disabling offline files for that drive alone. :)

We have a machine that sends data to our server when someone is running an experiement. The total data on our server as of right now is 7 gigs. We only want to hold 2 gigs of the most recent data on our local machine in the offline cache. The computer that runs the machine is designed specifically for this machine and has very little hard drive space (20 gigs).

So if the server goes down, while we are running an experiement we would like it to continue to write the data to the offline cache automatically, so we aren't losing the data from that experiement. I'm not sure this is even possible.

The problem is even though we are setting the cache to only hold 2 gigs, When we reinitialize the cache it downloads all 7 gigs anyways and asks to restart the computer. And when the drive is remapped it is no longer set to offline mode.

Well if you want it to stay mapped, change that script to persistent:yes

Then it should keep any configuration data you have for the offline settings... as to continue writing to the offline cache I think it's possible, but not necessarily in the way you think. configure the drive not to force a sync if the server goes offline the options under offline file settings - it should, in theory, continue adding info to the offline cache until it resyncs. If you try to add or access more data than there is actually room for it won't work... If you're locking the 7 gigs of data for writing, but only actually changing 2, it will still have the full 7 locked.

Hm. Not sure! But change it to persistent and try tweaking the offline settings.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.