Unsolved
This post is more than 5 years old
7 Posts
0
2153
HNAS NDMP BACKUP Failed
Hello
1. Failure information
-------------------------------
- NDMP Backup Not Success
- The failure index File : /nsr/tmp/
--------------------------------------------------------
2. Current Configuration
- Networekr ver : 7.5.4
- NAS : hitachi HNAS - 3060
- network backup (NO SAN)
- File Qty : 194276539
- Total File Size : 2376GB
- Backup Time : 4Day 10:00
- Configuration backup failed because no index(Symptoms such as when you configure index)
savegrp.log
------------------------------
NetWorker savegroup: (alert) FILE_HNAS-Cluster-1 completed, Total 1 client(s), 1 Failed. Please see group completion details for more information.
Failed: HNAS-Cluster-1
Start time: Sat Oct 10 03:00:00 2015
End time: Wed Oct 14 13:33:06 2015
-- Unsuccessful Save Sets ---
* HNAS-Cluster-1:/easap savegrp: suppressed 110 lines of output.
* HNAS-Cluster-1:/easap
* HNAS-Cluster-1:/easap The NDMP backup is complete.
HNAS-Cluster-1: /easap level=full, 2376 GB 103:07:01 194276539 files
* HNAS-Cluster-1:/easap 42913:nsrndmp_save: Save session closed with NW server successfully
* HNAS-Cluster-1:/easap
* HNAS-Cluster-1:/easap 42914:nsrndmp_save: Sorting File History....
* HNAS-Cluster-1:/easap 42916:nsrndmp_save: Sorting File History completed Successfully in 01:26:56 Hours
* HNAS-Cluster-1:/easap
* HNAS-Cluster-1:/easap 42917:nsrndmp_save: Processing NDMP File History...
* HNAS-Cluster-1:/easap 39078:nsrdmpix: SYSTEM error: Not enough space
* HNAS-Cluster-1:/easap
* HNAS-Cluster-1:/easap 42952:nsrndmp_save: HNAS-Cluster-1:/easap Processing NDMP File History failed on 'usms1'
* HNAS-Cluster-1:/easap
* HNAS-Cluster-1:/easap 42921:nsrndmp_save: recoverable(no indexes) savetime=1444413654
* HNAS-Cluster-1:/easap 42697:nsrndmp_save: Leaving /nsr/tmp/FileIndex639107350/fhfile
* HNAS-Cluster-1:/easap 42927:nsrndmp_save: Successfully done
* : Failed with error(s)
----------------------------------
daemon.log
39074 10/14/15 12:52:15 nsrjobd JOBS notice: Completed full database purge in 0 min 11 sec. Records purged: 84
42506 10/14/15 13:33:00 nsrd ndmp save notice: HNAS-Cluster-1:/easap Processing NDMP File History failed on 'umbsms1'
42506 10/14/15 13:33:00 nsrd ndmp save notice: HNAS-Cluster-1:/easap NDMP save succeeded on 'umbsms1'
77561 10/14/15 13:33:01 savegrp command 'nsrndmp_save -T dump -s umbsms1 -c HNAS-Cluster-1 -g FILE_HNAS-Cluster-1 -l full -LL -q -W 78 -N /easap /easap' for client HNAS-Cluster-1 exited with return code -1
98260 10/14/15 13:33:01 nsrjobd Failed to write job status of jobid 298013 to jobsdb with err: actual exit code is not a positive number
77562 10/14/15 13:33:01 savegrp job (298013) host: HNAS-Cluster-1 savepoint: /easap had ERROR indication(s) at completion
77567 10/14/15 13:33:06 savegrp FILE_HNAS-Cluster-1 * HNAS-Cluster-1:/easap See the file /nsr/tmp/sg/FILE_HNAS-Cluster-1/sso.HNAS-Cluster-1.wLEjUc for output of save command.
7341 10/14/15 13:33:06 savegrp HNAS-Cluster-1:/easap failed.
7241 10/14/15 13:33:06 savegrp nsrim run recently, skipping
38758 10/14/15 13:33:06 nsrd savegroup failure alert: FILE_HNAS-Cluster-1 Completed/Aborted, Total 1 client(s), 0 Clients disabled, 0 Hostname(s) Unresolved, 1 Failed, 0 Succeeded, 0 CPR Failed, 0 CPR Succeeded.
38758 10/14/15 13:33:07 nsrd savegroup alert: FILE_HNAS-Cluster-1 completed, Total 1 client(s), 1 Failed. Please see group completion details for more information.
0 10/14/15 13:33:07 nsrd notification process "/usr/bin/logger -p daemon.notice" failed with status "1"
12662 10/14/15 13:33:10 nsrd runq: NSR group FILE_HNAS-Cluster-1 exited with return code 1.
0 10/14/15 13:33:24 nsrd notification process "/nsr/script/monitor.ksh >> /nsr/logs/monitor/monitor_`/bin/date +%m%d%y`.log" failed with status "126"
39074 10/14/15 13:52:09 nsrjobd JOBS notice: Starting full purge of jobs database
ble1
14.3K Posts
0
October 21st, 2015 05:00
>>>> nsrdmpix: SYSTEM error: Not enough space <<<<
Can you enlarge your file system where /nsr/tmp is? Also check size of /nsr/index. Chances are you most likely have both on same file system and there is no enough space to merge records created during backup with actual index of the client.
greenbell_young
7 Posts
0
October 21st, 2015 22:00
Hello.
Space in /nsr/tmp is 800GB
Space in /nsr/index is 50GB
Backup client is no index backup. In no index /nsr/index Can it be affected?
Thank you
ble1
14.3K Posts
0
October 22nd, 2015 04:00
> Backup client is no index backup
Not sure what you think here, but I guess you can't find the index there? Check in client properties first if no alternative path is used for index of that client. If not, chances are that /nsr/index doesn't have enough space to get temp files (which are built during backup and placed in /nsr/tmp) to be merged/moved to /nsr/index area.