Re: Snapshot option on NBU

niks_blr · ‎09-01-2008

Hello ,

Master server is S10 , NBU 6.x.x.x Clients are windows

When i start the backup it is showing me the following message

08/25/2008 22:21:12 - begin Snapshot: Delete Snapshot
08/25/2008 22:21:17 - end writing
Operation Status: 0
08/25/2008 22:21:18 - end Snapshot: Delete Snapshot; elapsed time 0:00:06
Operation Status: 41
08/25/2008 22:21:18 - end Parent Job; elapsed time 2:05:26
network connection timed out (41)

I dont want the snapshot option , so how to disable the snapshot options

and i am getting n/w connection time out error for two machine, physically both the machies are in n/w and all the ports are open clients are windows 200,both can connect to master server.

pl. give the suggetion.

thanks in advance.

sdo · ‎09-01-2008

Your issue is not with snapshots. Status 41 can be caused by many factors.

Try following the suggested resolutions from:

$ bperror -S 41 -r

niks_blr · ‎09-01-2008

Thanks for updated.

I got following errors from the same master server, where there are six clients out of six from two client backup doesnt happen.

on the both the client n/w is working fine.

08/28/2008 17:19:30 SVR - skipping database backup -- no successful
                    regular or user backups
08/28/2008 17:21:10 - bprd TERMINATED
08/28/2008 17:21:13 - bpdbm TERMINATED
08/28/2008 17:21:13 - TERMINATED bpjobd
08/28/2008 17:21:46 - INITIATING bpdbm: NetBackup 6.0 2008012304 on
                     IDIRSTRUCT=2 (VERBOSE = 0)
08/28/2008 17:21:47 - INITIATING bpjobd: NetBackup 6.0 on SVR
08/28/2008 17:21:53 - INITIATING bprd: NetBackup 6.0 2008012304 on

08/28/2008 17:22:06 - [3] backup of client JPSASMDS, policy test1, is
                    suspended: exceeded configured number of tries for a
                    schedule
08/28/2008 17:22:06 - [3] backup of client APP2, policy
                    APP2, is suspended: exceeded configured number of
                    tries for a schedule
08/28/2008 17:22:06 - [3] backup of client APP1, policy
                   APP1, is suspended: exceeded configured number of
                    tries for a schedule
08/28/2008 17:22:06 SVR - [3] backup of client JPIDES, policy JPIDES, is
                    suspended: exceeded configured number of tries for a
                    schedule
08/28/2008 17:30:33 SVR SAPP2 client APP2 handling path
                    h:\backup180808
08/28/2008 17:30:33 DVR - running session_start_notify
08/28/2008 17:30:33 SVR - started backup job (jobid=451) for client
                    APP2, policy SAPP2-new, schedule Full
08/28/2008 17:30:33 SVR APP2 starting backup job (jobid=451)
08/28/2008 17:39:47 SVR - bprd TERMINATED
08/28/2008 17:39:51 SVR - bpdbm TERMINATED
08/28/2008 17:39:51 SVR - TERMINATED bpjobd
08/28/2008 17:40:49 SVR - bprd TERMINATED
08/28/2008 17:40:49 SVR - bprd TERMINATED
08/28/2008 17:41:25 SVR - INITIATING bpdbm: NetBackup 6.0 2008012304 on
                    SVR IDIRSTRUCT=2 (VERBOSE = 0)
08/28/2008 17:41:26 SVR - INITIATING bpjobd: NetBackup 6.0 on SVR
08/28/2008 17:41:31 SVR - INITIATING bprd: NetBackup 6.0 2008012304 on
                    SVR
08/28/2008 17:41:45 SVR - [3] backup of client JPSASMDS, policy test1, is
                    suspended: exceeded configured number of tries for a
                    schedule
08/28/2008 17:41:45 APP2 [3] backup of client JPSASAPP2, policy
                   APP2-new, is suspended: exceeded configured number of
                    tries for a schedule
08/28/2008 17:41:45 SVR - [3] backup of client APP2, policy
                    PP2, is suspended: exceeded configured number of
                    tries for a schedule
08/28/2008 17:41:45 SVR - [3] backup of client APP1, policy
                    APP1, is suspended: exceeded configured number of
                    tries for a schedule
08/28/2008 17:41:45 SVR - [3] backup of client JPIDES, policy JPIDES, is
                    suspended: exceeded configured number of tries for a
                    schedule

Can you throw some light on this issue?

David_Kerrivan · ‎09-03-2008

If you haven't done so already, set the logging on your client side to as high as you can (verbose 3 or higher) Make sure you have space for the logs on the client - the TroubleShooting Guide has a full list of the logs you'll need for clients and the master/media server.

You haven't indicated what sort of client this is (Windows, Linux, other UNIX). If you have access to it, or have a case open with support, get them to provide you the Apparent Networks SAS tool and run tests between the client and the master - it's a great way to really verify you have a solid network.

You might also want to narrow your focus to using bperror -problems -hoursago <integer_hours> -U to clear out the chatter that is shown. If you have 6.x use http://support.veritas.com/docs/278422 and if you have 5.x use http://support.veritas.com/docs/277695

David_Kerrivan · ‎09-03-2008

Sorry, missed the first line of your original post. Need more coffee!

VOX

Snapshot option on NBU