• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home
  • Public Forums
  • Application Monitoring & UEM
  • AppMon & UEM Open Q&A
avatar image
Question by James M. · May 30, 2012 at 11:03 PM · production

Fault Tolerant Deployment Strategies

We are moving towards having dynaTrace in a central position in our production operations activities, from monitoring to alerting, etc. To make this work, we need to move towards a model where there is no single point of failure anymore, something that is difficult to do with dynaTrace 4.1.

One area I'm focused on is the dynaTrace server itself and the persistant data stores (Oracle and file-based data), looking at how to handle catastrophic  The database is being replicated, within about 10-30 seconds after the data gets updated in the primary database. The dynatrace file system itself is where my questions are.

We have identified the following directories that need near-continuous replication. The other trees can be replicated with less frequency

dynatrace-4.1.0/logs

dynatrace-4.1.0/server/cache

dynatrace-4.1.0/server/sessions/stored data

dynatrace-4.1.0/collector/instances

??? - missing anything?

The question: what is dynaTrace engineering's recommendation for file-based replication? We anticipate having around 2-4Tb of data when done. We currently run on SAN, so are looking at preferentially using SRDF (block-level replication). However, I don't know if the dynatrace storage model is going to be compatible with block-level replication, since  a record could span multiple blocks. The other approach is something like rsync. Are there any guidelines/recommendations you have around keeping two datacenters in sync, so in the event of failure of one data center we can spin up the secondary dt server and pick up very close to where we left off (i.e. within a minute or two)?

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

2 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Günter S. · Jun 12, 2012 at 03:13 PM

Hi James,

the following directories are crucial for the collector/server to work.

Server:

If you are running the server normally:

dynatrace-4.1.0/dtserver.ini (= startup configuration of the server)

dynatrace-4.1.0/server/cache (= runtime data, you only need to copy the .imap file, the rest is optional)

dynatrace-4.1.0/server/conf (= the whole configuration, including license, system profiles, dashboards, permission..)

If you are running the server instanced you need those directories for every instance:

dynatrace-4.1.0/server/instances/<instance name>/cache

dynatrace-4.1.0/server/instances/<instance name>/conf

Collector:

If you are running the collector(s) normally:

dynatrace-4.1.0/collector.ini (= startup configuration of the collector)

dynatrace-4.1.0/collector/cache (= runtime data, same as server, only .imap are important, rest is optional)

dynatrace-4.1.0/collector/conf (= configuration data)

If you are running instanced collector(s) you need these directories for every collector:

dynatrace-4.1.0/collector/instances/<instance name>/cache

dynatrace-4.1.0/collector/instances/<instance name>/conf

You also need to backup your "storage" directory, the one where you are writting the PurePaths too. As for the question of block-level replication, I don't have any experience with that and I can't really help you with an answer here.

We do have another customer who's running a hot-standby server, but he's not replicating data between the two servers. In case of a failure the 2nd environment takes over and the data is written to a different storage and a different database till the problem is solved. So he'll not have all captured information in 1 dtserver, which seems to be your goal.

regards,

Günter

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · May 31, 2012 at 01:48 PM

Hi James

I've forwarded this internally to get a solid answer for you. stay tuned

Andi

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

1 Person is following this question.

avatar image

Related Questions

IIS Worker Process State "Terminated Unexpectedly" vs "Not Running"

Tibco Support

Instrument two or more service from same agent

Confirmed events

How to explain Out-of-memory incidents of a JVM agents if no sign of high use of memory is noticed?

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A