5 Practitioner
•
274.2K Posts
0
4308
NDMP backup of Unity file system is timed out after 24 hours of run
Hi everyone,
I'm having the following issue with backing up EMC Unity 600 file system via NDMP.
Because of a file system being pretty large (~60TB), backup does not end within 24 hours which is fine for the first full backup and I had no issues with VMAX when first backup was running up to 48 hours. Here, with Unity 600, backup is canceled on NAS side after exactly 24 hours of running.
Here is the part of an Avamar log related:
On the Unity side I can't find anything more detailed then this:
You can see that NDMP snapshot was created and then destroyed after exactly 24 hours but I have no clue why it happens and that's where I need your help, guys.
Avamar version used - 7.5.1-101
NDMP version - AvamarNDMP-7.5.101-101.x86_64
NDMP was enabled on Unity via web UI by setting the check-mark "NDMP" for the particular NAS. That's it. No settings like snapTimeout can be performed for Unity systems, as per NDMP user guide.
umichklewis
1.2K Posts
0
July 11th, 2018 13:00
Sure - you can do this multiple ways. My preferred method is to set the NDMP client to "Always allow overtime". Here is my backup policy for an old EMC Celerra NS40:
In the above output, I went into the Avamar console, selected the NDMP client, then clicked "Edit". I can set each NDMP client to always allow overtime this way.
Let us know if that helps!
Karl
umichklewis
1.2K Posts
0
July 11th, 2018 07:00
Do you have the client backup set to "always allow overtime"?
You might also want to ask this question in the Unity forums, since this will probably need to be addressed with NDMP settings on the filer. Most likely, there's a way in the CLI to make the necessary change. If it's not readily apparent, you'll need to open an SR with EMC to investigate.
Let us know if that helps!
Karl
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
July 11th, 2018 08:00
Karl, I don't recall such setting "always allow overtime". Could you point where it is?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
August 8th, 2018 05:00
Sorry for delay. Karl, your tip was helpful and I was able to avoid 24-hrs timeout.
Now facing another issue when after approximately 5 days, backup session is still active but nothing is actually being copied to DD. So, trying to understand at what end it brakes: NDMP accelerator, DD, Unity.
Logs on NDMP accelerator:
2018-08-08 07:01:17 avndmp Error <11894>: [snapup-/Jira-Filessystem] Send message failed call for 400.
2018-08-08 07:01:17 avndmp Error <11893>: [snapup-/Jira-Filessystem] ndmp socket write, trying to write 4000 bytes, send returned error 32: code 32: Broken pipe
Session log on Avamar side:
2018-08-08 06:28:25 avtar Warning <6568>:Internal Warning: Very large number of entries on TODO queue (139508)
2018-08-08 06:43:14 avtar Info <41437>: Executing a flush (fsync) to keep write stream alive for file "avamar-1521563896/container.1.cdsf" with file handle 1812451331
2018-08-08 06:43:25 avtar Info <8688>: Status 2018-08-08 06:43:25, 11,456,912 files, 1,829,445 directories, 50,861 GB (11,456,912 files, 1.441 GB, 49.00% new) 3227MB 0% CPU (1 open files)
umichklewis
1.2K Posts
0
August 28th, 2018 08:00
This will definitely need an SR, if you don't already have one. There's a chance the snapshot could be expired or the NDMP session could be expiring. Support will certainly be able to point you in the right direction.
Let us know how it turns out!
Karl
TechMcGee
1 Message
0
September 25th, 2020 06:00
Hi @Anonymous,
Did you ever find the resolution to this? We are experiencing the same exact thing with out backups just looking like they aren't writing anything and stuck on an open file, etc.
123kateb
1 Rookie
1 Rookie
•
45 Posts
0
October 1st, 2020 07:00
@TechMcGee