What I've set up myself is the following:
1) Mount the external drive / NAS samba share / whatever to somewhere
on your filesystem, e.g. /mnt/nasdrive and make sure your system does
this on startup.
2) Create a folder in your new mount folder called 'filestore' (or
move the existing filestore folder from ResourceSpace if you already
have resources)
3) Remove ResourceSpace's own 'filestore' folder
4) Create a symbolic link to the 'filestore' folder on your mounted
folder from the ResourceSpace folder.
To ResourceSpace, nothing has changed, it is still putting files in
the local 'filestore' folder, however they are being stored remotely
on your NAS server.
The above is for a UNIX system but if you're running Windows you can
probably do something similar using NTFS junction points, although I
haven't tried this myself.
Hope this helps.
Dan
Found this on the windows side of things...would this be helpful? Its
for group policy so I am not sure if this works. But posting a snippet
here
Managing Documents with Folder Redirection
Folder redirection is a component of IntelliMirror that allows
administrators to redirect the path of the following folders to a new
location: My Documents (and its subfolders My Pictures, My Music, and
My Videos), Application Data, Desktop, and Start Menu. These folders
are located by default in each user's profile on the local computer.
The most commonly redirected folders are those that contain large
amounts of user data-My Documents and its subfolders. Although it is
not a recommended practice to store large amounts of data on the
Desktop, users in some organizations do, and the Desktop folder can be
redirected as well.
The new location can be another folder on the local computer or a
directory on a network share. Users work with documents on a server as
though the documents were stored on the local drive.
There are benefits to redirecting any folder, but redirecting the My
Documents folder can be particularly advantageous:
* No matter which computer on the network the user logs on to, the
user's documents are always available.
* You can use Group Policy to set disk quotas and limit the amount
of space taken up by users' folders.
* You can back up data stored on a shared network server as part
of routine system administration. This is safer and requires no action
on the part of the user.
* User data can be redirected to a hard disk on the user's local
computer other than the disk where the operating system files are
located. This protects the user's data if the operating system must be
reinstalled.
This might work, I am going to give it a try. There is a tool someone
made that might do what we need (at least on NTFS)
http://www.microsoft.com/technet/sysinternals/FileAndDisk/Junction.mspx
Introduction
Windows 2000 and higher supports directory symbolic links, where a
directory serves as a symbolic link to another directory on the
computer. For example, if the directory D:\SYMLINK specified C:\WINNT
\SYSTEM32 as its target, then an application accessing D:\SYMLINK
\DRIVERS would in reality be accessing C:\WINNT\SYSTEM32\DRIVERS.
Directory symbolic links are known as NTFS junctions in Windows.
Unfortunately, Windows comes with no tools for creating junctions -
you have to purchase the Win2K Resource Kit, which comes with the
linkd program for creating junctions. I therefore decided to write my
own junction-creating tool: Junction. Junction not only allows you to
create NTFS junctions, it allows you to see if files or directories
are actually reparse points. Reparse points are the mechanism on which
NTFS junctions are based, and they are used by Windows' Remote Storage
Service (RSS), as well as volume mount points.
I am beginning to suspect that I can not create junction points to a
network location with Windows.
I found a little tool called Junction Link Magic that makes creating
junction points a snap. For a test I created C:\test and C:\target,
linked the two with this tool and it works.
Then I tried c:\test R:\target (R being a mapped drive to a network
location and I am getting an error telling me that I could not create
a link.
Any one else out there have any ideas for external storage?
E.g. link c:\test to \\myserver\someshare\somefolder
Dan
I am working with our IT person. We are going to try to hook the
server directly to the SAN via fiber and see if we can mount the SAN
drive. Maybe that will work. But wow, I dont think that many people
would be able to do that.
Interestingly, Windows Vista has junction points now part of the OS.
Here's an article that might be interesting:
http://articles.techrepublic.com.com/5100-6346_11-5388706.html
and possibly this one too:
http://support.microsoft.com/kb/205524
It's important to keep in mind that NTFS junction points are designed
to work only on local hard disks. They don't work across a network. In
other words, you can't create a junction point on an NTFS drive that
points to a network drive.
Let you know how it goes.
--
ResourceSpace: Open Source Digital Asset Management
http://www.resourcespace.com
---
You received this message because you are subscribed to a topic in the Google Groups "ResourceSpace" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/resourcespace/NUqAvvpFUuQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to resourcespac...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/resourcespace/169867a3-ce0c-43fe-9bad-5ff18b81d4f2%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "ResourceSpace" group.
To unsubscribe from this group and stop receiving emails from it, send an email to resourcespac...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/resourcespace/CAOuPBFDVqMGtZBwN3wHSD9FvWsohHduGL8WY-QeOeuaSwQsnTQ%40mail.gmail.com.