1nisbackup(1M) System Administration Commands nisbackup(1M)
2
6 nisbackup - backup NIS+ directories
7
9 nisbackup [-v] backup-dir directory...
10 nisbackup [-v] -a backup-dir
13
16 nisbackup backs up a NIS+ directory object on a NIS+ master server.
17 Updates to the NIS+ database will be temporarily disabled while nis‐
18 backup is running. The backup-dir is a UNIX directory that must exist
19 prior to running nisbackup. The nisbackup command can be used to backup
20 an individual NIS+ directory object or all ( -a) of the NIS+ directory
21 objects served by a master server. The NIS+ directory objects being
22 backed up will be placed into subdirectories under the backup-dir
23 directory. These subdirectories are named according to the NIS+ direc‐
24 tory object they contain. nisbackup operates on individual NIS+ direc‐
25 tory objects (for example, org_dir.wiz.com). This allows an administra‐
26 tor to selectively backup specific directories.
27 The rpc.nisd(1M) process must be running on the master server with a
30 stable NIS+ database for nisbackup to complete. nisbackup will not
31 attempt to correct any corruption in the NIS+ database, so it is impor‐
32 tant that backups be done regularly as part of the NIS+ administration.
33 The first synopsis is used to backup a single NIS+ directory object or
36 a list of NIS+ directory objects. The objects can be partially quali‐
37 fied or fully qualified. The machine on which the command is executing
38 must be the master for the NIS+ directory objects specified.
39 The second synopsis will backup all of the NIS+ directory objects that
42 are served by this master. The -a option is the recommended method of
43 backing up a master server, since it will backup all NIS+ directory
44 objects that are served by this master. If this server is a master
45 server for more than one domain, the backup will include NIS+ directo‐
46 ries that belong to all of the domains served. Individual NIS+ direc‐
47 tory objects can be selected for restoring from a backup-dir created
48 with the -a option. See nisrestore(1M).
49 The -a option only includes directory objects for which this server is
52 the master. It is possible, but not recommended, to configure a master
53 server as a replica for other domains. The objects belonging to those
54 replicated domains will not be backed up with the -a option. The backup
55 of replicated objects must be run on the master server for those
56 objects.
57 Do not use the same backup-dir to backup different master servers. Each
60 master server must have its own backup-dir.
61 nisbackup will set the rpc.nisd(1M) to read only mode, which will dis‐
64 able updates to the NIS+ database. This is neccessary to ensure the
65 consistency of the backup. For this reason, nisbackup should not be run
66 while large numbers of updates are being applied to the NIS+ database.
67 Update utilities such as nisaddent(1M) should not be run simultaneously
68 with nisbackup.
69
71 -a Creates a backup of all NIS+ directory objects for which this
72 server is a master.
73 -v Verbose option. Additional output will be produced and sent to
76 syslog(3C) upon execution of the command (see syslog.conf(4)).
77
80 backup-dir The directory into which the subdirectories containing
81 the backed up objects are placed. This must be created
82 prior to running nisbackup.
83 directory The NIS+ directory object(s) being backed up.
86
89 Example 1 Backup of the org_dir NIS+ directory object of the domain
90 foo.com on a master server to a directory named /backup
91 To backup the org_dir NIS+ directory object of the domain foo.com on a
94 master server to a directory named /backup:
95 master_server# nisbackup /backup org_dir.foo.com.
98 Example 2 Backup of the entire NIS+ domain foo.com to a directory named
102 /backup
103 To backup the entire NIS+ domain foo.com to a directory named /backup:
106 master_server# nisbackup /backup foo.com. \
109 org_dir.foo.com. groups_dir.foo.com. \
110 ctx_dir.foo.com.
111 Example 3 Backup of an entire NIS+ database to a backup directory named
115 /backup
116 To backup an entire NIS+ database to a backup directory named /backup:
119 master_server# nisbackup -a /backup
122
126 0 Successful completion.
127 1 An error occurred.
130
133 /backup-dir/backup_list
134 This ascii file contains a list of all the objects contained in
136 this backup-dir directory.
137 /backup-dir/directory-object
140 A subdirectory that is created in the backup-dir that contains the
142 NIS+ directory-object backup.
143 /backup-dir/directory-object/data
146 A subdirectory that contains the data files that are part of the
148 NIS+ directory-object backup.
149 /backup-dir/directory-object/last.upd
152 This data file contains timestamp information about the directory-
154 object.
155 /backup-dir/directory-object/data.dict
158 A NIS+ data dictionary for all of the objects contained in the NIS+
160 directory-object backup.
161
164 See attributes(5) for descriptions of the following attributes:
165 ┌─────────────────────────────┬─────────────────────────────┐
170 │ ATTRIBUTE TYPE │ ATTRIBUTE VALUE │
171 ├─────────────────────────────┼─────────────────────────────┤
172 │Availability │SUNWnisu │
173 └─────────────────────────────┴─────────────────────────────┘
174
176 NIS+[22m(1), nisdefaults(1), nisrm(1), nisrestore(1M), rpc.nisd(1M), sys‐
177 log(3C), nisfiles(4), syslog.conf(4), attributes(5)
178
180 NIS+ might not be supported in future releases of the Solaris operating
181 system. Tools to aid the migration from NIS+ to LDAP are available in
182 the current Solaris release. For more information, visit
183 http://www.sun.com/directory/nisplus/transition.html.
184SunOS 5.11 12 Dec 2001 nisbackup(1M)