cancel
Showing results for 
Search instead for 
Did you mean: 

Backing up a NetWare6.5 server

Richard_Yates
Level 2
Hi

We have a Solaris 2.9 server(BACCHUS) running NetBackup 5.1.0 GA Enterprise server on it, and it's been backing up various unix/windows based servers fine for ages, but we are trying to get it to backup a Netware 6.5 server (CROM) now too.

We have installed the NetBackup Netware client onto the Netware6.5 server, configued all the target service agent details, pointed it to BACCHUS, then using a Windows 2000 admin workstation, setup a backup job in the NetBackup Management Console. The backup job is set to point to the server CROM, using a standard policy and we've tried either backing up a specific volume or used the standard ALL_LOCAL_DRIVES, but with no luck.

The job submits fine, but it always eventually comes back with the following info with Activity Monitor

7/8/2005 3:28:39 PM - connecting
7/8/2005 3:28:40 PM - connected
7/8/2005 3:28:41 PM - mounting 000363
7/8/2005 3:29:19 PM - mounted
7/8/2005 3:29:19 PM - positioning 000363 1
7/8/2005 3:29:22 PM - positioned
7/8/2005 3:29:22 PM - begin writing
7/8/2005 3:29:42 PM - end writing
none of the files in the file list exist(71)

Now in the log file \\crom\sys\VERITAS\NBUCLT\NetBack\logs\bpcd\070805.LOG. It states the following (just a section posted)

15:28:37: <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = /SYS:
15:28:37: <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = ALL_LOCAL_DRIVES
15:28:37: <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = /SYS
15:28:37: <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = / SYS
15:29:31: <4> Open File Backup: INF - OFB Status: SYNCHRONIZED.
15:29:31: <2> tar_base::V_vTarMsgM: TRV - target does not exist: SYS: (No such file or directory)
15:29:31: <2> tar_base::V_vTarMsgM: TRV - target does not exist: (No such file or directory)
15:29:31: <2> tar_base::V_vTarMsgM: TRV - target does not exist: SYS (No such file or directory)
15:29:31: <2> tar_base::V_vTarMsgM: TRV - target does not exist: SYS (No such file or directory)
15:29:31: <2> tar_base::backup_finish: TAR - backup: 0 files
15:29:31: <2> tar_base::backup_finish: TAR - backup: file data: 0 bytes
15:29:31: <2> tar_base::backup_finish: TAR - backup: image data: 1024 bytes
15:29:31: <2> tar_base::backup_finish: TAR - backup: elapsed time: 1 secs 1024 bps
15:29:31: <2> tar_base::V_vTarMsgM: INF - EXIT STATUS 71: none of the files in the file list exist


Now there you can see i'm attempting to backup ALL_LOCAL_DRIVES, SYS, SYS: and SYS:\ (just because i thought i might be using a wrong format), all of them fail.

Any ideas??? For info the servers have each others details in their host files, can ping each other fine. TCP ports 13782 and 13720 are listening on BACCHUS(master server), and just 13782 on CROM(NetWare server running NW client). The NetWare 6.5 server has SP3 on it, and i've updated the TSA and SMDR to the latest from tsa5up18.exe


Now one other thing we tried was to put in the files/dirs we wanted backing up in the following format /CROM/SYS, and this seemed to get past the "none of the files in the file list exist(71)" message, now we just get "the requested operation was partially successful(1)", and in the log file it states the following (again only a certain chunk)

15:59:31: <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
15:59:31: <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = /CROM/SYS:\zenworks\zfs-startup.log
16:00:25: <4> Open File Backup: INF - OFB Status: SYNCHRONIZED.
16:00:25: <2> tar_base::V_vTarMsgM: ERR - unable to scan first dataset: (SMS: FFFDFFD1: (TSAFS.NLM 6.51.0 302) There are no more data sets to be scanned.)
16:00:25: <2> sms_xbackup::tar_backuplogs: DAT - ERROR LOG (0 bytes):
16:00:25: <2> sms_xbackup::tar_backuplogs: DAT - SKIPPED DATA SETS (0 bytes):
16:00:25: <2> tar_base::backup_finish: TAR - backup: 0 files
16:00:25: <2> tar_base::backup_finish: TAR - backup: file data: 0 bytes
16:00:25: <2> tar_base::backup_finish: TAR - backup: image data: 1024 bytes
16:00:25: <2> tar_base::backup_finish: TAR - backup: elapsed time: 1 secs 1024 bps
16:00:25: <2> tar_base::V_vTarMsgM: INF - EXIT STATUS 1: the requested operation was partially successful





I know thats a lot of info, but i thought i'd post as much as i could, Hope someone can help

Richard Yates
3 REPLIES 3

Jeffrey_Redingt
Level 5
When using target backups for NetWare, the file list is made up of the target names. Keep in mind they are case sensitive also. So if you made a target called NDs for instance then it would look like this in the file list:

\NDs

It has to have the \ followed by the target name.

JR

Yasuhisa_Ishika
Level 6
Partner Accredited Certified
For NetWare target clients, you must write flie list as below:

/target/

Target name must be in upper case. And policy type must be Standard.

Richard_Yates
Level 2
Yup, that did the trick, cheers mate.

We weren't aware you had to specify the actual TARGET, we just thought you had to specify the server name which is wrong.


Thanks again.