Edit: Interesting HTML tags on it, and it seems I need my own server to set up pictures. Well, good thing we have a static IP! Just need to get the DNS records moved...
I'm writing this more to clear my head than anything else. If it helps someone, great. We have measured significant 'release impact' when deploying one of our core applications. The main problem is initialization/warmup of the appPool. We've tried the built-in methods, but for whatever reason we are always stuck with ~25s of dead time while the first request warms things up (we assume it's warming things up, not really sure what is happening). After that 25s wait things are very snappy and fast, so how do we prevent all of our web servers from going into 25s of dead time with production traffic inbound? Starting point - why do this? We care about our customers, and we want to help drive our business forward with as much quality/safety/speed as possible. Because we want to drive our business forward, we are pushing to do more and more deploys ( currently we do a daily deploy, but want to see 5x that ) ( if you have to ask why we want 5x, read this ).
This warning isn't documented that well on the googles, so here's some google fodder: You are trying to set up replication for a DFS folder (no existing replication) Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2) You have no issues getting replication configured You see the DFSR folders get created on the other end, but nothing stages Finally you get EventID 4312: The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved. Additional Information: Folder: F:\Users$\user.name\Desktop\Random Folder Name\ Replicated Folder Root: F:\Users$ File ID: {00000000-0000-0000-0000-000000000000}-v0 Replicated Folder Name: Users Replicated Folder ID: 33F0449D-5E67-4DA1-99A
An issue I've come across many times now is how to properly present a purchase request to your manager/his boss. There are occasional managers who will just take your word for it, but some (hopefully most) will question the need for it. As a technical person, I find it really easy to get caught up in what something can do rather than why we need it in the first place. Case in point. An upgrade was required for some KVM servers - more RAM required - and I put through the request for purchase to my superior. He sent it over to the director, who immediately shot back an email requiring a really nice reason to approve it. After some futzing about via email (I was out of the office that day), it became clear that he was fine approving it, but we needed to make the case as to WHY he should approve it. Frankly we needed to prove it to ourselves first, but he was technically-competent and was not just going to stamp everything 'a-ok'. There was a clear reason to me and my c
Comments
Post a Comment