[Veritas-bu] Cold Catalog Backup?

Hi,

We’re running NBU 6.5.1 and have just rebooted everything (just as PM thing – no issues were occurring).

Before boot I canceled all active jobs and waited for unmount.

After boot NBU seemed to start fine.

Activity monitor shows a Catalog backup occurring. Various commands I issue return messages about database server being down but NBEMM is running.

The server system log shows me it successfully mounted the tape for the Catalog backup (SU3221). I then see messages indicating NBDB was stopped.

I’m wondering if this means NBU has taken this opportunity to do a “cold” Catalog backup?

I don’t mind waiting for that to complete but don’t know how to verify it is actually doing something. After the mount the job detail in Activity Monitor doesn’t show any updates (except elapsed time). I’d just like some sort of positive confirmation that it is in fact doing a cold backup and I need to wait.

The system log contained:

Aug 15 10:39:17 atubks01 tldd[4596]: TLD(2) MountTape SU3221 on drive 16, from slot 119

Aug 15 10:39:18 atubks01 tldcd[4643]: returned from mm_authenticate_request, vauth_action=4, VAUTH_DENIED=1, VAUTH_ALLOWED=0

Aug 15 10:39:18 atubks01 tldcd[4643]: tldcd.c.3085, process_request(), received command=1, from peername=atubks01, version 50

Aug 15 10:39:18 atubks01 tldcd[4643]: Processing MOUNT, TLD(2) drive 16, slot 119, barcode SU3221 , vsn SU3221

Aug 15 10:39:18 atubks01 tldcd[8349]: TLD(2) opening robotic path /dev/sctl/c27t3l0

Aug 15 10:39:18 atubks01 tldcd[8349]: inquiry() function processing library HP A5597A 0395:

Aug 15 10:39:19 atubks01 tldcd[8349]: TLD(2) initiating MOVE_MEDIUM from addr 1118 to addr 515

Aug 15 10:39:43 atubks01 tldcd[8349]: TLD(2) closing/unlocking robotic path

Aug 15 10:39:43 atubks01 tldcd[4643]: inquiry() function processing library HP A5597A 0395:

Aug 15 10:39:43 atubks01 tldcd[4643]: tldcd.c.2699, newfd = INVALID_SOCKET, newfd=-1, timersig=1, error=4, EINTR=4, selectret=-1

Aug 15 10:39:47 atubks01 tldd[8347]: Calling the drive_mount_notify script, DriveName=Ultrium16

Aug 15 10:39:47 atubks01 tldd[8347]: Mount callout returned normal status, DriveName = Ultrium16, Status = 0

Aug 15 10:39:48 atubks01 tldd[4596]: DecodeMount: TLD(2) drive 16, Actual status: STATUS_SUCCESS

Aug 15 10:39:49 atubks01 ltid[4545]: LTID - received ROBOT MESSAGE, Type=54, LongParam=0, Param1=15, Param2=0

Aug 15 10:39:58 atubks01 SQLAnywhere(nb_atubks01): Starting database "utility_db" (utility_db) at Fri Aug 15 2008 10:39

Aug 15 10:39:58 atubks01 SQLAnywhere(nb_atubks01): Database "utility_db" (utility_db) started at Fri Aug 15 2008 10:39

Aug 15 10:39:58 atubks01 SQLAnywhere(nb_atubks01): Starting checkpoint of "NBDB" (NBDB.db) at Fri Aug 15 2008 10:39

Aug 15 10:39:58 atubks01 SQLAnywhere(nb_atubks01): Finished checkpoint of "NBDB" (NBDB.db) at Fri Aug 15 2008 10:39

Aug 15 10:39:58 atubks01 SQLAnywhere(nb_atubks01): Database "NBDB" (NBDB.db) stopped at Fri Aug 15 2008 10:39

Aug 15 10:39:58 atubks01 SQLAnywhere(nb_atubks01): Database "utility_db" (utility_db) stopped at Fri Aug 15 2008 10:39

Aug 15 10:40:28 atubks01 sshd[8590]: Accepted keyboard-interactive/pam for root from 10.0.22.10 port 1142 ssh2

Aug 15 10:42:57 atubks01 xntpd[4367]: synchronized to 10.0.20.124, stratum=1

----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu