0 Basic Learning Cloud computing and Big Data DBA cluster Architect "enterprise-level operation and maintenance technology and practice Project January 21, 2015 Thursday"

1Building the right system management ideas7*24 system Operation {24 hours a day, 7 days a week, uninterrupted system monitoring 8 per day:xx~ -: 00 times per day for user Access 2:xx~6: 00 for maintainable or interruptible time stability monitoring, profile backup, database structure backup can be completed during user access time system, application, platform migration operation must be completed within the maintenance time (for example: Service off-line) online database of any offline operation should be within the maintenance time Complete (for example: Database migration)} operation and maintenance engineer requirements {Guaranteed service to meet the standards, to ensure that the online service is stable and secure continuously improve the reliability and robustness of application services, performance optimization and ensure security gradually improve the site at all levels of monitoring (software, hardware, operating status, etc.), to avoid monitoring dead ends, and    Real-time visibility into the operation of applications through innovative thinking to solve operational efficiency issues, and continuously optimize the automation scripts, the use of new technologies to constantly solve new problems.    Accumulate and precipitate operations and maintenance knowledge, and constantly improve the documentation to avoid repetitive error.    Planning and execution are required, there are planned and specific implementation steps, and the plan is to find ways to achieve the goal, without making excuses. Be able to refine daily monitoring work, design and develop operations tools, generate visual charts with existing systems or scripts} How to avoid errors in the work {back up after backup all, back up files before you destroy the system take the time stamp and the machine name or IP address the best offsite backup backup before packing fragmented text    Permissions (including owner and owning group) also to back up don't forget to link the file to write down the operation steps, before executing to confirm the target side and the source side open a window try to make different host windows to render different color overlay file before think twice the MV will always be safer than RM Leaving an operational record is your responsibility to the team and the assurance that others will continue your work} operational security Considerations {Protect yourself and protect users as important as interpreting confidentiality agreements do not take the customer's data away from the company you can see all the data, but out of professional ethics you can't see, even if you look at it, forget about    A day's operation is recorded and reported carefully is always more conducive to your growth than carelessness. Daily documents to be submitted {daily newspaper weekly Report action plan pending reports project operations and Results Report General issues Summary Report Unable to resolve problem summary report} daily time Management {    When you need to focus, turn off your QQ and Weibo, machine to vibrate or fly to classify tasks, important and urgent to do beforehand, and then important things to check the mail every hour instead of every minute to make their own schedule, preferably a GTD-type pre-operation classification business, universal operation as far as possible automation Recommended Reading--"Time management-to system administrator"} excellent system administrator's ability {1Self-recognition System Management task capability2implementation of best practice thinking ability 0 standardized Standardization0 centralization Centralization0 extensibility Scalability0 Provisioni NG0 Automation Automation3. Avoid "one-time (OneOff)" Trap capability4. Using the System management tools ability} Daily system administration work {1. System Startup and shutdown20 File system integrity and free disk space required for daily maintenance 0 Many profiles 0 Software installation 0 user authentication 0 security 0 System Monitoring 0 Deployment new Department System 0 integration of old systems} standardization {1. Plan 0 System installation and upgrade 0 software installation and upgrade when installing any software, you should follow the following sequence:1) first install test or test machine on the test machine or the application of the source code or binary mode program2Create a server system that can be installed on your server for third-party software to support the installation package structure (class Redhat system uses the RPM method, the Debian-like system uses the DEB method, the BSD-like system uses the TAR method)3Test your packaged application software installation package on a test machine or test machine4) Deploy the package to the system that needs it5) Verify its health on the deployment server6if necessary, you can restore the previous system structure and configuration2. Create a standard document • File system list • Third-party software list note the version information • configuration file list • What do you think all important things} configuration file list {W.H.O.program When time why why modify what modified content} Document specification {requires Scenario action steps questions and Answers system monitoring deployment system consolidation old system} }

0 Basic Learning Cloud computing and Big Data DBA cluster Architect "enterprise-level operation and maintenance technology and practice Project January 21, 2015 Thursday"