Hi All,
i alreday backup SQL database..all the child job result is 0 , but only one result is 1 (the requested operation was partially successful).
1-How can i fix this error
2-Let say, i just ignore this error code, can i do a SQL restoration with successful?
Environment= NetBackup 7.6.0.4, Win Server 2008/2012
14/7/2015 12:43:40 PM - Info nbjm(pid=9864) starting backup job (jobid=342560) for client JJHMGISAV1, policy ucust-sql-full_DCDB_GLIN_PDCL, schedule Full_Backup
14/7/2015 12:43:40 PM - Info nbjm(pid=9864) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=342560, request id:{374DD706-BC9A-4042-A91B-50F98C568C72})
14/7/2015 12:43:40 PM - requesting resource majsmrma2-OST-stu
14/7/2015 12:43:40 PM - requesting resource majsmrfa1.NBU_CLIENT.MAXJOBS.JJHMGISAV1
14/7/2015 12:43:40 PM - requesting resource majsmrfa1.NBU_POLICY.MAXJOBS.ucust-sql-full_DCDB_GLIN_PDCL
14/7/2015 12:43:40 PM - granted resource majsmrfa1.NBU_CLIENT.MAXJOBS.JJHMGISAV1
14/7/2015 12:43:40 PM - granted resource majsmrfa1.NBU_POLICY.MAXJOBS.ucust-sql-full_DCDB_GLIN_PDCL
14/7/2015 12:43:40 PM - granted resource majsmrma2-OST-stu
14/7/2015 12:43:41 PM - estimated 0 Kbytes needed
14/7/2015 12:43:41 PM - Info nbjm(pid=9864) started backup (backupid=JJHMGISAV1_1436849020) job for client JJHMGISAV1, policy ucust-sql-full_DCDB_GLIN_PDCL, schedule Full_Backup on storage unit majsmrma2-OST-stu
14/7/2015 12:43:43 PM - started process bpbrm (12720)
14/7/2015 12:43:45 PM - Info bpbrm(pid=12720) JJHMGISAV1 is the host to backup data from
14/7/2015 12:43:45 PM - Info bpbrm(pid=12720) reading file list for client
14/7/2015 12:43:55 PM - Info bpbrm(pid=12720) starting bphdb on client
14/7/2015 12:43:56 PM - connecting
14/7/2015 12:43:56 PM - Info bphdb(pid=14276) Backup started
14/7/2015 12:44:06 PM - connected; connect time: 0:00:10
14/7/2015 12:44:15 PM - Info dbclient(pid=380) INF - BACKUP STARTED USING
14/7/2015 12:44:15 PM - Info dbclient(pid=380) Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
14/7/2015 12:44:15 PM - Info dbclient(pid=380) May 14 2014 18:34:29
14/7/2015 12:44:15 PM - Info dbclient(pid=380) Copyright (c) Microsoft Corporation
14/7/2015 12:44:15 PM - Info dbclient(pid=380) Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
14/7/2015 12:44:15 PM - Info dbclient(pid=380) Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch, Op# = 1
14/7/2015 12:44:16 PM - Info dbclient(pid=380) INF - Using backup image JJHMGIFA1.MSSQL7.JJHMGISAV1\DCDB_GLIN_PDCL.db.master.~.7.001of001.20150714124414..C
14/7/2015 12:44:16 PM - Info dbclient(pid=380) INF - backup database "master" to VIRTUAL_DEVICE='VNBU0-380-13728-1436849055' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
14/7/2015 12:44:16 PM - Info dbclient(pid=380) INF - Number of stripes: 1, Number of buffers per stripe 2.
14/7/2015 12:44:17 PM - Info dbclient(pid=380) INF - Created VDI object for SQL Server instance <DCDB_GLIN_PDCL>. Connection timeout is <300> seconds.
14/7/2015 12:45:07 PM - Info dbclient(pid=380) INF - Thread has been closed for stripe #0
14/7/2015 12:45:13 PM - Info dbclient(pid=380) INF - OPERATION #1 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 59(0) seconds
14/7/2015 12:45:18 PM - Info dbclient(pid=380) INF - BACKUP STARTED USING
14/7/2015 12:45:18 PM - Info dbclient(pid=380) Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
14/7/2015 12:45:18 PM - Info dbclient(pid=380) May 14 2014 18:34:29
14/7/2015 12:45:18 PM - Info dbclient(pid=380) Copyright (c) Microsoft Corporation
14/7/2015 12:45:18 PM - Info dbclient(pid=380) Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
14/7/2015 12:45:18 PM - Info dbclient(pid=380) Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch, Op# = 2
14/7/2015 12:45:18 PM - Info dbclient(pid=380) INF - Using backup image JJHMGIFA1.MSSQL7.JJHMGISAV1\DCDB_GLIN_PDCL.db.model.~.7.001of001.20150714124516..C
14/7/2015 12:45:18 PM - Info dbclient(pid=380) INF - backup database "model" to VIRTUAL_DEVICE='VNBU0-380-9588-1436849118' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
14/7/2015 12:45:19 PM - Info dbclient(pid=380) INF - Number of stripes: 1, Number of buffers per stripe 2.
14/7/2015 12:45:19 PM - Info dbclient(pid=380) INF - Created VDI object for SQL Server instance <DCDB_GLIN_PDCL>. Connection timeout is <300> seconds.
14/7/2015 12:46:05 PM - Info dbclient(pid=380) INF - Thread has been closed for stripe #0
14/7/2015 12:46:10 PM - Info dbclient(pid=380) INF - OPERATION #2 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 53(1) seconds
14/7/2015 12:46:14 PM - Info dbclient(pid=380) INF - BACKUP STARTED USING
14/7/2015 12:46:14 PM - Info dbclient(pid=380) Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
14/7/2015 12:46:14 PM - Info dbclient(pid=380) May 14 2014 18:34:29
14/7/2015 12:46:14 PM - Info dbclient(pid=380) Copyright (c) Microsoft Corporation
14/7/2015 12:46:14 PM - Info dbclient(pid=380) Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
14/7/2015 12:46:14 PM - Info dbclient(pid=380) Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch, Op# = 3
14/7/2015 12:46:15 PM - Info dbclient(pid=380) INF - Using backup image JJHMGIFA1.MSSQL7.JJHMGISAV1\DCDB_GLIN_PDCL.db.msdb.~.7.001of001.20150714124612..C
14/7/2015 12:46:15 PM - Info dbclient(pid=380) INF - backup database "msdb" to VIRTUAL_DEVICE='VNBU0-380-6556-1436849174' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
14/7/2015 12:46:15 PM - Info dbclient(pid=380) INF - Number of stripes: 1, Number of buffers per stripe 2.
14/7/2015 12:46:16 PM - Info dbclient(pid=380) INF - Created VDI object for SQL Server instance <DCDB_GLIN_PDCL>. Connection timeout is <300> seconds.
14/7/2015 12:47:01 PM - Info dbclient(pid=380) INF - Thread has been closed for stripe #0
14/7/2015 12:47:06 PM - Info dbclient(pid=380) INF - OPERATION #3 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 54(2) seconds
14/7/2015 12:47:08 PM - Info dbclient(pid=380) INF - Results of executing <C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulldbbackup.bch>:
14/7/2015 12:47:09 PM - Info dbclient(pid=380) <3> operations succeeded. <0> operations failed.
14/7/2015 12:48:09 PM - Info dbclient(pid=9760) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full backup can be performed on the master database.
14/7/2015 12:48:10 PM - Info dbclient(pid=9760) INF - OPERATION #1 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulllogbackup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 40(40) seconds.
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) INF - BACKUP STARTED USING
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) Microsoft SQL Server 2012 - 11.0.5058.0 (X64)
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) May 14 2014 18:34:29
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) Copyright (c) Microsoft Corporation
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: )
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulllogbackup.bch, Op# = 2
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) INF - Using backup image JJHMGIFA1.MSSQL7.JJHMGISAV1\DCDB_GLIN_PDCL.trx.model.~.7.001of001.20150714124812..C
14/7/2015 12:48:14 PM - Info dbclient(pid=9760) INF - backup log "model" to VIRTUAL_DEVICE='VNBU0-9760-10944-1436849294' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
14/7/2015 12:48:15 PM - Info dbclient(pid=9760) INF - Number of stripes: 1, Number of buffers per stripe 2.
14/7/2015 12:48:15 PM - Info dbclient(pid=9760) INF - Created VDI object for SQL Server instance <DCDB_GLIN_PDCL>. Connection timeout is <300> seconds.
14/7/2015 12:49:00 PM - Info dbclient(pid=9760) INF - Thread has been closed for stripe #0
14/7/2015 12:49:04 PM - Info dbclient(pid=9760) INF - OPERATION #2 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulllogbackup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 52(0) seconds
14/7/2015 12:49:08 PM - Info dbclient(pid=9760) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full or incremental database backup can be performed on database <msdb> because it uses the simple recovery model or has 'truncate log on checkpoint' set.
14/7/2015 12:49:08 PM - Info dbclient(pid=9760) INF - OPERATION #3 of batch C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulllogbackup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2(2) seconds.
14/7/2015 12:49:11 PM - Info dbclient(pid=9760) INF - Results of executing <C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\jjhgifav-glin_pdcl-fulllogbackup.bch>:
14/7/2015 12:49:11 PM - Info dbclient(pid=9760) <1> operations succeeded. <2> operations failed.
14/7/2015 12:49:11 PM - Info dbclient(pid=9760) INF - The following object(s) were not backed up successfully.
14/7/2015 12:49:12 PM - Info dbclient(pid=9760) INF - master
14/7/2015 12:49:12 PM - Info dbclient(pid=9760) INF - msdb
14/7/2015 12:49:21 PM - Error bpbrm(pid=12720) from client JJHMGISAV1: ERR - command failed: the requested operation was partially successful (1)
14/7/2015 12:49:21 PM - Error bpbrm(pid=12720) from client JJHMGISAV1: ERR - bphdb exit status = 1: the requested operation was partially successful
14/7/2015 12:49:22 PM - Info bpbrm(pid=12720) validating image for client JJHMGISAV1
14/7/2015 12:49:29 PM - Error bpbrm(pid=12720) cannot send mail to
14/7/2015 12:49:30 PM - Info bphdb(pid=14276) done. status: 1: the requested operation was partially successful
14/7/2015 12:49:41 PM - end writing
the requested operation was partially successful(1)
The job was successfully completed, but some files may have been
busy or inaccessible. See the problems report or the client's logs for more details.
