This will be long and detailed, so bear with me.
Recently our company expanded, acquiring a new facility. We run a VPN between the facilities and both are seperate internet connections.
The staff moving to that facility needed their current project folders moved to a new file server located in the facility, and some users in the existing facility would need access to it from time to time.
So our solution was, due to limited bandwidth, to setup a DFS replication set for those particular projects.
This is where I think I myself went wrong, and thus disaster struck.
Our primary file server is running Server 2k3 R1 (server1), the new file server is running Server 2k3 R2(server2).
We wanted server2 to be the Primary source/host of the information, so I created the DFS replication using that server as the host, even though the data existed on server1.
I created the DFS root, shared all the necessary files, and added the targets. Since they were running different releases, I had to use the R1 version of DFS.
After everything was pathed, shared etc, we enabled replication, and the pre-existing data was moved into a folder labeled "Pre-existing_data_..." on server1.
I copied the data back into it's root folders on server1, and instantly saw that server2 began to replicate.
Since this was roughly 30 GB of data, it was not moving as fast as we would have liked (this is crunch time) and so we decided to copy the data over to server2 by hand, and then enable DFS.
I stopped DFS replication, and went to the directories on server1, and noticed that there was significant file loss. I found the bulk of these files on server2.
This basically meant I had to restore those two directories from backups we had made, and this is where I sit now.
I'm hesistant to restart the service as this catastrophy is likely getting me in enough trouble as it stands.
Long story short, I need to know why those files were missing off of our server1, I'm assuming it has something to do with the way I setup the replication.
Recently our company expanded, acquiring a new facility. We run a VPN between the facilities and both are seperate internet connections.
The staff moving to that facility needed their current project folders moved to a new file server located in the facility, and some users in the existing facility would need access to it from time to time.
So our solution was, due to limited bandwidth, to setup a DFS replication set for those particular projects.
This is where I think I myself went wrong, and thus disaster struck.
Our primary file server is running Server 2k3 R1 (server1), the new file server is running Server 2k3 R2(server2).
We wanted server2 to be the Primary source/host of the information, so I created the DFS replication using that server as the host, even though the data existed on server1.
I created the DFS root, shared all the necessary files, and added the targets. Since they were running different releases, I had to use the R1 version of DFS.
After everything was pathed, shared etc, we enabled replication, and the pre-existing data was moved into a folder labeled "Pre-existing_data_..." on server1.
I copied the data back into it's root folders on server1, and instantly saw that server2 began to replicate.
Since this was roughly 30 GB of data, it was not moving as fast as we would have liked (this is crunch time) and so we decided to copy the data over to server2 by hand, and then enable DFS.
I stopped DFS replication, and went to the directories on server1, and noticed that there was significant file loss. I found the bulk of these files on server2.
This basically meant I had to restore those two directories from backups we had made, and this is where I sit now.
I'm hesistant to restart the service as this catastrophy is likely getting me in enough trouble as it stands.
Long story short, I need to know why those files were missing off of our server1, I'm assuming it has something to do with the way I setup the replication.
