Müller Docs Documentation Versão 0.0.1

Müller Docs Documentation Versão 0.0.1 Müller Fernandes da Silva 27 September, 2015 Conteúdo 1 Fontes 3 1.1 Table of Contents.............................................3 1.2 Indices and tables............................................ 231 1.3 Conteúdo Pendente............................................ 231 Bibliografia 235 i ii Müller Docs Documentation, Versão 0.0.1 Bem vindo à minha base de documentação. Na busca por um método de anotar os conheci- mentos necessários para minhas atividades do dia-a-dia me deparei com o trabalho feito pelo ‘Ops School<(http://www.opsschool.org/en/latest/>‘_ e comecei a alterá-lo para satisfazer minhas necessidades. Conteúdo 1 Müller Docs Documentation, Versão 0.0.1 2 Conteúdo CAPÍTULO 1 Fontes • Fork de Ops School • Este projeto é escrito em reStructuredText • Hospedado em Read the Docs • Compilado pelo sistema de documentação Sphinx no Travis CI 1.1 Table of Contents 1.1.1 Tecnologia da informação Active Directory 101 What is Active Directory? Active Directory is a Directory Service created by Microsoft. It is included with most Windows Server operating systems. Almost all Active Directory installations actually include several separate but related components; although the term “Active Directory” technically refers only to the directory service, in general use it refers to the entire constellation of parts. What is Active Directory used for? Active Directory is primarily used to store directory objects (like users and groups) and their attributes and relati- onships to one another. These objects are most commonly used to control access to various resources; for instance, an Active Directory might contain a group which grants its members permission to log into a certain server, or to print to a specific printer, or even to perform administrative tasks on the directory itself. Active Directory also provides a useful configuration management service called Group Policy, which can be used to manage computers which connect to the domain in order to install packages, configure software, and much more. You mention “separate components”; what is Active Directory composed of? Most Active Directory installations have a few distinct parts which all work together: •a directory database which stores the actual directory information 3 Müller Docs Documentation, Versão 0.0.1 •a Kerberos key distribution center which helps manage user passwords and other security resources •a DNS server, which maps IP addresses to hostnames and back •a DHCP server, which grants dynamic IP addresses to hosts as they join the network • one or more Global Catalogs, which cache parts of the directory database and help speed up some common queries Also, Active Directory is designed in such a way that it can be run on multiple computers at the same time, which coordinate between themselves to ensure that their data is always consistent; this process is called “replication”. What specific services does Active Directory provide? Group Policy DNS Kerberos Key Distribution Center DHCP Best Practices for managing an Active Directory installation Cleaning up Unneeded Objects Making Backups Replication Health Active Directory 201 Detailed Breakdown of Active Directory Components/Services NTDS, the database Kerberos KDC DNS DHCP Global Catalog Advanced Active Directory Maintenance FSMO Roles 4 Capítulo 1. Fontes Müller Docs Documentation, Versão 0.0.1 Application Components 201 Message Brokers RabbitMQ Apache ActiveMQ Memory Caches Memcached Redis Specialized Caches Varnish nginx+memcached Architecture 101 How to make good architecture decisions Patterns and anti-patterns Introduction to availability Introduction to scalability Architecture 201 Service Oriented Architectures Fault tolerance, fault protection, masking, dependability fundamentals Fail open, fail closed Perspective: node, network, cluster, application Caching Concerns Static assets Data 1.1. Table of Contents 5 Müller Docs Documentation, Versão 0.0.1 Eviction and replacement policies and evaluation Approaches (TTL, purge-on-write, no-purge versioning, constantly churning cache versus contained, working set sizing) Crash only Synchronous vs. Asynchronous Business continuity vs. Disaster Recovery Designing for Scalability: Horizontal, Vertical Simplicity Performance Tiered architectures MTTR > MTBF http://www.kitchensoap.com/2010/11/07/mttr-mtbf-for-most-types-of-f/ Backups Backups are a critical part of preserving an organization’s information. RAID, clustering and other real-time copies of data do not help when the data is deleted, the buildings containing these live sources are compromised by weather, human intervention, or facilities failures. Could the organization survive if part or all of its information were lost? Remember, RAID is not a backup solution. RAID protects against the loss of individual drives, but if data gets corrupted or deleted, RAID will replicate that corruption across all RAID stripes. Making backups on separate media is the best way to protect yourself against both “hard” and “soft” data loss. Designing a backup policy Operations needs to work with organizational leaders to develop a backup policy that protects the organization’s information while balancing cost and other factors important to the organization. Operations engineers need to be able to understand organizational needs in order to evaluate backup solutions, stra- tegies, and current best practices. They must then translate this knowledge into recommended solutions which management can use to make a sound business decision. The ability to assemble a cohesive plan, including a cost-benefit analysis of available options, can help the organization make the right decision for the business on an appropriate backup policy. 6 Capítulo 1. Fontes Müller Docs Documentation, Versão 0.0.1 Deciding what to backup Consider cost, time, and staff resources when deciding what to backup. Does it make sense to backup every client hard drive when a system can be re-imaged over the network? Does the configuration management solution maintain client customizations? If so, operations may not need to backup the operating system on clients and can focus on user data. Ideally, the goal is not to restore clients starting at the operating system level. Where is organizational data stored? Is data local on each client or does the organization use a file server? Do users actually store their data on the file server? Some users have had bad experiences using the network and move all of their data locally, or refuse to store anything on the server in case the network becomes unavailable. If users travel frequently, they may store all of their data on a laptop. This poses additional backup challenges when laptops are not always on the organization’s network to talk to the backup server. Some organizations perform incremental backups on all clients to protect against users who decide where best to store their data. What about data stored on servers? Do all servers need to be backed up? What is the available backup window and will the organization’s network push enough data to a backup server to fit within that window? How will taking the backup affect each application’s performance? Ultimately, deciding what to backup is a business decision. What information is critical to the business and how much is the organization willing to invest to protect that information? There may also be laws requiring the organization to retain certain data that will influence this decision. When not to backup Por fazer restoring? what not to backup, regulations on same, how to store them (PCI) Retention periods Is there a risk to having a long retention period? Por fazer The idea of such a risk may not be immediately clear to a beginning ops person. What is the cost to retain backups for a 30-days, 6-months, or 1 year? Is there a business requirement for keeping backups for a specific length of time? Are there laws for maintaining electronic records for a specific period of time? If the organization is required to adhere to Freedom of Information Act (FOIA) law, sometimes long retention periods are a detriment. FOIA requests can cover any kind of data including individual emails on a specific subject. If the information doesn’t benefit the organization, then it might be a liability due to labor-intensive searches through ancient backups. Por fazer How does FOIA affect what information an organization needs to have available? Assume the reader is a civilian and doesn’t know how FOIA affects an organization. Offsite backups How sensitive is the organization’s information? Storing a copy of the organization’s crown jewels in an insecure location can expose the organization to loss, unauthorized modification, or theft of intellectual property. Is the organization required to encrypt offsite data? Does the organization have a second geographically distributed location that could house an off-site backup of the organization’s information? 1.1. Table of Contents 7 Müller Docs Documentation, Versão 0.0.1 Designing a Backup System Backup type and frequency What kind of information does the organization rely on to do business? Do hourly changes need to be captured or can the organization survive with backups every 12-hours or once per day? • Full backups • Incremental backups • Replication • Snapshots • Bare-metal restore vs data only • online/offline Por fazer media – should someone address the state of backup media? Some places are still doing tape. What about orgs who rely on standalone consumer-grade disks for client backups (e.g. Time Machine)? Risks,

Load more