Linux System Administration Recipes A Problem-Solution Approach

More documents

Recommendations

Info

CHAPTER 4 ■ TAKING BACKUPS AND MANAGING DATA• How much data do you need to store? See recipe 4-1 for a script to calculate yourcurrent total disk size and actual current usage.• How often do your files change? Recipe 4-2 has a script to establish this.• What is the purpose of your backups? Do you want a long-term archive of filehistory or just a backup so that if someone accidentally types rm -rf . in theirhome directory, you can restore their files for them?• Related to the previous point, how long do you want to archive your data for, andhow long do you want to give users to realize that they’ve accidentally deletedtheir Important Directory? Often this is going to be dictated either by companypolicy or by finances.• How important is it that you are able to restore fast? You can usually choose, whenbacking up, either to do a full backup dump or to do a diff backup. The formertakes up more space and takes longer to do but is quicker to restore from. Chancesare you want somewhere between the two.Once you’ve considered all this information, you can start pricing various options. For example, ifyou want a full backup weekly and then a diff backup nightly, use the information from the first twobullets to calculate how much space you want (and how much space you might want if all your disks fillup) for the full backup and then for each day’s incremental change. That’s your weekly datarequirement. Based on that, how many weeks can you afford tapes for before you have to rotate? Whatabout adding an extra archive copy per month?You also need to consider how long each backup will take—how fast does data move over your localnetwork, and how fast can your preferred backup media be written to? (Remember that tapes are fasterthan disk.) As a rule, you probably don’t want backups running during the day if you can avoid it, so youneed to think about how much you can back up every night.Finally, if you’re pricing a new backup solution, think about the future. You should allow for at leasta 100 percent increase in the quantity of data you need to back up over the life of the system, andpreferably more. Many systems now are modular, so you can buy more drives or libraries to extend yoursetup in the future for less than the cost of a whole new system.■ Note Your backups are only as good as your last restore check. Confirm that restores are working OK (andtherefore that the backups are working OK) weekly by running a test restore from your backup software.4-1. Calculating Your Network’s Total Disk Size andCurrent UsageTo establish what backup policy you need, one of the things to find out is the total potential size of yourdisks and what your current usage is. The following script can calculate this for all the machines in yournetwork:96Download at WoweBook.Com
CHAPTER 4 ■ TAKING BACKUPS AND MANAGING DATA01 #!/usr/bin/perl -w02 # Script to tally up total disk space available and used in local network03 # JK 25.03.20090405 use strict;06 use Net::LDAPS;0708 die "Usage: dfscript\n" unless @ARGV == 0;0910 my ($search) = @ARGV;11 my $server = "ldaps://ldap.example.com";12 my $cert = "/etc/ldap/servercert.pem";13 my $base = "dc=example,dc=com";14 my $total = 0;15 my $used = 0;1617 my $ldap = Net::LDAPS->new( $server,18 verify => 'optional',19 cafile => $cert ) or die $@;20 my $mesg = $ldap->bind;21 my $filter = "(objectClass=ipHost)";22 $mesg = $ldap->search( base => $base,23 filter => $filter,24 attr => ['cn'],25 );26 $mesg->code && die $mesg->error;2728 my @entries = $mesg->sorted('cn');2930 foreach my $entry ( @entries ) {31 my $machine = $entry->get_value( 'cn' );32 if ( $machine ) {33 open my $info, '-|', "ssh $machine 'df'"34 or warn "Can't ssh to $machine";36 while () {37 if ( /^\/dev/ ) {38 my @list = split;39 $total += $list[1];40 $used += $list[2];41 }42 }43 }44 }4546 $mesg = $ldap->unbind;47 print "Total is: $total\nUsed is: $used\n";97Download at WoweBook.Com
Page 2:
Download at WoweBook.Com
Page 5 and 6:
Download at WoweBook.Comiii
Page 7 and 8:
Contents■About the Author .......
Page 9 and 10:
■ CONTENTS3-7. Writing a Nagios P
Page 11 and 12:
■ CONTENTS■Chapter 8: Using the
Page 13 and 14:
■ CONTENTSAbout the Author■Juli
Page 15 and 16:
■ CONTENTSAcknowledgmentsMany tha
Page 17 and 18:
■ CONTENTSIntroductionThis book i
Page 19 and 20:
■ INTRODUCTIONDownloading the Cod
Page 21 and 22:
C H A P T E R 1■ ■ ■Saving Yo
Page 23 and 24:
CHAPTER 1 ■ SAVING YOURSELF EFFOR
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
C H A P T E R 2■ ■ ■Centraliz
Page 43 and 44:
CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66: CHAPTER 2 ■ CENTRALIZING YOUR NET
Page 83 and 84: C H A P T E R 3■ ■ ■Monitorin
Page 85 and 86: CHAPTER 3 ■ MONITORING AND UPDATI
Page 115: C H A P T E R 4■ ■ ■Taking Ba
Page 119 and 120: CHAPTER 4 ■ TAKING BACKUPS AND MA
Page 139 and 140: C H A P T E R 5■ ■ ■Working w
Page 141 and 142: CHAPTER 5 ■ WORKING WITH FILESYST
Page 155 and 156: C H A P T E R 6■ ■ ■Securing
Page 157 and 158: CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 167 and 168:
CHAPTER 6 ■ SECURING YOUR SYSTEMS
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
C H A P T E R 7■ ■ ■Working w
Page 179 and 180:
CHAPTER 7 ■ WORKING WITH APACHEOn
Page 181 and 182:
CHAPTER 7 ■ WORKING WITH APACHEdi
Page 183 and 184:
CHAPTER 7 ■ WORKING WITH APACHE4.
Page 185 and 186:
CHAPTER 7 ■ WORKING WITH APACHE
Page 187 and 188:
CHAPTER 7 ■ WORKING WITH APACHEAl
Page 189 and 190:
CHAPTER 7 ■ WORKING WITH APACHE
Page 191 and 192:
C H A P T E R 8■ ■ ■Making Be
Page 193 and 194:
CHAPTER 8 ■ USING THE COMMAND LIN
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
C H A P T E R 9■ ■ ■Working w
Page 207 and 208:
CHAPTER 9 ■ WORKING WITH TEXT IN
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
C H A P T E R 10■ ■ ■Things G
Page 225 and 226:
CHAPTER 10 ■ THINGS GO IN, THINGS
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
C H A P T E R 11■ ■ ■Tracking
Page 235 and 236:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 237 and 238:
CHAPTER 11 ■ TRACKING DOWN BUGS01
Page 239 and 240:
CHAPTER 11 ■ TRACKING DOWN BUGS
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
CHAPTER 11 ■ TRACKING DOWN BUGSTh
Page 247 and 248:
CHAPTER 11 ■ TRACKING DOWN BUGSAn
Page 249 and 250:
CHAPTER 11 ■ TRACKING DOWN BUGS#
Page 251 and 252:
C H A P T E R 12■ ■ ■Managing
Page 253 and 254:
CHAPTER 12 ■ MANAGING TIME AND PE
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
APPENDIX■ ■ ■Perl TipsSee rec
Page 269 and 270:
APPENDIX ■ PERL TIPS• Date::Par
Page 271 and 272:
APPENDIX ■ PERL TIPSPerl Syntax N
Page 273 and 274:
■ ■ ■Index■Symbols$CDPATH,
Page 275 and 276:
■ INDEXenscript option (printing)
Page 277 and 278:
■ INDEX■NNagiosadding hosts to,
Page 279 and 280:
■ INDEXsyslogcentralized logging
Page 281 and 282:
Download at WoweBook.Com
show all

Linux System Administration Recipes A Problem-Solution Approach

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?