HP Model 755/125cL System Configuration Repository User's Reference: HP-UX/HP - Page 31

Change Management, node1, time node2

Page 31 highlights

SCR Overview Additional Uses of SCR Change Management SCR can complement your system change management process by keeping good records of changes and alerting you to unplanned changes. • You can configure SCR to automatically take periodic snapshots. • You can take snapshots whenever you want them. • You can tailor reports to compare the current system state to previous states. • You can generate records of all reports. Use the scrupdate, scrconfig, and scrhist commands to perform change management, as follows: 1. Complete the initial configuration steps described in this chapter. 2. Take an initial snapshot of the systems as they are, to provide a base for detecting future changes: # scrupdate -a 3. Set SCR to collect data weekly or as often as you wish: # scrconfig -i lw 4. Have SCR email a system history report to you. (Remember that SCR will not store a snapshot if the node has not changed since the last snapshot.) # scrhist 5. When you receive the email, order a scrdiff report on the system nodes that showed differences, to see what they are. # scrdiff node1:time node2:time Chapter 2 31

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84

Chapter 2
31
SCR Overview
Additional Uses of SCR
Change Management
SCR can complement your system change management process by
keeping good records of changes and alerting you to unplanned
changes.
You can configure SCR to automatically take periodic snapshots.
You can take snapshots whenever you want them.
You can tailor reports to compare the current system state to
previous states.
You can generate records of all reports.
Use the
scrupdate
,
scrconfig
, and
scrhist
commands to perform
change management, as follows:
1.
Complete the initial configuration steps described in this chapter.
2. Take an initial snapshot of the systems as they are, to provide a base
for detecting future changes:
#
scrupdate -a
3.
Set SCR to collect data weekly or as often as you wish:
#
scrconfig -i lw
4.
Have SCR email a system history report to you. (Remember that
SCR will not store a snapshot if the node has not changed since the
last snapshot.)
#
scrhist
5.
When you receive the email, order a scrdiff report on the system
nodes that showed differences, to see what they are.
#
scrdiff
node1
:
time node2
:
time