It seems like
obvious advice, but administrators often fail to take it. They think that a little configuration job won??™t
cause much trouble until they??™re picking up the pieces later. You should already have a good backup
program in place because your server contains valuable data. If you aren??™t backing up your server
regularly (regularly is defined as at least once a day and probably more often than that), then you??™re
already setting yourself up for a major surprise at the worst possible moment. Don??™t cause that
moment to occur by performing a task on a server that hasn??™t been backed up for the last month.
Try to perform any configuration tasks as soon as possible after the backup completes so that a
disaster will cause as little loss as possible. In fact, if you can perform the tasks before anyone starts
working with the server, you??™ll likely have better results.
Perform User-Specific Changes during Downtime
Some changes you make to a user account affect the user immediately; other changes wait until the
next time the user logs into the system. Think about this issue for a moment and you??™ll figure out
that this scenario can create instabilities.
Pages:
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379