Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Linux Administration Best Practices

You're reading from   Linux Administration Best Practices Practical solutions to approaching the design and management of Linux systems

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781800568792
Length 404 pages
Edition 1st Edition
Tools
Arrow right icon
Author (1):
Arrow left icon
Scott Alan Miller Scott Alan Miller
Author Profile Icon Scott Alan Miller
Scott Alan Miller
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Preface 1. Section 1: Understanding the Role of Linux System Administrator
2. Chapter 1: What Is the Role of a System Administrator? FREE CHAPTER 3. Chapter 2: Choosing Your Distribution and Release Model 4. Section 2: Best Practices for Linux Technologies
5. Chapter 3: System Storage Best Practices 6. Chapter 4: Designing System Deployment Architectures 7. Chapter 5: Patch Management Strategies 8. Chapter 6: Databases 9. Section 3: Approaches to Effective System Administration
10. Chapter 7: Documentation, Monitoring, and Logging Techniques 11. Chapter 8: Improving Administration Maturation with Automation through Scripting and DevOps 12. Chapter 9: Backup and Disaster Recovery Approaches 13. Chapter 10: User and Access Management Strategies 14. Chapter 11: Troubleshooting 15. Other Books You May Enjoy

On premises, hosted, and hybrid hosting

Now that we have talked about so many aspects of the underlying components that are used to provide us with a platform on which to deploy an operating system, we can finally talk about where those systems should exist!

This is, at least, the simplest of all our topics. Physical location is easy to explain, even if many businesses get confused about it in practice. Conceptually we really only think about two locations for a workload and that is as being either on premises or off premises. This can be a little convoluted, though, as companies own multiple locations so what is off premises to one site might be see as on premises to another. But we generally consider on premises to be all of a company's owned sites and off premises being any sites that are operated by a third party. Because of this we generally refer to off premises physicality as being hosted, as physical systems are being hosted on our behalf. However, there are reasons...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image