Unsolved
This post is more than 5 years old
5 Posts
0
559
NMM backup remain in queued state in windows 2003
Hi All,
We are facing issue with NMM(2.4) backup on windows 2003. The backup remain in queue state and it shows in NMC gui as Currently running, but it never write backup data and after running hours it fails.
We have checked removing NMM and backup runs fine with traditional method. As the system having share-point application we want to configure backup using NMM.
The vssadmin list writers does not show errors.
This server network configured using teaming and we could see that when we ping hostname it is resolving to IPV6 address even though the IPV6 is disabled from registry.
>ping xyz
Pinging xyz..com [fe80::1%1] from fe80::1%1 with 32 bytes of data
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Reply from fe80::1%1: time<1ms
Outside from xyz host ip is resolving to IPV4. We checked from backup server and it is resolving to IPV4 ip address.
christopher_ime
2K Posts
0
January 3rd, 2014 20:00
Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "NetWorker Support Forum".
NetWorker Support Forum
ble1
2 Intern
2 Intern
•
14.3K Posts
0
January 5th, 2014 08:00
Is it 2.4 or 2.4SP1? What does nmm.raw say? During what kind of backup does this happen?
ble1
2 Intern
2 Intern
•
14.3K Posts
0
January 5th, 2014 09:00
Disable IPv6 from TCP properties and see if that works. I'm not sure if NMM 2.4 works with IPv6 at all. Most likely not (and most likely you wish to explore possibility to update to 2.4SP1).
subhash_kv
5 Posts
0
January 5th, 2014 09:00
Hi Hrvoje,
The NMM version is 2.4.0.375. The nmm.raw does not give clear details about error. The backup is hanging during filesystem backup and sharepoint application backup both. When we remove NMM the filesystem backup runs fine with traditional method(without snap). We have open a case on this issue with support team and still waiting for solution.
I suspect the IPV6 might be causing issue but not sure as the traditional backup runs fine.