|
Product: StorageExpress™ Backup Server
E3001, E3006, E3007, E3008, E3009, E3011, E3012, E3013, E3014, E3015,
E3016, E3018, E3019, E3020, E3025, E3031, E3066, E3075, E3082, E3083, E3084,
E3001 - Failed to get [volume]'s number, [NetWare error code]
Problem
The specified volume is not visible to the network. Either the
volume has been dismounted or the connection to the server
containing it has been broken.
Resolution
Use CHKVOL or VOLINFO (for NetWare 3.1x) or NDIR (for NetWare 4.x)
to see if the volume is still mounted. Use SLIST or MAP to see if
the connection to the volume's server has been broken. See Network
Communications Troubleshooting Checklist.
E3006 - Failed to get[file name]'s information, [NetWare error code]
E3025 - Failed to scan [file name or directory] trustees, [NetWare error
code]
E3031 - Failed to scan[volume] ([directory])'s space restrictions,
[NetWare error code]
E3075 - Failed to enable login to server [server name], [NetWare error
code]
E3082 - Failed to assign trustee to [file or directory],
objectID=[object] rights=[rights], [NetWare error code]
E3083 - Failed to set [volume or directory] space restriction to
[number] KB), [NetWare error code]
E3084 - Failed to add object [object id]'s space restriction
([number]KB) to [volume], [NetWare error code]
Problem
Either the specified directory or file doesn't exist, or the
account being used to access it does not have sufficient rights to
access it.
Resolution
Make sure that the file/directory has not been renamed or deleted.
Check to see that the user has appropriate rights to the
file/directory.
E3007 - Failed to back up [Macintosh file name]'s resource fork
E3008 - Failed to back up [Macintosh file name]'s data fork
Problem
This error occurs due to one of the following:
1. The file is open and locked by another application.
2. The file has been deleted.
3. The connection to the source has been broken.
Resolution
For each of the causes, do the following:
1. Use the NetWare MONITOR utility to see what user or process has
the file locked, then close the offending application or clear the
connection that has locked the file.
2. Make sure that the file exists in the specified directory (or
folder).
3. Use MAP or SLIST to see if the connection to the source server
has been broken. See Server Communications Troubleshooting
Checklist.
E3009 - Failed to open [file name] at end of session
Problem
ARCserve is attempting to access a file that it was unable to
access during the course of a job, as per the Open File Retry
options specified during the job's creation. Again, the file has
been found to be open.
Resolution
Have the application close the open file or schedule the job for a
time when the file is not in use.
E3011 Failed to open file [file name], [NetWare error code]
E3011 Failed to open file SYS:\Monitrix\DUMP\"dump file." Resource in use.
E3011 Failed to open file (ALT 255) Files missed from backup
Problem
There can be several reasons for this error message:
1. The file doesn't exist.
2. An explicitly specified path to a file was entered incorrectly.
3. The file is in use by another application which has it open in
exclusive mode, and the file hasn't been flagged as shareable.
4. The account being used to access the file does not have
sufficient rights to access it.
Resolution
1. Make sure the file exists in the directory specified.
2. Make sure that the file is not in use by another application or
process and that it is flagged as
Shareable (if appropriate). In the Backup Options screen of the
ARCserve Manager, set the
Open File Method to Deny None if Deny Write Fails and retry the
job.
3. Check that the account being used to access the file has the
appropriate rights.
NOTE: If this sort of problem occurs frequently, it may be
advisable to run the backup job at a time when there is a lesser
chance of users accessing files or to activate the Clear User
Connections Before Job option in the Backup Options screen of the
ARCserve Manager.
Resolution E3011 Failed to open file SYS:\Monitrix\DUMP\"dump file."
Resource in use.
This is caused by ARCserve trying to back up the Monitrix Dump file
while Monitrix is trying to update its database. A solution that
will ensure a proper backup of the Monitrix files is to set up a
Pre/Post-execution command in the ARCserve job that will perform a
MONSTOP before the backup and a MONSTART afterwards.
Problem E3011 Failed to open file (ALT 255) Files missed from
backup
When the ASCII 255 null space character is used as part of a file
name (by pressing the ALT-255 keystroke sequence), the file is
missed from the backup job, but no indication is made in the
activity log that the file was missed. The error only occurs when
ARCserve is in Full SMS mode. If the server is not using SMS
logic, the files will be backed up and restored properly.
Resolution E3011 Failed to open file (ALT 255) Files missed from
backup
The only workaround at this time is to disable SMS logic.
E3012 - Failed to open [Macintosh file name]'s resource fork, [NetWare
error code]
E3013 - Failed to open [Macintosh file name]'s data fork, [NetWare error
code]
Problem
There can be several reasons for this error message:
1. The file doesn't exist.
2. An explicitly specified path to a file was entered incorrectly.
3. The file is in use by another application which has it open in
exclusive mode, and the file hasn't been flagged as shareable.
4. The account being used to access the file does not have
sufficient rights to access it.
Resolution
1. Make sure the file exists in the directory specified.
2. Make sure that the file is not in use by another application or
process and that it is flagged as Shareable (if appropriate). In
the Backup Options screen of the ARCserve Manager, set the Open
File Method to Deny None if Deny Write Fails and retry the job.
3. Check that the account being used to access the file has the
appropriate rights.
NOTE: If this sort of problem occurs frequently, it may be
advisable to run the backup job at a time when there is a lesser
chance of users accessing files or to activate the Clear User
Connections Before Job option in the Backup Options screen of the
ARCserve Manager.
E3014 - Failed to get [filename]'s AFP information, [error code].
Problem
File has been deleted.
E3015 - Service connection with [file server] is broken, [NetWare error
code]
Problem
The connection to the specified file server has been broken.
Resolution
If you see this error message, use the following checklist:
Check that the specified server exists on the network.
Check the communications path to the server, such as routers,
bridges, cabling, etc.
Make sure that the latest versions of the LAN drivers are being
used on both servers.
Make sure that the LAN cards are functioning properly. Try
replacing the LAN cards and drivers with those from a different
vendor on both servers.
See also Server Communications Troubleshooting Checklist.
E3016 - Failed to access [file server]/[directory], [NetWare error code]
Problem
ARCserve has failed to access the directory due to one or more of
the following:
1. The target file/directory no longer exists.
2. The volume containing the file/directory has been dismounted
3. The connection to the source file server has been broken
Resolution
Check the NetWare error code specified for more information on the
exact nature of the problem. For each of the above causes, check
the following:
1. Check to see if the target file/directory has been deleted.
2. Use the CHKVOL or VOLINFO command (for NetWare 3.1x) or the NDIR
command (for NetWare
4.x) to see if the volume has been dismounted.
3. Use the MAP or SLIST command to see if the connection to the
source server has been broken.
See Server Communications Troubleshooting Checklist.
E3018 - Failed to initialize work file [file name]
Problem
The ARCserve host volume is out of disk space.
Resolution
More disk space needs to be made available on the ARCserve host
volume.
See also TECHNOTE: ARCserve and File Server Disk Space Problems.
E3019 - Failed to load RWDB
Problem
FSTAPE.NLM was not able to spawn RWDB.NLM, either because there was
insufficient memory available on the ARCserve host server, or
because the RWDB.NLM file was damaged or non-existent.
Resolution
The function of RWDB.NLM is to reset the "last accessed" dates and
the file attributes of files that have just been backed up by
ARCserve. The failure to spawn this NLM will not affect the
success or failure of the backup job, however, files will show
themselves as having been accessed during the backup and archive
bits (if specified) will not be reset.
1. See Checking the File Server's Memory Status.
2. Make sure that RWDB.NLM exists in the \ARCSERVE\NLM directory.
If the problem persists, it may be necessary to replace RWDB.NLM
with a new copy from the ARCserve installation disks (using the
Microsoft EXPAND utility).
E3020 - Failed to set CWD to [file path]
Problem
There is an problem with certain CLIB functions when accessing
files with extended ASCII characters in the name, such as ',' which
is displayed as the trademark symbol on a Macintosh. If a
directory name contains one of these characters, a backup may stop
scanning at this directory and not back up the rest of the
directories.
Resolution
Novell has recently released LIBIT6.EXE to their CompuServe forum
(GO NOVLIB), which contains CLIB.NLM v4.10d PTF (for NetWare 4.x).
LIBUP4.EXE contains CLIB.NLM v3.12h (for NetWare 3.x). These
versions will allow for unattended Backup/Restore operations of
files with extended ASCII character sets. The original workaround
is to rename the offending directories, avoiding all non-standard
characters, and repeat the job.
E3021 - Failed to change directory [server name/volume name]:,ffffffff
E3022 - Invalid Directory
Problem
These errors occur intermittently during a backup job. The E3021
occurs at the start of a session backup. After a second attempt at
backing up the session is made, and fails, the session backup is
canceled and ARCserve will not back up any other volumes on that
server. This occurs during both host & remote server backups on
servers running NetWare 4.0x. It can also occur on Netware 3.1x
servers running a version of CLIB.NLM prior to 3.12g. The E3125
error occurs when ARCserve is attempting to back up a remote server
that has more than 1000 directories (total) on all of its volumes.
Resolution
The problem is due to an interaction with CLIB.NLM versions 4.01d
and previous. Update all NetWare 4.0x servers to CLIB.NLM version
4.01d (PTF 940309) or later. Breaking up large backup jobs into
smaller ones (of less than 1000 directories each) may also be used
as a temporary workaround to the problem.
E3024 - Failed to map path, volume, directory [file path]
Problem
There is an problem with certain CLIB functions when accessing
files with extended ASCII characters in the name, such as ',' which
is displayed as the trademark symbol on a Macintosh. If a
directory name contains one of these characters, a backup may stop
scanning at this directory and not back up the rest of the
directories.
Resolution
Novell has recently released LIBIT6.EXE to their CompuServe forum
(GO NOVLIB), which contains CLIB.NLM v4.10d PTF (for NetWare 4.x).
LIBUP4.EXE contains CLIB.NLM v3.12h (for NetWare 3.x). These
versions will allow for unattended Backup/Restore operations of
files with extended ASCII character sets. The original workaround
is to rename the offending directories, avoiding all non-standard
characters, and repeat the job.
E3024 Failed to map path sys:, FFFFFFFF on SFT-III version 4.10
Problem
When the user attempted to backup an SFT-III 4.10 server with MAC
namespace installed, he received the following error:
E3024 Failed to map path sys:, FFFFFFFF
Resolution
Installing LIBIT9.EXE to the DOS partition on both IO servers as
well as in the SYS:SYSTEM directory resolved the problem.
E3027 - Failed to Cache Backup Set, ff
Problem
There was not enough disk space on the SYS volume of the ARCserve
host server to complete the operation.
Resolution
Free up disk space on the SYS volume of the ARCserve host server,
and then reschedule the job. See also TECHNOTE: ARCserve and File
Server Disk Space Problems.
E3028 Failed to read from scan buffer, [Error Code].
E3029 Failed to access relative path (Request =11 Actual = 2).
Resolution
Usually happens after E3112. Usually happens when there is little
or no disk space in the ARCserve Home Directory. Follow
instructions for E3018.
E3037 - Failed to allocate tape buffer
E3038 - Failed to allocate [entity] ([size] bytes)
E3073 - Failed to allocate block map for [file name] ([number] blocks)
[number] bytes
E3112 - Failed to update Scan Buffer, req=16372 actual =-1
Problem
There was not enough memory available on the ARCserve host server
to create the tape buffers necessary for an ARCserve operation.
Resolution
See Checking File Server Memory Status.
Check server memory. You can do this by following these steps:
1. Enter LOAD MONITOR from the server console.
2. Select "Resource Utilization" from the Available Options menu.
3. If the cache buffer's percentage is very low (below 30%), your
server is probably low on memory.
4. To free up some memory, unload any NLMs that are not required.
5. Enter ASTOP from the server console to stop ARCserve.
6. Enter ASTART from the server console to restart ARCserve.
If it happens again, you should restart the file server. You
should also consider purchasing more memory for the file server.
E3112 Failed to update Scan Buffer, req=16372 actual = -1.
Resolution
Not enough space on the SYS volume. Try freeing disk space on SYS
volume of the ARCSERVE host server.
E3046 Failed to set database [name] to backup mode. Check Btrieve Error
(86) "File Full"
Problem
The BTRIEVE.NLM has to many Btrieve database files opened during
backup and the "Number of Open Files" parameter has been reached.
Resolution
Modify the load statement for BTRIEVE.NLM to include the parameter
-f=30 or higher. Default value is 20.
Example: LOAD BTRIEVE -f=30
E3047 Failed to get database [database name]'s file name(s), [NetWare
error code].
Problem
None.
Resolution
This is an internal error. Contact your reseller or Cheyenne
Technical Support.
E3052 Failed to read [file] or [directory]'s information, [NetWare error
code].
Problem
None.
Resolution
See E1061.
E3058 - Failed to submit InocuLAN scan request - time-out
E3059 - Failed to submit Inoculan scan request 1, fc
Problem
InocuLAN failed to respond to ARCserve's request for a virus scan,
due either to its not being properly loaded on the server or to it
being busy performing another scan.
Resolution
The success or failure of a backup job will not be affected by
these errors, but the requested virus scan will not be performed.
Make sure that InocuLAN is properly installed on the server, and
that it is not being monopolized by another process. Check the
InocuLAN Activity Log and/or documentation for more infomation on
InocuLAN's current status.
E3065 - Failed to set [file name]'s information, [NetWare error code]
E3066 - Failed to change [file name]'s information, [NetWare error code]
Problem
The account being used access the specified file does not have
appropriate rights to perform this function, or the file has been
deleted.
Resolution
Using SYSCON (for NetWare 3.1x), NWADMIN ot NETADMIN (for NetWare
4.x), make sure that the backup user has sufficient rights to
modify the file information. Also, make sure that the file exists
on the path specified.
E3067 - Failed to read next file header, [NetWare error code]
E3120 - Failed to Backup [filename], [error code]
Problem
There is a problem reading the tape, possible due to media or
hardware problems.
Resolution
See Tape Drive Troubleshooting Checklist. The tape may be bad. See
E1061.
E3068 Failed to Start FTS session, fffffff
Problem
The error E3068 Failed to Start FTS session, fffffff will be
generated if two or more concurrent backup operations are running
and a second job attempts to back up the ARCserve database (FTS)
while one job already has the database open and in a continuous
mode. The code was changed in the 5.01e release to allow this
error to occur so that ARCserve would not attempt to repeatedly
back up the database during multiple concurrent backup operations.
ARCserve 5.01d will back up the database without error, but would
create a condition of greatly increased Processor Utilization on
the server and would waste time and tape, as the database had
already been successfully backed up.
Resolution
Upgrade the user to 5.01g or above. An additional error will be
reported in 5.01g when this condition exists. The error message is
"E3151 Failed to put FTS in backup mode, ffffffff - Is FTS already
being backed up?" To avoid the error, the start time of the jobs
should be changed so that the database will not be accessed by any
two jobs at the same time. The activity log can be used to
determine how much time is required for each job to back up the
database. The execution times of the jobs would then need to be
separated by this amount of time.
Also see E1061, E3018.
E3076 - Failed to lock [file name] (sz = [size of file]), [NetWare error
code]
Problem
ARCserve cannot lock the specified file because it is in use.
Resolution
1. Use the NetWare MONITOR utility to determine which user or
process has the specified file open.
2. When creating the job using the ARCserve Manager, do not select
Use Lock Mode if Deny Write Fails from the Open File Method dialog
in the Backup Options screen if there is a good chance the files
will be in use. Instead, choose Deny None if Deny Write Fails.
This will allow a user to view a file while it is being backed up.
E3079 - Failed to create file [file name], [NetWare error code], [error
description]
E3085 - Failed to create Mac. folder (Macintosh file name), [NetWare
error code]
E3091 - Failed to restore (Macintosh file name)'s resource fork
E3092 - Failed to restore (Macintosh file name) data fork
E3093 - Failed to write (Macintosh file name)'s resource fork, request:
[file size] actual:[size that was actually written successfully]
E3094 - Failed to write (Macintosh file name)'s data fork, request:
[file size] actual:[size that was actually written successfully]
E3095 - Failed to create Mac file [Macintosh file name], [NetWare error
code]
Problem
Files were not written to the target drive for any of the following
reasons:
1. There is insufficient disk space on the target volume or drive.
2. There is an error reading data from the tape
3. The account being used to write the files to the target has
insufficient rights to perform the operation.
Resolution
For each of the causes, check the following:
1. Make sure that there is adequate disk space available on the
target volume or drive.
See also TECHNOTE: ARCserve. and File Server Disk Space
Problems.
2. See Tape Drive Troubleshooting Checklist for infomation on
checking for media and hardware errors.
3. Make sure that the backup user has sufficient rights to create
the files and that it is not subject to Volume or Disk restrictions
that would prevent files from being created.
E3079 Failed to Create <pathname>\filename, 1 no space left
Problem
User receives E3079 error messages during an unattended restore to
a server drive with File Conflict Resolution set to "Overwrite All
Files." If the destination server hard drive is completely filled
with a combination of actual files and files in the \DELETED.SAV
directory (ie: salvageable files), the operating system will not be
able to purge the files from \DELETED.SAV as quickly as ARCserve
writes new files to the disk. By default, NetWare will not purge a
file until the time since the file was deleted is greater than the
"File Delete Wait Time." The default setting is 5 minutes,
29.6 seconds.
Resolution
Lower the setting for the "File Delete Wait Time" to 0 by typing the
following at the file server console prompt:
SET FILE DELETE WAIT TIME=0
This will allow files in the \DELETED.SAV directory to be purged
immediately and the new files written to disk by ARCserve to be
successfully created.
E3080 - Failed to restore [filename] - request:[file size] actual:[how
much was restored successfully], [NetWare error code]
Problem
The specified file restored is of a different size than the copy on
tape for one of the following reasons:
1. There is not enough disk space available on the target volume or
drive.
2. There is some corruption in the file.
3. The connection with the remote server has been broken.
Resolution
1. Check to see that there is sufficient disk space available on
the target drive or volume. Also, check for directory and user
space restrictions with the NetWare DSPACE utility.
See also TECHNOTE: ARCserve and File Server Disk Space Problems
for more information.
2. Try to restore the file to a temporary directory and then run it
in its native application to see if it has been corrupted. If it
is, see Tape Drive Troubleshooting Checklist.
3. See Network Communications Troubleshooting Checklist.
E3074 - Failed to disable login to server [server name], [NetWare error
code]
E3102 - Failed to Clear Connection, c6
Problem
Connections are not being cleared at the beginning of a backup job,
causing both of the above errors to be generated, particularly (but
not exclusively) when the target is a NetWare 4.x server.
Resolution
The account being used to access the target server must be a
Console Operator. For NetWare 4.x, use NWADMIN or NETADMIN to
assign the backup user rights as a Console Operator. For NetWare
3.1x, use SYSCON. File Server Console Operators is located under
the Supervisor Options menu.
E3090 - Failed to open (Macintosh file name)'s data fork,[NetWare error
code]
Problem
Either the specified file does not exist, or the account being used
to access the specified file does not have the appropriate rights
needed to complete the operation assigned to it.
Resolution
Make sure that the file exists on the specified path, and check the
access rights of the backup user.
E3096 - Failed to restore sparse file [file name], [number] segments
Problem
There is insufficient disk space on the target volume or drive.
Resolution
Free up an adequate amount of disk space on the target drive or
volume. See also TECHNOTE: ARCserve and File Server Disk Space
Problems.
E3061 InocuLAN scanner error - [NetWare error code].
E3069 Failed to end FTS backup - [NetWare error code].
E3070 Failed to delete Mac file (MacIntosh file name), [NetWare error
code].
E3078 Failed to get [Volume]'s statistics, [NetWare error code].
E3086 Failed to get (MacIntosh file name)'s entry id, [NetWare error
code].
E3087 Failed to request (MacIntosh file name)'s info, [NetWare error
code].
E3088 Failed to set (MacIntosh file name)'s info, [NetWare error code].
Resolution
See E1061.
E3072 Failed to read [file name]'s map ([number] bytes).
Resolution
ARCserve couldn't read the sparse file's map due to the number of
seqments.
E3035 Failed to start session, [NetWare error code].
Resolution
Seems to be a problem with the ARCSERVE Btrieve database. Try
repairing the database.
E3111 - Too many subdirectories
Problem
This error is generated when backing up a host or remote file
server. On a host server, the maximum number of subdirectory
levels that can be successfully backed up is 100. On remote
servers, the maximum is 16.
Resolution
There is none at the present time. A future release of ARCserve
will increase the remote server limitation to 100.
E3123 Failed to connect to TS on rverName>, [error code].
Resolution
User was attempting to do a SMS backup but TSA was not loaded on
the server. Try loading the TSA on the server or else disable SMS
backup option in the ARCSERVE configuration.
E3105 - Failed to query [directory]'s disk space limit, [NetWare error
code]
E3106 - Failed to query user's disk space allocation limit, [NetWare
error code]
Problem
The account being used to perform the ARCserve operation has
insufficient rights to perform this function.
Resolution
Use SYSCON (for NetWare 3.1x) or NETADMIN or NWADMIN (for NetWare
4.x) to make sure that the backup user has the appropriate rights
to perform this function.
E3113 Failed to get [path\file] SYS:'s session id
E3114 Missed file [path\file] in NWBTRV [group]
E3114 Missed file ARCSERVE\DATABASE\*.DB Database not fully protected
Problem
1. These messages appear in the ARCserve 5.x Activity Log. They
occur when the specified database is not selected as a source for a
particular backup job. The is because the DBagent will
automatically prepare all database files for backup, but only those
selected in the ARCserve Manager will be placed into backup mode.
2. This error referring to the \ARCSERVE\DATABASE files occurs
when the DBagent for SQL is installed and the ARCSERVE\DATABASE
directory is specified as a source directory to be backed up.
Resolution
1. None, this is a notification message, not an error.
2. The \ARCSERVE\DATABASE directory should be excluded from the
backup job so that it will get backed up normally at the end of the
job, as it is with every ARCserve backup job.
E3123 - Failed to Connect To TSA on [ServerName], [error code]
Failed to login/connect to TSA as Supervisor, FFFDFFD7
Problem
1. The E3123 message indicates that the ARCserve server did not
connect to the TSA on the server name specified. It only indicates
a problem if the user intended to perform a backup in Full SMS
mode.
2. The second message appears in the ARCserve Activity Log when
attempting to back up a NetWare 4.x server using ARCserve 5.x. It
indicates that the backup user is attempting to log into the TSA as
Supervisor, but Supervisor does not exist in the NDS.
Resolution
1. Unless it is essential that a Full SMS backup be performed,
this message is purely informational and may be ignored. However,
if the appropriate TSA has been loaded on the target server, then
this message indicates the existence of a communications problem
between servers. See Network Communications Troubleshooting
Checklist.
2. Have the user create a new user (not Supervisor). This user
should exist in Bindery Emulation, have Supervisor Object Rights to
the Root of the NDS Tree and have Admin Equivalent Rights.
Note: One way to be sure that the user can login to the TSA is to
add the user and password to the Server Security Login field. This
can be done by enabling Node Options in the Source Configuration
screen of the ARCserve Manager's Backup Window.
E3123 - Failed to Connect To TS on server (server name), fffdffd7
-ARCnet
Problem
A user received the above message when he attempted to backup NDS.
If the user powered on any PC on his ARCnet network segment, the
error would no longer appear.
Resolution
The above error is indicative of the nature of the ARCnet media
protocol. ARCnet uses a token passing bus algorithm. Therefore,
it logically emulates a ring. To have a valid ring in ARCnet, you
must have more than one machine (and not just the file server)
active on the ARCnet segment. Turning on a second machine creates
a valid ring. Installing a terminated Ethernet card in the file
server will also resolve the issue.
E3125 - Failed to scan trustee, 9d" problem
E3125 - Failed to read [filename]'s data set, fffdfe83
Problem
These errors occur intermittently during a backup job. The E3021
occurs at the start of a session backup. After a second attempt at
backing up the session is made, and fails, the session backup is
canceled and ARCserve will not back up any other volumes on that
server. This occurs during both host & remote server backups on
servers running NetWare 4.0x. It can also occur on Netware 3.1x
servers running a version of CLIB.NLM prior to 3.12g. The E3125
error occurs when ARCserve is attempting to back up a remote server
that has more than 1000 directories (total) on all of its volumes.
Resolution
The problem is due to an interaction with CLIB.NLM versions 4.01d
and previous. Update all NetWare 4.0x servers to CLIB.NLM version
4.01d (PTF 940309) or later. Breaking up large backup jobs into
smaller ones (of less than 1000 directories each) may also be used
as a temporary workaround to the problem.
E3125 - Failed to read [filename]'s data set, [error code] Failed to
read (context) data set, FFFDFEFF
Problem 1
This error occurs when running ARCserve 5.x on NetWare 4.x and the
account being used to back up the NDS is not a Admin Equivalent.
Problem 2
It has been found that if login is disabled during a full volume
backup of a 4.01 Server, the NDS will not be protected (backed up).
The following errors would be generated:
E3125 Failed to read .[Root]'s data set, fffdfeff
Error in NWSMTSScanNextDataSet, fffdfeff
0 files 16kb written to tape
Directory Services database is not protected
E3123 Failed to connect to TS on server Servername, fffdffd7
Problem 3
The same failure will occur if the user runs a full volume backup
of a 4.01 Server and has enabled the Clear User Connections Before
Job option in the ARCserve Manager's Backup Options screen. This
command will also disable login to the server. The following
errors would be generated:
E3125 Failed to read .[Root]'s data set, fffdfeff
Error in NWSMTSScanNextDataSet, fffdfeff
0 files 16kb written to tape
Directory Services database is not protected
E3124 Failed to release TS on server Servername, fffdffd6
Resolution 1
1. Create a user with full rights in the NDS that is being backed
up.
2. Update the server's CLIB.NLM to version 4.01d (PTF 940309)
version. This is ONLY available
from the Cheyenne Online Services. See E3021 for details.
3. Upgrade ARCserve to version 5.01e or higher.
Resolution 2-3
In each situation the data will still be backed up. This will not
damage the NDS. Upgrading ARCserve to version 5.01e or higher will
resolve the problem.
E3150 Failed to insert record volume:\path\file in FTS, ffffffff
Problem
When running 6 concurrent Autopilot Jobs on a 5.01g server, several
pages of the above error message are egenerated during the backups.
Apparently, all of the ^^^ files are being hit at the same time.
Resolution
Using the LOAD ARCSERVE NO_AP_FTS switch for the AP jobs will
prevent the pccurrence of the error messages. However, a custom
job must be created in order to back up the databases after all the
AutoPilot jobs have completed.
E3101 Failed to get volume [volume name]'s information, conid = [id
number], [NetWare error code].
E3104 Failed to unlock [file name] size = [file size], [NetWare error
code].
E3108 Invalid trustee size [size] (max = [maximum size]).
Resolution
See E1061.
E3105 Failed to query [directory]'s disk space limit, [NetWare error
code].
E3106 Failed to query user's disk space allocation limit, [NetWare error
code]
Problem
The user doesn't have appropriate rights to perform this function.
Resolution
Check the assigned rights.
This applies to:
|
