Errors when trying to re-enable DFS-R
I am trying to restore DFSR after the complete failure of a hard drive hosting a virtual machine. This is Server1. There are only two machines in the network, and the other is Server2 which was not affected by the failure. The DFS-R is between the Data drives only.
The data was on a virtual drive on another hard drive and is safe [albeit a few days behind]. the original data drive and contents have been successfully attached to the virtual machine
I am getting the following error when I do a health diagnostic report [attached] using Server 1 The DFS Replication service stopped replication on replicated folder Downloads at local path f:\Downloads due to Error ID: 9098 (A tombstoned content set deletion has been scheduled). Event ID: 4004
From Server 2, I get the following error "The DFS Replication service stopped replication on replicated folder Downloads at local path f:\Downloads due to Error ID: 9098 (A tombstoned content set deletion has been scheduled). Event ID: 4004"Server2Health-ad.aedc.com_downloads.html
My current fresh data is on Server2, and I am getting the error on the newly installed Server1. Server 2 now hosts the FSMO items, and is the most current server.
What is the best solution to remedy this?
Server1Health-ad.aedc.com_downloads.html
The data was on a virtual drive on another hard drive and is safe [albeit a few days behind]. the original data drive and contents have been successfully attached to the virtual machine
I am getting the following error when I do a health diagnostic report [attached] using Server 1 The DFS Replication service stopped replication on replicated folder Downloads at local path f:\Downloads due to Error ID: 9098 (A tombstoned content set deletion has been scheduled). Event ID: 4004
From Server 2, I get the following error "The DFS Replication service stopped replication on replicated folder Downloads at local path f:\Downloads due to Error ID: 9098 (A tombstoned content set deletion has been scheduled). Event ID: 4004"Server2Health-ad.aedc.com_downloads.html
My current fresh data is on Server2, and I am getting the error on the newly installed Server1. Server 2 now hosts the FSMO items, and is the most current server.
What is the best solution to remedy this?
Server1Health-ad.aedc.com_downloads.html
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The data size is just under 500 GB
If failed server is domain controller, did you promote new server as domain controller?
And if sysvol is running with frs or dfsr and if it working correctly?
And if sysvol is running with frs or dfsr and if it working correctly?
ASKER
Both servers were domain controllers. I seized the FSMO roles from the failed Server1 with Server2. Most of the users did not notice that Server1 was down.
Both server2 and server1 have their own virtual Data drives on separate physical drives [different boxes]. I added the Server1 Data drive to the virtual machine, and all data was present. That data is now a few days old.
I rebuilt Server1, and then attempted to add it to the DFSR replication. Server2 has the current data, so I set it as the dominant Server, and had anticipated that adding the folders from Server1 as Replication groups would work. I noticed a test file that I had created for the "Common" folder had not replicated from Server1 to Server2, so ran the health report. I then added Downloads as a replication group and ran the health report, but found the errors.
Both server2 and server1 have their own virtual Data drives on separate physical drives [different boxes]. I added the Server1 Data drive to the virtual machine, and all data was present. That data is now a few days old.
I rebuilt Server1, and then attempted to add it to the DFSR replication. Server2 has the current data, so I set it as the dominant Server, and had anticipated that adding the folders from Server1 as Replication groups would work. I noticed a test file that I had created for the "Common" folder had not replicated from Server1 to Server2, so ran the health report. I then added Downloads as a replication group and ran the health report, but found the errors.
Have you tried my 1st comment?
ASKER
Not yet, I am still doing the backups. On your first comment, I would want Server2 to replicate to Server1 in this case, because Server2 has the current data, or would I need to allow Server1 to replicate the empty downloads folder and then restore the backed up data, or will the current data on Server2. The backups should be finished by late tonight, and I will try your suggestion as soon as they are done.
Thanks
Thanks
Backup is not for restoring data
It is only for safety if in case anything happens wrong and you lose data on server 2 which is up to date as compared to server 1
Follow 1st comment and it should do the needful
It is only for safety if in case anything happens wrong and you lose data on server 2 which is up to date as compared to server 1
Follow 1st comment and it should do the needful
ASKER
Agreed
ASKER
Thank you for your prompt assistance and persistence with my issue. It appears to be working. I will do the same process with any other directories as I continue the rebuild.
ASKER
Does this complicate things. Server 2 is the most up to date data that I need to save. I will make a backup copy for the data drives on each server
Server1-dfs.jpg