Unsolved
This post is more than 5 years old
71 Posts
0
1401
Staging problems with v7.4Sp4
Hello,
I have realized strange things with staging, Despite the fact that I have set high water mark up to 80% and the low water mark to 40% on the backup server networker.izum.pri , staging has been run from the tape. In addition to the storage node intdc2-u staging was trying to run even it should not to, although when I checked the size and the used drive is 1.5 tb from 2tb which is 80%. errors appear in the daemon.log file. Below are the settings for the daily and monthly staging, which I have set following as recommended. I have adjusted the final tasks. Previous I was trying to work on the staging intdc2 concerns is repetitive, I have already noticed. Despite the fact that the disk is filled 1.5 tb/2tb. In all the servers we have a disk for daily and monthly device.
Please see the output from the daemon.log:
11348 20.3.2009 13:50:12 nsrd deactivating mmd #26
11349 20.3.2009 13:50:12 nsrd Calling mm_deactivate for mmd 26 thats using device rd=intdc2.izum.pri:\\.\Tape3 with volume IZUM0014 on host intdc2.izum.pri
42506 20.3.2009 13:50:12 nsrd write completion notice: Writing to volume IZUM0014 complete
11274 20.3.2009 13:50:12 ansrd ansrd_clone FAILED: errnum is 15002 and errstr is cannot open N:\disk2m\48\54\614fc2a6-00000006-c13c47e8-493c47e8-00400000-0a01647a file: No such file or directory
11275 20.3.2009 13:50:12 ansrd failed to execute MODE_CLONE
39078 20.3.2009 13:50:12 nsrstage SYSTEM error: cannot open N:\disk2m\48\54\614fc2a6-00000006-c13c47e8-493c47e8-00400000-0a01647a file: No such file or directory
5777 20.3.2009 13:50:12 nsrstage Cannot open nsrstage session with networker.izum.pri
5882 20.3.2009 13:50:12 nsrstage Failed to clone any save sets
12361 20.3.2009 13:50:15 nsrd [Jukebox `MSL5052', operation # 648]. Finished with status: succeeded
0 20.3.2009 13:51:51 nsrd Operation 649 started : Unload jukebox device `rd=intdc2.izum.pri:\\.\Tape3'.
.
38752 20.3.2009 13:51:53 nsrd rd=intdc2.izum.pri:\\.\Tape3 1:Eject operation in progress
12361 20.3.2009 13:52:38 nsrd [Jukebox `MSL5052', operation # 649]. Finished with status: succeeded
I have realized strange things with staging, Despite the fact that I have set high water mark up to 80% and the low water mark to 40% on the backup server networker.izum.pri , staging has been run from the tape. In addition to the storage node intdc2-u staging was trying to run even it should not to, although when I checked the size and the used drive is 1.5 tb from 2tb which is 80%. errors appear in the daemon.log file. Below are the settings for the daily and monthly staging, which I have set following as recommended. I have adjusted the final tasks. Previous I was trying to work on the staging intdc2 concerns is repetitive, I have already noticed. Despite the fact that the disk is filled 1.5 tb/2tb. In all the servers we have a disk for daily and monthly device.
Please see the output from the daemon.log:
11348 20.3.2009 13:50:12 nsrd deactivating mmd #26
11349 20.3.2009 13:50:12 nsrd Calling mm_deactivate for mmd 26 thats using device rd=intdc2.izum.pri:\\.\Tape3 with volume IZUM0014 on host intdc2.izum.pri
42506 20.3.2009 13:50:12 nsrd write completion notice: Writing to volume IZUM0014 complete
11274 20.3.2009 13:50:12 ansrd ansrd_clone FAILED: errnum is 15002 and errstr is cannot open N:\disk2m\48\54\614fc2a6-00000006-c13c47e8-493c47e8-00400000-0a01647a file: No such file or directory
11275 20.3.2009 13:50:12 ansrd failed to execute MODE_CLONE
39078 20.3.2009 13:50:12 nsrstage SYSTEM error: cannot open N:\disk2m\48\54\614fc2a6-00000006-c13c47e8-493c47e8-00400000-0a01647a file: No such file or directory
5777 20.3.2009 13:50:12 nsrstage Cannot open nsrstage session with networker.izum.pri
5882 20.3.2009 13:50:12 nsrstage Failed to clone any save sets
12361 20.3.2009 13:50:15 nsrd [Jukebox `MSL5052', operation # 648]. Finished with status: succeeded
0 20.3.2009 13:51:51 nsrd Operation 649 started : Unload jukebox device `rd=intdc2.izum.pri:\\.\Tape3'.
.
38752 20.3.2009 13:51:53 nsrd rd=intdc2.izum.pri:\\.\Tape3 1:Eject operation in progress
12361 20.3.2009 13:52:38 nsrd [Jukebox `MSL5052', operation # 649]. Finished with status: succeeded
ble1
2 Intern
2 Intern
•
14.3K Posts
0
March 22nd, 2009 13:00
The error message sent indicates that one of ssids that NW tried to stage was no longer there. Do mminfo -q ssid=614fc2a6-00000006-c13c47e8-493c47e8-00400000-0a01647a -r ssid,name,volume,ssflags,sumflags to see what you get.
cameron11
28 Posts
0
March 22nd, 2009 21:00
There are several possible scenarios that could cause this, and more investigation needs to be done to determine the root cause.
Here are some ideas to get you started:
1) Was an mmrecov performed? (this would recover an older MDB)
2) Were files manually deleted from the AFTD ?
3) Was there an abnormal shutdown of the OS?
4) Was connectivity ever lost to the filesystem where the AFTD is located? (Eg: fiber, NFS, CIFS or network mapped drive)
broeste1
153 Posts
0
April 22nd, 2009 02:00
ble1
2 Intern
2 Intern
•
14.3K Posts
0
April 22nd, 2009 04:00
DavidHampson
1.1K Posts
0
April 22nd, 2009 05:00
I would be particularly concerned if as you appear to be saying that you are backing up to a disk drive within your client - so that client catches fire and nothing remains, how do you get your data back?