What is backlog in DFSR?

What is exactly backlog in DFSR? Is the files that are not replicated yet to the target server or if we change security on a file and this is not finished to replicate can be considered as a backlog too?

What I don't understand the report show me backlogs but when I compare the folder that suppose to contain backlogs there are similar.
For example I run this cmd:
dfsrdiag backlog /rgname:<REPL_GROUP> /rfname:<REPL_FOLDER> /smem:<SRV_A> /rmem:<SRV_B> [/v]
When I check on one of the folders like:
\\server01\foldetIT\Tool\ and compare to \\server02\foldetIT\Tool\
Check the files that show in backlog report and they are similar. So my question is what DFSR consider as a backlog if I see the same file (same security, same date and size)?

Similar Messages

DFSR issues - Backlog reset

Hi,
I have some fileservers with a huge amount of data. Both servers are Win2K8 R2. Topoligy is fullmesh. All works fine and pretty fast.
On 2 servers I get a backlog for files that do not (longer) exist on the servers. I guess they were deleted during the initial replication process by a user. So they were indexed but later not found. The amount of this backlog files is small (5 and
96).
Is there any way to clear or reset the backlog without reconfiguring the DFSR-membership or replication-group.
I think it should be possible, because the dfrs.db delivers the backlog data, so there must be away to clean this data.
I won't reconfigure the memberships because there are about 5-12 million files on each server and I would need a time window for about 4-5 days.
Any hints?
Sascha Nill
Senior System Administrator

In commons, Ned replied the question "Is there a way to clear the backlog so dfs starts fresh after a pre-stage?"
If you want to start fresh and remove your backlog, you can remove the replica set, get your 'master' data onto one box, then use NTBACKUP to create a BKF of it, move or delete the 'bad' data off the other server(s), then copy the BKF out to them and restore
the data to the correct spot. Then you create the replica and choose the 'master' server as primary - then the data should all sync up, and since it's indentical there shouldn't be a long period before initial replication is done and you;re back in business.
If this all sounds nutso and dangerous, don't hesitate to open a case with us here for backend support.
-Ned
Shaon Shan |TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Windows 2012 R2 DFSR and backlog for Read only Server

Hi All
I have strange situation - i have 2 servers running Win2012R2 with 2 folders replicated by DFSR ( + Deduplication Enabled on both servers). Second Server folders set to ReadOnly. But second server showing high backlog waiting replication to Server1 -
in the same time Staging Folder is empty. When i'm disabling membership for this server, and enabling back - some time it is showing 0 backlog - all is ok, but then it resumes to show hight backlog again. How i can fix it?
Best Wishes, Andrew Golubenkoff

Hi,
Is there any error message in the Event Log? Since the got the status 5 ( "5: In Error" ), you could try to rebuild the DFSR database to resolve the issue.
For more detailed information, you could refer to the thread below:
DFSR - Database Corrupt
https://social.technet.microsoft.com/Forums/windowsserver/en-US/b69839aa-f050-419c-9344-6b7bf067c318/dfsr-database-corrupt?forum=winserverfiles
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

DFSR - backlog and sharing violations

Hi,
i have a Replication Group Setup with a lot of sharing violations (accessed files) and lately i also saw a list of backlogged files. I also noticed, that a small txt file i created wasnt replicated either. It took a few hours and everything was replicated,
so in General it works.
My question: is it safe to say, that when having a large amount of sharing violations and backlog files that also normal files will be queued at the end of the Journal/list and not treated with Preference ? Also in normal circumstances those not accessed
files would be replicated very fast, but due to backlogs delayed ?
thanks for clarification.
Marcus

Hi Marcus,
With enough sharing violations though, DFSR can start spending more time retrying locked files than it does replicating unlocked ones, to the detriment of performance.
To determine the real state of the file, use the DFSRDIAG BACKLOG command to check for sharing violations. The command output provides a list of the first 100 files that are not replicated.
You could refer to the article below to troubleshoot the issue.
Top 10 Common Causes of Slow Replication with DFSR
http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

DFSR Backlog Stuck on Non-Existent Folders

I have two 2008r2 servers setup in a full-mesh multipurpose replication group. (01 and 02). 01 was the source server. The initial sync just finished last night and there are 2 folders that do not appear on either server but they are stuck in the backlog of
changes being pushed from 02 to 01. The backlog from 01 to 02 is clear and is replicating perfectly.
I've attempted rebooting 02, this did nothing.
The Event viewer for both servers contains nothing helpful.
I've attempted creating and deleting the "batman" folder hoping that would clear it out. It didn't. When I created it on 01 it pushed it to 02. When I created it on 02 it created a redundant entry on the backlog.
There were some other random files stuck in the backlog. They were unnecessary so I just deleted them from 01 and it cleared them from the backlog. I was hoping to just do the same with the folders...
http://i.stack.imgur.com/ji41m.png
Is there somewhere else I can look to help find why those folders are stuck?
Edit:
I also found this from the DFSR debug log (This occurred while the initial sync was finishing up last night).
20140513 23:27:39.254 2372 CSMG 6769 ContentSetManager::Initialize csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} csName:Art rootPath:E:\Art state:InitialSync(Sync) ptr:0000000000F83D50
20140513 23:27:39.254 2372 CSMG 5547 ContentSetManager::CheckContentSetState Updating content set record csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} csName:Art ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000
20140513 23:27:39.254 2372 CSMG 5590 ContentSetManager::CheckContentSetState Content set csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} state:InitialSync(Cleanup)
20140513 23:27:39.395 2372 STAG 2594 Staging::ScanStagingDirectory Staging space usage is: 285794033664
20140513 23:27:39.395 2372 CSMG 2960 ContentSetManager::StartInitialSyncCleanup csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
20140513 23:27:39.395 448 ISYN 153 InitialSyncCleanupTask::Run csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
20140513 23:27:45.760 448 ISYN 453 InitialSyncCleanupTask::MoveOut Moving \\.\E:\Art\Artist Files\Christine\batman to pre-existing:0x9000000156B80 csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
20140513 23:27:45.776 448 CSMG 547 ContentSetManager::DeleteChildren LDB Updating ID Record:
+ fid 0x1000000001DF2
+ usn 0x0
+ uidVisible 0
+ filtered 0
+ journalWrapped 0
+ slowRecoverCheck 0
+ pendingTombstone 1
+ internalUpdate 0
+ dirtyShutdownMismatch 0
+ meetInstallUpdate 0
+ meetReanimated 0
+ recUpdateTime 20140505 11:56:12.179 GMT
+ present 1
+ nameConflict 0
+ attributes 0x10
+ ghostedHeader 0
+ data 0
+ gvsn {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
+ uid {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
+ parent {29CFABC2-0180-41C7-A9CE-21DD92783892}-v6880183
+ fence Initial Sync (1)
+ clockDecrementedInDirtyShutdown 0
+ clock 20140501 00:01:02.367 GMT (0x1cf64d070b1522c)
+ createTime 20140124 09:37:42.441 GMT
+ csId {2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
+ hash 00000000-00000000-00000000-00000000
+ similarity 00000000-00000000-00000000-00000000
+ name batman
+
20140513 23:27:45.776 448 LDBX 4435 Ldb::InsertWalkerJob Inserting dirWalkerJob:uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133 moveType:MoveOut (2) at time:20140514 03:27:45.776
20140513 23:27:45.807 448 DIRW 647 DirWalkerTask::QueueMoveoutJob Queueing move-out uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133 fid:0x1000000001DF2
20140513 23:27:45.807 2372 DIRW 317 DirWalkerTask::Run Start walking directory.
20140513 23:27:45.807 2372 DIRW 1373 DirWalkerTask::MoveoutStep Starting to process move-out job. uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 1398 DirWalkerTask::MoveoutStep Iterating children of uid: {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 2764 DirWalkerTask::TombstoneOrDelete LDB Updating ID Record:
+ fid 0x1000000001DF2
+ usn 0x0
+ uidVisible 0
+ filtered 0
+ journalWrapped 0
+ slowRecoverCheck 0
+ pendingTombstone 0
+ internalUpdate 0
+ dirtyShutdownMismatch 0
+ meetInstallUpdate 0
+ meetReanimated 0
+ recUpdateTime 20140505 11:56:12.179 GMT
+ present 0
+ nameConflict 1
+ attributes 0x10
+ ghostedHeader 0
+ data 0
+ gvsn {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1376267
+ uid {BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
+ parent {29CFABC2-0180-41C7-A9CE-21DD92783892}-v6880183
+ fence Default (3)
+ clockDecrementedInDirtyShutdown 0
+ clock 20140514 03:27:45.776 GMT (0x1cf6f247911f746)
+ createTime 20140124 09:37:42.441 GMT
+ csId {2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB}
+ hash 00000000-00000000-00000000-00000000
+ similarity 00000000-00000000-00000000-00000000
+ name batman
+
20140513 23:27:45.807 2372 DIRW 101 DirWalkerTask::Job::Finish MoveOut csId:{2D9CF1D7-50E2-4B3E-AC6B-3D60C6B026EB} uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 893 DirWalkerTask::RemoveJob Removing job type:2 uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 LDBX 4472 Ldb::DeleteWalkerJob Deleting dirWalkerJob. uid:{BE36C74B-B5FC-4E8A-8735-039CF9FB3982}-v1264133
20140513 23:27:45.807 2372 DIRW 364 DirWalkerTask::Run Exit.

Hi,
From the log, it is trying to move E:\Art\Artist Files\Christine\batman to pre-existing folder, which means your Server01 is the primary server and the folder exists on server02 before setup the initial replication (and it does not exist on server01).
Could you find the folder in pre-existing folder on server02? It is a hidden folder.
If issue still exists, try to set your server01 as Primary again to see if replication could be re-performed to get it fixed:
Dfsradmin Membership Set /RGName:<RG Name> /RFName:<RF Name> /MemName:<Member Name> /IsPrimary:True
If you have any feedback on our support, please send to [email protected]

DFSR with two members, both in Initial replication state?

We have in total 3 servers replicating a given folder, one server has its replication in a completely broken state because of some DB error on its volume.
Now, out of two servers for the above replicated folder, both are in Initial repliction, the state '2' as in the output of command - Wmic /namespace:\\root\microsoftdfs path dfsrreplicatedfolderinfo get replicationgroupname,replicatedfoldername,state
- Not any errors at all in the logs/diags.
Is this supposed to be in this state, under any circumstances? Should I wait for some more time (, in fact this condition existed for almost last two months with backlog counts growing in each direction) ? Or should I rush ahead and designate the server
with latest content as primay?
If I need to do something immediately, what is the best way to do it?

Hi,
As you said it is the result of corrupted DFSR database. Try following steps to reset it:
1. Stop and ALSO disable the DFSR service on a server you would like to set it as Primary (called ServerA) (don't just simply stop it)
2. In Windows Explorer open the specific drive
3. Right click on the "System Volume Information" directory and select Properties\Security
Note: You might need to select the option for "Show hidden files, folders or drives" and also uncheck "Hide protected operating system files" in the folders view options to be able to even see the "System Volume Information" directory.
4. Grant your user account that you're logged in with (if a member of Administrators group this will also suffice) "Full Control" to the "System Volume Information" directory.
Note: You may get an error on setting security on some files - this is expected.
5. Open an elevated/Administrative command prompt. Switch to the "<drive letter>:\System Volume Information" directory
6. Type the command "rmdir DFSR /s"
7. Enable and re-start the DFSR service on <ServerA> server
8. We will then set the <ServerA> server as the Primary member with dfsradmin.exe utility –
Dfsradmin Membership Set /RGName:<RG Name> /RFName:<RF Name> /MemName:<Member Name> /IsPrimary:True
Note: Files will be replicated from ServerA to all other targets. So if there is any newer file on other target servers, backup before starting replication.
If you have any feedback on our support, please send to [email protected]

DFSR Question about the DFSRPrivate folder

Hello all and thanks in advance for any info you may provide.
I am using DFSR for first time and I face an issue with the replicated data and the source data. I want to clarify that I am using DFSR only to migrate data to a new file server and after the replication is completed I will decommission the olf File
Server.
My problem is that when I go to check the source and the destination data, they don't have the same size (which is expected, as I thought that some files, if they are opened or in use, they cannot be replicated). Well, it seems that this is not true,
because I checked it in a test environment. So, after I tested it and I saw that everything is replicated, even the opened files, I was wondering why the source and the destination data are not the same. I believe that there's not any problem if
I miss 500-600 files, because these files may be temp files, or bak files. When I run the report, I see that the files that are not replicated are basicaly pdf,docx,xlsx files. So, why these files are not replicated?
A colleague explained me that the difference between the source and destination data occurs because I have left the DFSRPrivate folder which contains the staging folder in its original location in the replicated folder. He advices me to change this, which
is a huge workload for me now. My question is, does my colleague have right? Shall I change it? If you leave the staging folder to its original place, will this cause any trouble?
Thank you all!

I would not move the staging folder. I have NEVER seen a Microsoft document that recommends that, for any reason.
Have you checked the DFS Replication logs in Event Viewer (under applications and services logs)? Do you see a lot of 4304s? That may be the reason that the pdf, docx and xlsx files aren't getting replicated, they may be in use. (the same file
on more than one server)
How is replication progressing? Is there a backlog? There is some information in this article on using the backlog command: http://blogs.technet.com/b/askds/archive/2007/10/05/top-10-common-causes-of-slow-replication-with-dfsr.aspx
Also, to check what state the replication process is in, use this command:
wmic /namespace:\\root\microsoftdfs path DfsrReplicatedFolderInfo get replicatedFolderName, State
0: Uninitialized
1: Initialized
2: Initial Sync
3: Auto Recovery
4: Normal
5: In Error

DFSR Error : Error: 9098 (A tombstoned content set deletion has been scheduled)

Hello,
We are getting this error on one of our DFSR shares and am not sure how to get this fixed. We have over 30 different shares replicating and all of them are fine except for one. I have tried to remove the Replication and the namespace and have recreated them
both and continue to get the same error. This is what is in the event logs on the server;
The DFS Replication service stopped replication on the replicated folder at local path E:\SHARE\Sharelocation.
Additional Information:
Error: 9098 (A tombstoned content set deletion has been scheduled)
Additional context of the error:
Replicated Folder Name: Sharelocation
Replicated Folder ID: 9BDA3E5A-8103-481F-84B2-269AE8A3BBC8
Replication Group Name: SHARE
Replication Group ID: C25E73B7-5B65-4299-A1BE-76E723443B02
Member ID: 568CC517-3329-42A4-ABAD-633CB3D1EF2E
If anyone has any suggestion on how to get this working again it would be greatly appreciated.

Here is a short summary of what I did:
Look in Event Viewer and identify all the replication groups/folders that are giving the tombstone error. Once you have them identified, go into DFS Management GUI and completely delete the replication group
associated with that folder. You do not need to delete the DFS Namespace for that folder, just the replication functionality of that namespace folder. If you have other replication groups in your DFS-R that do not get the 9098 errors, then you do not have
to do this for these folders.
Stop DFSR services (you may need to kill the service using the taskkill command if it hangs when it tries to stop).
Give yourself permissions to the hidden System Volume Information folder. If you're account is under the domain admins group, you can simply add the security group.
This folder exists on all servers that is a member of the replication group. In my situation, 2 of the 3 servers didn't show this folder as existing even when I enabled to see hidden folders. If this happens to you,
the server is lying to you that it's not there. It is there. Don't listen to it. My suggestion is to download and use the 7-zip file manager. It will see the folder and will help you set the permissions to
it as well as delete files that are longer than 256 characters, which is an issue if you do the next step from the command line).
Note, after you set the permissions, it might tell you that you still don't have access to that folder. Just close out of 7-zip and open it back up. It should let you in that folder as well as its subfolders.
Once you have access to that folder, go ahead and delete the DFSR folder that resides underneath it. You will want to do this on all servers that has the DFSR role installed and is a member to any replication
groups. You can use the command line command "rmdir", but it fails to delete files/folders that are longer than 256 characters. This is why the 7-zip file manager is a better option to delete the DFSR folder under System Volume Information. However,
there are instances where 7-zip is unable to delete a file or folder. If you run in that scenario, use the rmdir command in an elevated command prompt. Essentially, a combination of these two will eventually clear out everything you need to clear out.
Turn DFSR services back on. This will begin the process of recreating the DFSR hash and virtual tree that you had just deleted.
Recreate the replication group that you want.
On the replication groups that you did not delete, you may get the warning: "The DFS Replication service initialized the replicated folder at local path <path> and is waiting to perform initial
replication. The replicated folder will remain in this state until it has received replicated data, directly or indirectly, from the designated primary member."
If you do, what you need to do is run the command line to set one of the DFSR servers as the primary server for that replication group, and then once set - this
is important - you will have to go in the DFS Management GUI, click on the replication group with the associated warning, select the connections tab, and then right click the the sending member that
you just made as primary and choose "Replicate now..." This will initialize the replication and you will have to do this just that once for it to replicate here on out. You will need to do choose the "Replicate now..." option for each receiving
member that the sending member/primary member server is attached to in that replication group.
Wait about 5-10 minutes and run the dfsrdiag backlog command on each replicationgroup and see if a backlog for replication/sync gets created. Run this command each 5 to 10 minutes to see if the backlog file count value decreases. If it does, it's syncing/replicating.
Don't forget that when testing replication, you cannot create test files via the local path and see if it replicates. You must create it in the DFS Namespace (\domain\folder\share) to see if replication works. Otherwise
you get false negatives and you think replication is still broken. Just an FYI.

2K8 DFSR Replication not working

We moved from 2003 servers to 2008 servers a few months ago, recently we noticed that replication between server1 & server2 is not working, as the initial copy from the primary to the secondary semed ok, but nothing has replicated since. When you run
the health diagnostics in DFS it appears to indicate no issue and all is ok, but nothing is actually replicating from 1 to 2.
when i run dfsrsdiag backlog on either server says there's nothing in backlog. I have a feeling it might have never worked since the initail copy, but found another utility which shows me the below, what does this mean? replciation should be one way server1
to server2
UPDATE:
Dfsradmin Membership List /RGname:Rep_group_namef/attr:MemName,RFName,IsPrimary
Both servers show No to Primary, is this absolutely required? as other servsr with DFS shares have this option of no for all mebers but they are replicating OK

Hi,
If initial replicaiton is finished, it is common that there is no primary server.
Here are the steps to clear database and redo the initial replication. You could first test the step 8 only to see if it could help. If not then try the clear database steps.
1.       Stop and ALSO disable the DFSR service on <ServerA> server (don't just simply stop it)
2.       In Windows Explorer open the specific drive
3.       Right click on the "System Volume Information" directory and select Properties\Security
Note: You might need to select the option for "Show hidden files, folders or drives" and also uncheck "Hide protected operating system files" in the folders view options to be able to even see the "System Volume Information" directory.
4.       Grant your user account that you're logged in with (if a member of Administrators group this will also suffice) "Full Control" to the "System Volume Information" directory.
Note: You may get an error on setting security on some files - this is expected.
5.       Open an elevated/Administrative command prompt. Switch to the "<drive letter>:\System Volume Information" directory
6.       Type the command "rmdir DFSR /s"
7.       Enable and re-start the DFSR service on <ServerA> server
8.       We will then set the <ServerA> server as the Primary member with dfsradmin.exe utility –
Dfsradmin Membership Set /RGName:<RG Name> /RFName:<RF Name> /MemName:<Member Name> /IsPrimary:True
Note: Files will be replicated from ServerA to all other targets. So if there is any newer file on other target servers, backup before starting replication.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Product Revenue Bookings and Backlog Dashboard does not display any data

Product Revenue Bookings and Backlog Dashboard does not display any data even though the load completed successfully.
They are able to see just the parameters.
Not sure if the upgrade of the database from 9.2.0.6 to 10.2.0.3 is a factor.
What can I check?
Is there some table to verify that the data exists for display in the Product Revenue Bookings and Backlog Dashboard?
Screenshot is at:
https://gtcr.oracle.com/gtcr-dir/gtcr_5637/6415786.993/Product_Revenue_Bookings_Backlog_Dashboard.doc
Support suggested to create a new request set and run the initial load with load all summaries option; but there was no change in the Product Revenue Bookings and Backlog Dashboard.
Any ideas?

hi
We have faced the similar problem after the upgrade to 10G
What we did was
Ran the initial load of time dimension, Item setup request set, and the request set of all the dash board in the clear and initial load mode..
we were able to get the data once the clear and load is completed successfully
Regards
Ramesh Kumar S

Exchange 2010 SP2 RU2 - Indexing backlog reached a critical limit of 48 hours or the number of items in the retry queue is greater than 10000 for one or more databases

We have been getting intermittent SCOM alarms for our Exchange 2010 MBX server citing "Indexing backlog reached a critical limit of 48 hours or the number of items in the retry queue is greater than 10000 for one or more databases"
I see events in EventViewer that SCOM is triggering on, but not whats generating the events or how else to test for them.
    get-eventlog -computername SERVERNAME -logname "Application" -after "03/14/2013" | ?{$_.eventid -eq "5604"} | select MachineName,EventID,EntryType,Message | ft -autosize
One MS Forum post online says it is a bug in RU4, unclear if it may also be a bug in RU2 (our installed version).
    http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/9dcb3011-9327-4935-9479-62b38a6ddd87
    "I was looking for the same error and found this.. it basically says that this is a bug in RU4 and RU4-v2...and it needs to be removed."
tests using troubleshooting scripts find no issues with search indexer,
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>.\Troubleshoot-CI.ps1
    Get-EventLog : No matches found
    At C:\Program Files\Microsoft\Exchange Server\V14\scripts\CITSLibrary.ps1:622 char:40
    + $msftesqlCrashes = get-eventlog <<<< -computername $Server -after $StartTime -logname "Application" -source $msftesqlServiceName | where {$_.eventId
    -eq $msftesqlCrashEventId}
        + CategoryInfo : ObjectNotFound: (:) [Get-EventLog], ArgumentException
        + FullyQualifiedErrorId : GetEventLogNoEntriesFound,Microsoft.PowerShell.Commands.GetEventLogCommand
    Name IsDeadLocked CatalogStatusArray
    SERVERNAME False {DATABASENAME\SERVERNAME, DATABASENAME\S...
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>
and tests against searches on each DB themselves show no issues and respond typically within 3 seconds.
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\scripts>Test-ExchangeSearch | ft Server, Database, ServerGuid, ResultFound, SearchTimeInSeconds, Error -AutoSize
    Server Database ServerGuid ResultFound SearchTimeInSeconds Error
    SERVERNAME DATABASENAME b16e3461-257c-40dd-a9ad-99a5f41a927e True 2.937
I also tried to check the Performance Viewer for the MSExchange Search Indexer and MXExchange Search Indices but am unsure which of the many metrics would indicate this issue.
We have had no reports of search issues from our users and have been unable to duplicate any impairment in our testing.
Does anyone else have any suggestions for tests to check or steps to take on this alert? Is it simply a false alarm or a timeout of other sorts during testing? We have 80 DAGs on this server (as well as all our servers, some of which have also reported the
same alert) and the Test-ExchangeSearch command times out before completely testing all DAGs.

Hi IAMChrisL,
Any updates?
Frank Wang
TechNet Community Support

What is your theory on what happened with ASUS Transformer Prime and BB?

This is my theory:
First preorder batch 11/22:
BB opened up for preorders based on expected date of anticipated 12/9 ship date. The buyers at BB that orders from vendors did not buy any preorder stock from ASUS in Champagne on first order. I gotta bleive that the reason that the Champagne prime is not shipping from BB is a "buyer" error. They filled their first allotment of preorders. That is why BB shiped out grey from the first wave of preorders. Other vendors got both- why did BB only get grey? The buyers always think they know what we want or will order and only ordered grey in the request to ASUS. They got caught with their pants down when Amazon cancelled the orders on 12/2 and EVERYONE affected jumped on BB.com and ordered the champagne which was available as the next wave.
Amazon fallout 12/2:
Best buy opened up another set of preorder allotment - 2nd wave, and got hit hard real fast with preorders that they were not prepared for, or had stock for.
ASUS is filling initial preorder requests from the resellers in the order that the resellers requested too. BB was offering that in the next wave of preorders, but they probably took too many orders at once, and they put in another order to ASUS around the 12/9 delay ship date and ASUS was not taking them at that time (delays due to Wifi reported) .
ASUS 12/9 wifi report delay in shiping:
ASUS was cought in a delay with reports of wifi range problems and either stopped taking orders, or recallled/replaced shipment with others. Once ASUS took orders again from the reseller they are shipping daily based on the preorder backlog. Asus is responsible for the delay in accepting orders from vendors, and BB had a buyer error, by either waiting too long to put in the first wave of orders, or not ordering enough, and now they are in the back of the vendor reseller line waiting on ASUS to get to them.
12/19:
The date of irst ship came and BB shipped all it ordered from first wave and could not get anymore from ASUS in the second wave to cover the Amazon fallout system overload. They were left in the back of the line of all other vendors becuse no reseller could get a second next wave fulfillment until all others got their first waves fulfilled. The 12/9 delay kept next waves from being fulfilled, and that is why inventory is trickling into the other resellers and BB can only get a few more at a time. BB ordered champagne on a next wave delay.
The thing that bugs me in to no end is how is a person that ordered grey on 11/28 at BB still on backorder, but a 12/05 grey order has shipped and delivered?? This is not ASUS fault, That is poor business operations on BB.
That is my "perfect storm" theory- what do you think? What is your theory?

That is pretty close to what I think happened.
It does seem pretty clear that Best Buy never initially ordered and Champagne Primes. I have combed through the threads at this site and others and haven’t seen one person receive a Champagne Prime from BB. Meanwhile people who bought from other resellers like New Egg and Amazon have received Champagne Primes.
The mismanagement of shipping out orders chronologically has to be maddening for the people who ordered the Grey Primes. I do feel for these people that ordered the same exact product before others who now have their Prime, but will still don’t have their items.
The communication from Best Buy had been terrible. Screwing up the orders in the 2 examples are somewhat forgivable to me, but the miscommunication and what seems to be deceitfulness that Best Buy has exhibited is not. They just seem not to care about the customer any more. From my experience, prior to the release I was lead to believe my order would be ready to ship on 12/18. Then it went on backorder with no real reason why. Two (12/18 and 12/22) of three calls to customer service reps indicated that my Champagne Prime would still arrive by today (12/23), with the other call rep (12/20) saying she basically had no when my item would be in. Then yesterday afternoon a post from a customer care rep on these boards confirming that I am basically hosed because I choose BB to fulfill my Prime preorder.

Here's what you do activate the iPhone if you had a BlackBerry

I had luck activating my phone after a 25-hour wait!! Finally.
Doomay, thank you for posting this number.
Ok, this is what I did.
Called 1 877 800 3701
Spoke to a representative. She was very helpful. Tried everything and eventually realized that the problem lies in my existing BlackBerry data plan that stubbornly refuses to get replaced with the apple data plan. So what she did, is left everything the way it is, and activated the phone without activating the data plan. That's it. I got confirmation email in seconds while I was still on the phone with her. The Phone started working seconds later. Sure, I probably have no email functionality just yet, but this will be resolved on Monday when the customer care center opens -- 1800 331 0500. At least now the phone is "unlocked", everything works and i already got a backlog of sms messages from yesterday and today. Hooray!!
If you call that number, ask for Penny Wells.
That's all folks!

This was helpful, thanks.

I have now used Reflow for 2 client prototypes and here is what I have found.

First, I can see Reflow being an incredible prototyping tool if Adobe steps up and makes it a useful tool for production and not just another creative program to help designers build for the web. That's what Muse is for.
So here is my wish list.
Reflow needs to be able to have more control over the DOM elements. By that I mean, we should be able to have a layer based approach (similar to what you can see in Macaw) to move elements around from "box" to "box" (also, can't we just call them "divs"). Nesting is crucial. Also, what's up with all the IDs in the published files? We should be able to name and create classes for these elements before it publishes. Also, support the basic HTML tags for users to control.
On that note, shared elements should have one style sheet instead of a style sheet for each page.
Also, elements should be able to be saved to a library for use on multiple pages. It is a nightmare now if you create an element on a page that needs to also be placed on other pages. You have to recreate it on each page as of now.
Support for common CSS frameworks would be an amazing idea...just sayin.
As for type...Edge fonts and Typekit are great but we all know that there are many other font libraries out there such as Google fonts. Also, being able to use your own @font-face should be an option.
I think the overall goal would be able to use the files produced as a starting point for production code. As it stands right now, the code that is produced will require more time to format properly than it would be to build from scratch.
I know Reflow is not meant to be a Dreamweaver or Brackets, but it could really help set the stage for development in those programs. It can improve the workflow of web development vs. just being a "cool new app". It has real potential and I hope it gets the love that it deserves.

Control over DOM: Yup we're working on exposing this even more. You may or may not have noticed the elements panel already in Reflow. You can find it here:
Are you looking for more than that? We're looking at ways to expose the elements panel in a better way, that should be coming soon.
As for stye sheets all being in one, we're debating this. Since we don't know everything you want to do page-to-page, we're holding off making this leap until we can begin cleaning up what CSS we already give you. (see last answer)
Common library elements: yup, we want this too. It's on our backlog.
Frameworks: yup again, on our backlog. Are there frameworks you would prefer? We don't wanna play favorites unnecessarily. We don't know how it might be prioritized, since we've got lots of features to get to.
Additional fonts: yup for this one too, we have it on our backlog to tackle. As a note, most google fonts are available in the Adobe Web Fonts.
Output: We're actively working on improving the CSS output from Reflow. We cannot promise perfect production quality, but the issues you raise are all ones we're eager to minimize.
Thanks for the thorough feedback, we love these kinds of posts!
- Seth

DFSR fails with partner that no longer exists.

Short version: one of our domain controllers has DFSR Event 5008 errors, regarding a domain controller that has be demoted and removed from our domain. It is the only domain controller, of five, to have this error, the other four domain controllers are clean.
Longer version: we are in the process of upgrading Active Directory from 2008 to 2012 R2, at this time we have three 2012 R2 servers and one of those three owns all the FSMO roles, it also happens to be the one that we see the DFSR Event 5008 errors on.
In addition to those three 2012 R2 servers, we have two 2008 servers remaining, until we clear up the remaining errors.
DFS Replication, on DC-2012-1, says that it failed to communicate to partner DC-2008-2; however, that is to be expected since DC-2008-2 is no longer a domain controller, nor a member of the domain. When we go into DFS Management and look at the sysvol replication,
we do not see DC-2008-2 referenced anywhere, nor have I found a reference to it anywhere else that I have looked.
What can we do remove the reference to the partner, to eliminate these errors?

Hi Nate,
Have you tried to create a new replication group?
More information for you:
Create a replication group
http://technet.microsoft.com/en-us/library/cc756710(v=WS.10).aspx
DFS Step-by-Step Guide for Windows Server 2008
http://technet.microsoft.com/en-us/library/cc732863(v=WS.10).aspx
Best Regards,
Amy

What is backlog in DFSR?

Similar Messages

Maybe you are looking for