Backup & Recovery Unconfirmed Errata

Errata

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

Version	Location	Description	Submitted By
Printed	Page 66 1st paragraph, definition of "Incremental"	The definition for "Incremental" is incorrect; it should end as follows: "... and mark them as backed up". (i.e. omit the "do not"	Anonymous
Printed	Page 90 1st paragraph, opening sentence	"The v option is used ..." should read "The s option is used ...", consistent with the paragraph heading.	Anonymous
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
Printed	Page 335 uppermost, first set of commands - last line	the last tar command lacks the '--exclude /proc' option.	francesco cicolani
Printed	Page 492 first paragraph, last sentence	... native bcp files scan only be used... should this read "native bcp files can only be used.."	Steve Baucum
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