locked
DFS Replication Total Files Size RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi, 

    I hope someone can help me out with this issue. We have a new file server(It's empty and no any files on it), and I setup DFS replication between old file server and new one. After the replication process started, it looks fine that two file server replicated. The total size on old one is around 1.5TB, and I can see that on new server hard drive space has been taken around 2.1TB. The problem is when I checked the Main User Home folder(all users home folder is under it) properties on new server, it only shows total size is 150GB. Why I only see 150GB, but hard disk space status shows 2.1TB has been taken on new file server? I ran the DFS Replication Diagnostic Report, and everything seems fine for me. Please help and thank you.

    swl2011  

    Thursday, January 19, 2012 5:11 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    You will probably have to take ownership, which is best accomplished using the takeown command.

    takeown /F * /U domain\user /R /D Y

    Run this on the root of the drive to take ownership of everything.  Alternatively, replace the wildcard asterisk with the actual directory.

    After you have taken ownership, you can also add the appropriate account to the ACL with the Full Control permission. Assuming Server 2008:

    ICACLS *  /T /grant domain\user:F /C

    You can also use xcacls or cacls, which have similar syntax.  ICACLS is the preferred method in Vista and on.

    • Proposed as answer by ptilsen Friday, January 20, 2012 3:33 PM
    • Marked as answer by swl2011 Friday, January 20, 2012 3:39 PM
    Friday, January 20, 2012 3:33 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Several possibilities come to mind that can explain the difference.

    Hard links, which are a part of how Windows function, can cause some bizarre results when comparing directory sizes to used drive space.  However, you will typically see a set of directories show more used space that the volume does, rather than the other way around as you are experiencing.

    Another possible cause is the staging folder used by DFS, as well as conflict and deleted and pre-existing folders.   These can explain why the old server is 1.5TB and the new one is less, but they really don't explain why the difference is so drastic.

    The most likely cause I'm coming up with immediately is that you do not have sufficient rights to view the users' folders on the new server.  If you are browsing over a share, you might not have share-level rights.  Locally, you might not have NTFS rights.

    Friday, January 20, 2012 3:35 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Ptilsen,

    Thanks for reply.

    Yes, it looks like I don't have sufficient rights to view folders. I also found out that after all folders replicated to new server, their ownership were removed. When I went into Advance Security Settings, and Owner option, it shows "Unable to display current owner". I tried to change it to Administrators group, and it didn't let me change it. Is it another reason that I can't see all stuffs?

    swl2011

    Friday, January 20, 2012 2:57 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You will probably have to take ownership, which is best accomplished using the takeown command.

    takeown /F * /U domain\user /R /D Y

    Run this on the root of the drive to take ownership of everything.  Alternatively, replace the wildcard asterisk with the actual directory.

    After you have taken ownership, you can also add the appropriate account to the ACL with the Full Control permission. Assuming Server 2008:

    ICACLS *  /T /grant domain\user:F /C

    You can also use xcacls or cacls, which have similar syntax.  ICACLS is the preferred method in Vista and on.

    • Proposed as answer by ptilsen Friday, January 20, 2012 3:33 PM
    • Marked as answer by swl2011 Friday, January 20, 2012 3:39 PM
    Friday, January 20, 2012 3:33 PM