List Info

Thread: Hard Linking a folder on one server to a folder on another server.




Hard Linking a folder on one server to a folder on another server.
user name
2006-01-13 12:18:31

Thanks will have a look at DFS.  Would this work to have a mapping of say \domaindfscompany to F: and the contents of this share to come from various places.

 

e.g.

 

F:Folder1  would actually link to a share on Server1.   and

F:Folder2  would actually link to a share on Server2.

 

Thanks.


Steve

 


From: windows2000-bouncefreelists.org [mailto:windows2000-bouncefreelists.org] On Behalf Of Sorin Srbu
Sent: 13 January 2006 11:52
To: windows2000freelists.org
Subject: [windows2000] Re: Hard Linking a folder on one server to a folder on another server.

 

I'd use dfs instead.

 

Then Company1 would always be referred to as <\yourdomain.local.or.what.everdfscompany1&gt; and it could point to <\filesvr1companythis or that> or wherever you choose to keep it. In any case, you'd still be using <\yourdomain.local.or.what.everdfscompany1&gt; and the actual share could be anywahere. The pointer ref's would be taken care of automatically. You'll never have to remember where that particaulr file is physically located, just the dfs-pointer.

 

HTH.

 

 

-----Original Message-----
From: windows2000-bouncefreelists.org [mailto:windows2000-bouncefreelists.org]On Behalf Of Steve Rance
Sent: Friday, January 13, 2006 12:40 PM
To: Windows2000freelists.org
Subject: [windows2000] Hard Linking a folder on one server to a folder on another server.

Any ideas on this one;

 

I have two file servers, and have moved a number of the data folders from one to the other (running out of space on FILESVR1).  My question- is it possible to make it look and act like the moved folders are still where are were.

 

To explain fuller;

 

F: is mapped as \FILESVR1Company

G: is mapped as \FILESVR2Company

 

If I had F:AFolder which was moved to G:AFolder can I make it look and act like “AFolder” is still on the F: drive.&nbsp;  I know that I can make a shortcut to it but the two problems with that is (1) It is treated as a file in the listing – ie in with the files and not folders), and (2) if you use UP to go back you go up to G: and not F:.

 

FILESVR1 is a Windows 2000 Server, and FILESVR2 is Windows Server 2003.

 

Thanks,


Steve

 

Hard Linking a folder on one server to a folder on another server.
user name
2006-01-13 12:28:14
You can map dfs-shares to drive letters. Works like a charm.
 
I think you mean "links". Each actual domain root or standalone dfs root can have several links under it. If you use a domain I'd use the domain dfs type, as you can also use automatic replication and failover-locations for your files and docs.
 
Ie:
 
 
 
 
Each of the links, will be a folder and visible in the \yourdomain.local.or.what.everdfscompany1folder, and dbl-clicking one of them will take you to it as if it would be just any folder/file (although you won't see where it actual is, w/o checking the mapping with the dfs-snapin in mmc).
 ;
This is a bit difficult to explain with words. It's so much easier to show.
 ;
 ;
 
-----Original Message-----
From: windows2000-bouncefreelists.org [mailto:windows2000-bouncefreelists.org]On Behalf Of Steve Rance
Sent: Friday, January 13, 2006 1:19 PM
To: windows2000freelists.org
Subject: [windows2000] Re: Hard Linking a folder on one server to a folder on another server.

Thanks will have a look at DFS.  Would this work to have a mapping of say \domaindfscompany to F: and the contents of this share to come from various places.

 

e.g.

 

F:Folder1&nbsp; would actually link to a share on Server1.&nbsp;  and

F:Folder2&nbsp; would actually link to a share on Server2.

 

Thanks.


Steve

 


From: windows2000-bouncefreelists.org [mailto:windows2000-bouncefreelists.org] On Behalf Of Sorin Srbu
Sent: 13 January 2006 11:52
To: windows2000freelists.org
Subject: [windows2000] Re: Hard Linking a folder on one server to a folder on another server.

 

I'd use dfs instead.

 

Then Company1 would always be referred to as <\yourdomain.local.or.what.everdfscompany1&gt; and it could point to <\filesvr1companythis or that> or wherever you choose to keep it. In any case, you'd still be using <\yourdomain.local.or.what.everdfscompany1&gt; and the actual share could be anywahere. The pointer ref's would be taken care of automatically. You'll never have to remember where that particaulr file is physically located, just the dfs-pointer.

 

HTH.

 

 

-----Original Message-----
From: windows2000-bouncefreelists.org [mailto:windows2000-bouncefreelists.org]On Behalf Of Steve Rance
Sent: Friday, January 13, 2006 12:40 PM
To: Windows2000freelists.org
Subject: [windows2000] Hard Linking a folder on one server to a folder on another server.

Any ideas on this one;

 

I have two file servers, and have moved a number of the data folders from one to the other (running out of space on FILESVR1).  My question- is it possible to make it look and act like the moved folders are still where are were.

 

To explain fuller;

 

F: is mapped as \FILESVR1Company

G: is mapped as \FILESVR2Company

 

If I had F:AFolder which was moved to G:AFolder can I make it look and act like “AFolder” is still on the F: drive.&nbsp;  I know that I can make a shortcut to it but the two problems with that is (1) It is treated as a file in the listing – ie in with the files and not folders), and (2) if you use UP to go back you go up to G: and not F:.

 

FILESVR1 is a Windows 2000 Server, and FILESVR2 is Windows Server 2003.

 

Thanks,


Steve

 

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )