[Deploying Sakai] deprecating a bodyVolume
cousinea at umich.edu
Wed Jan 5 07:50:07 PST 2011
This is correct. As long as the old volume(s) are still accessible to the app servers, you should be ok.
At U-M we have historically created a new volume each calendar year, so we only have one volume configured at a time. Previous volumes remain NFS-mounted on the app servers so older content is still accessible.
Our configuration is currently:
bodyVolumes at org.sakaiproject.content.api.ContentHostingService=fs2011
On Jan 5, 2011, at 10:37 AM, John F. Hall wrote:
> Our production server was initially set up with a single content volume:
> bodyVolumes at org.sakaiproject.content.api.ContentHostingService =vol1
> When usage hit 70% we added two more (vol2,vol3) and new files are now
> being spread across all three successfully.
> However, I'd like to have Sakai stop putting new files on vol1 since
> it's over 70% full, but still have the content currently there be available.
> I think that simply taking 'vol1' out of the list is what I'd want to do
> bodyVolumes at org.sakaiproject.content.api.ContentHostingService=vol2,vol3
> since existing vol1 content references would still be in the database.
> Testing on our development server seems to show this works, but I'd like
> to get some confirmation that this is indeed the right thing to do. I
> couldn't find anything in the documentation.
> Could someone verify if this is (or isn't) what I should do?
> ______________ John F. Hall ______________
> Programmer/Analyst III, IT-Web Development
> University of Delaware
> production mailing list
> production at collab.sakaiproject.org
> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
Application & Web Infrastructure, Core Services and Infrastructure
Infrastructure Services, Information and Technology Services
University of Michigan
More information about the production