Forum Discussion

Level 4

9 years ago

NDMP error 99

Hi,

Since few days, I have some trouble on my NDMP backups. My backup selection is shared between many streams. All full backup are OK, but some of incr backup fails with status 99. Apparently, the level 0 dump is post-dated, and I have this error : "Aborting the incremental dump of level (1) because the snapshot specified for this backup is older than the one used in the previous dump."

14/02/2016 22:36:37 - connecting

14/02/2016 22:36:37 - connected; connect time: 00:00:00

14/02/2016 22:36:38 - mounting CAD126

14/02/2016 22:38:15 - Info bptm(pid=17364) media id CAD126 mounted on drive index 2, drivepath nrst1a, drivename HP.ULTRIUM5-SCSI.002, copy 1

14/02/2016 22:38:15 - mounted; mount time: 00:01:37

14/02/2016 22:38:20 - Info ndmpagent(pid=18976) bstou103: SCSI: TAPE READ: short read for nrst1a

14/02/2016 22:38:21 - positioning CAD126 to file 44

14/02/2016 22:39:35 - Info ndmpagent(pid=18976) bstou103: DUMP: creating "/vol/volpoles/../snapshot_for_backup.3112" snapshot.

14/02/2016 22:39:35 - positioned CAD126; position time: 00:01:14

14/02/2016 22:39:35 - begin writing

14/02/2016 22:39:37 - Info ndmpagent(pid=18976) bstou103: DUMP: Using subtree dump

14/02/2016 22:39:51 - Info ndmpagent(pid=18976) bstou103: DUMP: Date of this level 1 dump snapshot: Sun Feb 14 22:40:46 2016.

14/02/2016 22:39:52 - Info ndmpagent(pid=18976) bstou103: DUMP: Date of last level 0 dump: Tue Jan 19 04:14:07 2038.

14/02/2016 22:39:52 - Error ndmpagent(pid=18976) bstou103: DUMP: Aborting the incremental dump of level (1) because the snapshot specified for this backup is older than the one used in the previous dump.

14/02/2016 22:39:52 - Error ndmpagent(pid=18976) bstou103: DUMP: Dump failed to initialize.

14/02/2016 22:39:53 - Error ndmpagent(pid=18976) bstou103: DUMP: DUMP IS ABORTED

14/02/2016 22:39:54 - Info ndmpagent(pid=18976) bstou103: DUMP: Deleting "/vol/volpoles/../snapshot_for_backup.3112" snapshot.

14/02/2016 22:39:56 - Error ndmpagent(pid=18976) bstou103: DATA: Operation terminated: EVENT: INTERNAL ERROR (for /vol/volpoles/qtpoles/PRP/SERIS)

14/02/2016 22:39:56 - Error ndmpagent(pid=18976) NDMP backup failed, path = /vol/volpoles/qtpoles/PRP/SERIS

14/02/2016 22:39:57 - Error bptm(pid=17364) none of the NDMP backups for client bstou103 completed successfully

14/02/2016 22:40:23 - Info bptm(pid=17364) EXITING with status 99 <----------

14/02/2016 22:40:24 - end writing; write time: 00:00:49

NDMP backup failure(99)

Any idea ? My version is 7.5.0.4

Thanks !

Windows Server (2003-2008)

cruisen
9 years ago
OK ,

I saw that veritas has published a technote in reference to this post:

https://www.veritas.com/support/en_US/article.000108612

Best regards,

Cruisen

shrutisharma_18

Level 0

11 months ago

NDMP backup failure 99

I recently got a failure for one of my client's backups. Here are the logs which were generated.

 Error ndmpagent (pid=7504) 10.244.152.156: DUMP: Error: File system full. Only level 0 full volume or level 0 .qtree dumps can run on a full file system.

30 Nov, 2023 8:30:16 PM - Error ndmpagent (pid=7504) 10.244.152.156: DUMP: Error: Free up disk space and inodes on the volume to be dumpedto run this dump or modify selected dump command.

30 Nov, 2023 8:30:16 PM - Error ndmpagent (pid=7504) 10.244.152.156: DUMP: Error: Dump failed to initialize.

30 Nov, 2023 8:30:16 PM - Error ndmpagent (pid=7504) 10.244.152.156: DUMP: Error: DUMP IS ABORTED

30 Nov, 2023 8:30:16 PM - Info ndmpagent (pid=7504) 10.244.152.156: DUMP: Deleting "/vserver_cifs/cifs1_2020/../snapshot_for_backup.241" snapshot.

30 Nov, 2023 8:30:16 PM - Error ndmpagent (pid=7504) 10.244.152.156: DATA: Operation terminated: EVENT: INTERNAL ERROR (for /vserver_cifs/cifs1_2020/)

30 Nov, 2023 8:30:18 PM - Error ndmpagent (pid=7504) NDMP backup failed, path = /vserver_cifs/cifs1_2020/

30 Nov, 2023 8:30:18 PM - Error bptm (pid=16192) none of the NDMP backups for client 10.244.152.156 completed successfully

Could you please help me out in finding the solution.

cruisen
Level 6
9 years ago
OK ,

I saw that veritas has published a technote in reference to this post:

https://www.veritas.com/support/en_US/article.000108612

Best regards,

Cruisen
Will_Restore
Level 6
9 years ago
Thanks cruisen. I presume you meant NetApp (not Netbackup).

panthony, any update on your end?
cruisen
Level 6
9 years ago
I got what Netbackup has to say.
Will_Restore
Level 6
9 years ago
I am curious too what NetApp says about that dumpdate. In the meantime, found this:

"Data ONTAP denotes time as a signed 32-bit integer that is interpreted as the number of seconds since 1 January 1970, 00 hours 00 minutes 00 seconds (GMT). This interpretation imposes an upper limit of 03 hours 14 minutes 07 seconds on 19 January 2038 (GMT)."

https://library.netapp.com/ecmdocs/ECMP1196889/html/GUID-35986F6A-45FD-4847-A0E1-06FDEDAE2152.html
cruisen
Level 6
9 years ago
Hello,

Is there any update on this ???

Best regards,

Cruisen
Marianne
Level 6
9 years ago
It is not an issue with retention.

Simply the date on which the dump is done.
panthony
Level 4
9 years ago
I've opened a case with NetApp and Veritas.

I know there is no chance that this is a NBU problem, but it's a big coincidence I think that for some dumps (initiated by the filer, right ?), the date equals the "infinite" retention.
Marianne
Level 6
9 years ago
Have you logged a call with NetApp about this?

You do understand that this is outside the control of NetBackup?
panthony
Level 4
9 years ago
Indeed, this not work...

My first incremental backup is OK, but it is post-dated too. So, my 2d incremental backup is NOK because the level 1 dump has a 2038 date.