Professional Documents
Culture Documents
Restore The following logs are potentially involved with this error and are enabled by creating the following directories on the according host . Master Server Logging
UNIX:
/usr/openv /Netbackup /logs/bpcd /usr/openv /Netbackup /logs/bprd /usr/openv /Netbackup /logs/bpsched Windows : <Install_Path>\NetBackup\logs\bprd <Install_Path>\NetBackup\logs\bpcd <Install_Path>\NetBackup\logs\bpsched Media Server Logging UNIX: /usr/openv /Netbackup /logs/bpcd /usr/openv /Netbackup /logs/bpbrm /usr/openv /Netbackup /logs/bptm Windows :<Install_Path>\NetBackup\logs\bpcd <Install_Path>\NetBackup\logs\bpbrm <Install_Path>\NetBackup\logs\bptm Client Machine Logging UNIX: /usr/openv /Netbackup/logs/bpcd /usr/openv /Netbackup /logs/bpbkar /usr/openv /Netbackup /logs/tar (restore issues ) Windows :<Install_Path>\NetBackup \logs \bpcd <Install_Path>\NetBackup\logs\bpbkar <Install_Path>\NetBackup\logs\tar
Logs to obtain Client: bpcd, tar Media Server : bpcd, bpbrm , bptm Master Server : bpcd, bprd , bpsched
Status Code: 25 Client backup was not attempted because the backup window closed
Page 1 of 8
Table of Contents
1 NetBackup processes are not responding..........................................................................3 1.1 NetBackup Processes are not running..........................................................................3 1.2 The bpcd process is not listening on the client.............................................................3 2. Server List Issues................................................................................................................5 3. Network Communication issues..........................................................................................6 3.1 Ensuring communication to bpcd.................................................................................6 3.2 Firewall..........................................................................................................................6 3.3 Name Resolution...........................................................................................................7 4. System Resource issues........................................................................................................7 4.1 Minimum System Requirements..................................................................................7 4.2 RAM and CPU..............................................................................................................7 4.3 Drive Fragmentation (Windows)..................................................................................8 5. Links....................................................................................................................................8
Status Code: 25 Client backup was not attempted because the backup window closed
Page 2 of 8
Status Code: 25 Client backup was not attempted because the backup window closed
Page 3 of 8
If a general instability or issue outside of NetBackup has occurred on the NetBackup Master Server, Media Server or Client, then it may be necessary to reboot that machine to regain functionality. In some cases, it may only be necessary to restart the NetBackup Services/daemons. In either case, ensure that no backup jobs or other NetBackup activity is taking place on the host prior to rebooting or restarting services. Restarting the services in Windows: 1. From the desktop, right-click on My Computer and choose Manage. 2. Expand Services and Applications and highlight Services. 3. Locate the NetBackup services. 4. Right-click on each NetBackup service to stop and restart. Restarting the daemons in UNIX: Stopping Daemons:
# /usr/openv/netbackup/bin/goodies/netbackup stop
Starting Daemons:
# /usr/openv/netbackup/bin/goodies/netbackup start
Status Code: 25 Client backup was not attempted because the backup window closed
Page 4 of 8
NetWare and OS/2 Clients The instructions for Netware and OS/2 are nearly the same. Add or change SERVER entries in the Sys\openv\netback\bp.ini file as needed. Windows Clients and Media Servers Ensure proper server list configuration on Windows Clients and Media Servers by doing the following: 1. Open the Backup, Archive, and Restore interface on the machine in question. 2. Select File > Specify NetBackup Machines and Policy Type. 3. Select the Servers tab. 4. Verify that the according Master and Media Server(s) are added to this server list, and that the Master Server is set as current. 5. Click OK after adding any needed servers and then exit Backup, Archive and Restore. Note: If server entries are modified on a NetBackup Master Server, it is necessary to stop and restart NetBackup services/processes. Services/processes do not need to be restarted on a Media Server or Client after updating the server list.
Status Code: 25 Client backup was not attempted because the backup window closed
Page 5 of 8
Successful telnet output example from UNIX: # telnet <server name> bpcd Trying 10.10.100.20... Connected to <server name>. Escape character is '^]'. Hit the Ctrl ] and then type quit to end Unsuccessful telnet output example from UNIX: # telnet <server name> bpcd Trying 10.10.100.20... telnet: Unable to connect to remote host: Connection refused Successful telnet output example from Windows: telnet <server name> bpcd < If successful no displayed messages will be returned > To stop telnet: hold down Ctrl key and press the ] key, then release and type quit to end telnet session. Unsuccessful telnet output example from Windows: Connecting to <server name> . .Could not open a connection to host on port 13782 : Connect failed If a telnet test fails, ensure again that bpcd (The client service on Windows) is running and listening. If so, it may be necessary to analyze the network configuration to determine why the bpcd port (13782) can not be reached. A telnet test can also be used to test the connection to other processes such as bprd (Master) and vnetd.
3.2 Firewall
If a firewall is present in the configuration, it will be necessary to open port ranges for proper communication, or utilize the NetBackup vnetd daemon to lessen the amount of ports being used. See the NetBackup System Administrators Guide for more details on this.
Status Code: 25 Client backup was not attempted because the backup window closed
Page 6 of 8
Using bpclntcmd
bpclntcmd is a useful utility that can be run from any host. It will help determine if name resolution is working properly from NetBackups perspective. Test bpclntcmd between hosts where problems exist. This is often between the Client and Media Server. Windows command location: %install_path%\VERITAS\NetBackup\bin\ UNIX command location: /usr/openv/netbackup/bi n Switches and variations:
bpclntcmd bpclntcmd bpclntcmd bpclntcmd -pn -self -hn <hostname_of_master server, media server, or client> -ip <ip_of_master server, media server, or client>
The goal of these commands is to make sure the hostname is seen the same way after each command with no errors. Below is an explanation of what each switch does: -pn - The client process on the host connects to the Master Server and asks the question "Who am I?". The second line of the output is the result. This is how the client process on the host is being seen by the Master Server. -self - Checks how the local host can be resolved. Ideally, there should be only 1 unique hostname and 1 unique IP address. -hn - Checks the given hostname and returns an IP. -ip - Checks the given IP and returns a hostname. If there is any inconsistency or errors in the results of these commands, it may be necessary to add a local host entry in the operating system for the host to ensure proper name resolution.
Status Code: 25 Client backup was not attempted because the backup window closed
Page 7 of 8
Add more CPU or RAM to the Server in question. Minimize resources being used by other Server applications. Lessen the amount of concurrent backups or other NetBackup Operations.
Unix Additionally, for Unix, VERITAS has suggested minimum kernel parameters for UNIX machines. Review the technote for this in the related documents section in the web page of this technote. As mentioned with Windows, if CPU and RAM resources continue to be low, it may be necessary to do one of the following:
Add more CPU or RAM to the Server in question. Minimize resources being used by other Server applications.
5. Links
Click here to Search for other documents on Status Code 25
Status Code: 25 Client backup was not attempted because the backup window closed
Page 8 of 8