Errata

Errata for Backup & Recovery

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version	Location	Description	Submitted by	Date submitted
Printed	Page 106 "Use GNU tar if You Can" box, last bullet, last line	"... tar -create -verbose -file." should read "... tar --create --verbose --file." (i.e. consecutive dashes, not single dashes).	Anonymous
Printed	Page 115 3rd paragraph, last sentence	", authenticating using rsh, or ssh if the RSYNC_RSH variable had been set to ssh:" should read ", authenticating using ssh, or rsh if the RSYNC_RSH variable had been set to rsh:" (i.e. swap rsh with ssh, and ssh with rsh)	Anonymous
Printed	Page 117 2nd paragraph	Contrary to paragraph #2, the first two rsync commands on this page do not do the same thing. The outcome of the first command is correctly described in paragraph 1, but the second command results in a different destination tree (/backup/home/home).	Anonymous
Printed	Page 124 last three commands	In the last three command examples (create backup tapes on remote hosts), the arguments of dd should be 'of', not 'if', because dd is already reading input from the stdin of the remote ssh shell via the pipe.	francesco cicolani	Oct 28, 2009
Printed	Page 328 last command	"# gzip -dc /backups/hda.dd.gz\|dd of=/dev/had" should be "# gzip -dc /backups/hda.dd.gz\|dd of=/dev/hda"	Bruce Epper	Jul 07, 2013
Printed	Page 335 uppermost, first set of commands - last line	the last tar command lacks the '--exclude /proc' option.	francesco cicolani	Oct 28, 2009
Printed	Page 457 last set of commands	All 3 control files need to be copied here since the previous copy overwrote the original control02.ctl file. So the following command needs to be added to the set: $ cp /b/control2.ctl.sav /b/control2.ctl Also, the last command itself is specifying the wrong location for the destination. It should be: $ cp /b/control2.ctl.sav /c/control3.ctl The Windows commands at the top of page 458 also need the additional copy command added: C:\ copy D:\CONTROL02.SAV D:\CONTROL02.CTL	Bruce Epper	Jul 10, 2013
Printed	Page 629 last paragraph	in the PDF version, i can read : "On a Unix/Linux machine, psef would show something like the following: Need a process list from a PostgreSQL machine" On my database server, i've : $ ps -ef pgsql 1126 1098 0 Feb 01 ? 2:04 /usr/pkg/bin/postgres pgsql 1098 1 0 Feb 01 ? 68:03 /usr/pkg/bin/postgres pgsql 1125 1098 0 Feb 01 ? 24:55 /usr/pkg/bin/postgres pgsql 1127 1098 0 Feb 01 ? 601:49 /usr/pkg/bin/postgres pgsql 4126 1098 0 12:06:14 ? 0:00 /usr/pkg/bin/postgres pgsql 4071 1098 0 12:06:00 ? 0:00 /usr/pkg/bin/postgres pgsql 4107 1098 0 12:06:10 ? 0:00 /usr/pkg/bin/postgres pgsql 3870 1098 0 12:05:49 ? 0:00 /usr/pkg/bin/postgres pgsql 4236 1098 0 12:06:50 ? 0:00 /usr/pkg/bin/postgres pgsql 21531 1098 0 02:17:56 ? 0:00 /usr/pkg/bin/postgres pgsql 4088 1098 0 12:06:04 ? 0:00 /usr/pkg/bin/postgres pgsql 4121 1098 0 12:06:13 ? 0:00 /usr/pkg/bin/postgres pgsql 22704 1098 0 11:10:21 ? 0:00 /usr/pkg/bin/postgres	Anonymous
Printed	Page 648 Second command in "Backing up InnoDB tables" section	The command mysqldump --database=mysql --lock-all-tables --flush-logs --master-data=2 > system.sql does not follow the syntax mysqldump requires. It should read either mysqldump --databases mysql --lock-all-tables --flush-logs --master-data=2 > system.sql or mysqldump --lock-all-tables --flush-logs --master-data=2 mysql > system.sql	Anonymous	Sep 18, 2008
Printed	Page 648 second paragraph	In the sample code, the invocation for mysqladmin is incorrect. Instead of $ mysqladmin --flush-logs it should be $ mysqladmin flush-logs	JimCheetham	Mar 25, 2010