Status 2 running Full SQL backup

[HankHill]

10/4/2012 2:17:16 PM - Info nbjm(pid=10448) starting backup job (jobid=158786) for client LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL, policy LON-SUN-SQL-01_NEW_FULL, schedule FULL  
10/4/2012 2:17:16 PM - Info nbjm(pid=10448) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=158786, request id:{C8280B3E-CCE7-464B-A1B1-8FBCE9550592})  
10/4/2012 2:17:16 PM - requesting resource LON-SUN
10/4/2012 2:17:16 PM - requesting resource us-bak-01.shl.prod.NBU_CLIENT.MAXJOBS.LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL
10/4/2012 2:17:16 PM - requesting resource us-bak-01.shl.prod.NBU_POLICY.MAXJOBS.LON-SUN-SQL-01_NEW_FULL
10/4/2012 2:17:16 PM - granted resource us-bak-01.shl.prod.NBU_CLIENT.MAXJOBS.LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL
10/4/2012 2:17:16 PM - granted resource us-bak-01.shl.prod.NBU_POLICY.MAXJOBS.LON-SUN-SQL-01_NEW_FULL
10/4/2012 2:17:16 PM - granted resource LON-SUN
10/4/2012 2:17:16 PM - estimated 0 Kbytes needed
10/4/2012 2:17:16 PM - Info nbjm(pid=10448) started backup job for client LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL, policy LON-SUN-SQL-01_NEW_FULL, schedule FULL on storage unit LON-SUN
10/4/2012 2:17:19 PM - started process bpbrm (3672)
10/4/2012 2:17:21 PM - Info bpbrm(pid=3672) LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL is the host to backup data from     
10/4/2012 2:17:22 PM - Info bpbrm(pid=3672) reading file list from client        
10/4/2012 2:17:22 PM - connecting
10/4/2012 2:17:25 PM - Info bpbrm(pid=3672) starting bphdb on client         
10/4/2012 2:17:25 PM - connected; connect time: 00:00:03
10/4/2012 2:17:26 PM - Info bphdb(pid=424) Backup started           
10/4/2012 2:17:27 PM - Error bpbrm(pid=3672) from client LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL: ERR - command failed: none of the requested files were backed up (2)
10/4/2012 2:17:27 PM - Error bpbrm(pid=3672) from client LON-SUN-SQL-01.GROUP.SHLROOT.LOCAL: ERR - bphdb exit status = 2: none of the requested files were backed up
10/4/2012 2:17:30 PM - end writing
none of the requested files were backed up(2)

LON-SUN-SQL-01 is the virtual SQLHost.  Physical nodes are LON-SUN-SQL-02a and 02b.  Looked through some other forum posts that were similar, but nothing seemed to help.

[Marianne]

Please ensure that dbclient log folder exists on the active node. (You may as well create the folder on both nodes so that logs will be created wherever the cluster is online.)

Rename dbclient log after the next failure to dbclient.txt and post log as well as backup script as File attachments.

[HankHill]

Interestingly, about 5 minutes after the status 2, a status 2001 showed up for the policy.  Discovered that when they were setting up replication, they knocked out the tape drives for the volume pool.  Now that those have been re-added, I'm waiting for the volume pool to show up again in Device Manager so I can see if that is what caused the failure.