I have been having an ongoing issue with my Backup Exec 2010 R3. After upgrading my FAS 2020 to the latest controller firmware several months ago, Backup Exec could no longer to restore files to the NetApp!! It could to Windows machines. This caused alot of consternation, and after almost a month going around with Symantec, I figured out myself that it will restore whole directories, but not individual files. So if I need to restore an individual file, I have to restore a whole directory, then grab that file. Which is fine with small directories, but when I have to restore 150GB directories to get a 20Mb Word file, then I have a problem. So I'm coming back again to see if anybody has had this problem or has some idea of a solution.
The Backup Exec job fails with the following error message:
Completed status: Failed
Final error: 0xe000130a - The NDMP server returned a restore error.
See the NDMP Log for more information.
Final error category: Resource Errors
Here's the NDMP log (from Backup Exec) :
NDMP Log Message: RESTORE: Tue Jul 15 16:08:31 2014 : We have read 420330 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:13:31 2014 : We have read 722153 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:18:31 2014 : We have read 943678 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:23:31 2014 : We have read 1057125 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:28:31 2014 : We have read 1167314 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:33:31 2014 : We have read 1267869 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:38:31 2014 : We have read 1409057 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:43:31 2014 : We have read 1532971 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:48:31 2014 : We have read 1657610 KB from the backup.
NDMP Log Message: RESTORE: Tue Jul 15 16:53:32 2014 : We have read 1767226 KB from the backup.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/BOXFILESTORAGELIST.DOC/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/DirectionsLVOffice.doc/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/LHVTRANSMITTAL1.doc/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/Proposal - Fed Ex.doc/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/RFIR_STAMP_MOCK_UP.pdf/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/Seismic Table.doc/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/SPECISSU.DOC/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/SPECKEY.DOC/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/2-10-webinar.doc/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/aisc webinar.doc/: Path could not be created.
NDMP Log Message: RESTORE: /vol/CIFS/NetAdmin/Restore/cooper hospital.doc/: Path could not be created.
NDMP Log Message: RESTORE: No files were created.
NDMP Log Message: RESTORE: RESTORE IS ABORTED
NDMP Data Halted: Internal Error
NDMP Log Message: Dump aborted.
NDMP Log Message: Mover: Closing data connection.
NDMP Mover Halted: Connect Closed
================ NDMP ENVIRONMENT ================
DMP_NAME=NDMP
DIRECT=Y
VERBOSE=N
DEBUG=N
LIST=N
SMTAPE_BREAK_MIRROR=N
LIST_QTREES=N
EXTRACT=Y
RESTART=N
IGNORE_QTREES=N
MULTI_SUBTREE_NAMES=engineer
secure-c
clerical
typdet
approachDB
MAH_MP
CAD
projects
NetAdmin
RECOVER_FULL_PATHS=N
FILESYSTEM=/vol/CIFS
EXTRACT_ACL=Y
DATA_BLOCK_SIZE=64
SMTAPE_DELETE_SNAPSHOT=N
REPLICATE=N
TYPE=dump
RECURSIVE=Y
HIST=Y
EXCLUDE=*.bak, *.plt, *.tmp, *.mp3, *.mpeg
LEVEL=0
NDMP_UNICODE_FH=N
NDMP_VERSION=4
FORCE=N
DUMP_DATE=-1
ACL_START=2863959305216
RENAME_SUPPORTED=Y
UPDATE=Y
NOWRITE=N
NON_QUOTA_TREE=N
ENHANCED_DAR_ENABLED=T
BASE_DATE=-1
NO_ACLS=N
=============== NDMP ENVIRONMENT END ===============
|
You see the strange Path Could Not Be Created? Well, it creates those directories, but they're supposed to be files, as you can tell by the .DOC extensions. Plus, there is that strange /: after each filename.
If anyone has any ideas why this may be happening, and any suggestions for a fix, I would be immensely appreciative. As I said, this occurred after we upgraded to the latest controller firmware, I believe.
Thanks in advance!
