To try anything new, always use a test system that is configured
like your real server. You??™ll appreciate the safety net that such an arrangement provides the first
time you have to reformat the test machine drive due to unforeseen complications.
Write absolutely everything down as you test a new process. Don??™t use a file on the server to store
this information??”it may not be there in a few moments. If you don??™t have a secondary machine you
can use, then write down your procedure on paper. Verify everything you write down to make sure
you wrote it correctly. Execute a command only after you verify that you have written it down correctly
and used help to ensure you have formatted the command correctly. If something does go
horribly wrong, having a written record can make it possible for someone to help you fix the problem.
Even if you can??™t get help, at least you know not to try that command line syntax again. In some
cases, you have to be willing to fail in order to make progress. Of course, the safety net of your test
system makes such failure nonfatal (but still aggravating).
Even after you create a complete procedure that works in every way, test it several more times
on the test system before you begin using it in a production environment.
Pages:
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376