Unsolved
This post is more than 5 years old
12 Posts
0
856
November 9th, 2010 04:00
Unable to backup certain drives on a Windows 2003 server
Hi
On the server I have set the backup saveset set to backup C:, D:, G:, H:.
Each time, C: and H: backup OK but for D: and G: fail. When I isolate the D: drive and run the backup it seems to be running through the data backup successfully but then stops unexpectedly. The job then sits there in a waiting to run state - as if it has never started - until it times out (hours later).
On the server the process info shows:
root 18163 25056 0 09:53:14 ? 0:00 /usr/sbin/savegrp -l full INET_adhoc
Any ideas what is going on?
Example output:
===============
NetWorker savegroup: (alert) INET_adhoc completed, Total 1 client(s), 1 Failed. Please see group completion details for more information.
Failed: dr-esx-pr
Start time: Mon Nov 8 16:15:35 2010
End time: Mon Nov 8 22:17:48 2010
--- Unsuccessful Save Sets ---
* dr-esx-pr:D:\ 2 retries attempted
* dr-esx-pr:G:\ 2 retries attempted
--- Successful Save Sets ---
* dr-esx-pr:Probe savefs dr-esx-pr: succeeded.
dr-esx-pr: C:\ level=full, 4677 MB 00:22:59 30816 files
dr-esx-pr: H:\ level=full, 25 KB 00:00:04 10 files
sbc-backup: index:dr-esx-pr level=full, 10 MB 00:02:08 161 files
Versions:
Server – Networker 7.6 on solaris 10 (sparc)
Client – Networker 7.5sp3 on Windows2003sp2 standard edition.
VSS off on all drives.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
November 9th, 2010 17:00
If you try to do backup from client side, does that work? At this point you may wish to run it with debug 3 to see where it breaks. Run such test twice and pay attention to following:
a) does it break at the same spot
b) does it break after same amount of time
Based on above you will have hints where to look further.
escott123
12 Posts
0
November 11th, 2010 06:00
Apologies for delay in getting back to this. (In part this is because these D and G drives backup over a slow link and take over 24 hours to run).
I ran the backup from the client end using the save command. This worked for both drives.
So, next thing is to run the backup again from the server using debug level 3.
I'll run the savegrp command again as savegrp -vvv ....
(If this is not what you mean by debug level 3, let me know).
Regards
Ewan
masonb
445 Posts
0
November 11th, 2010 06:00
That is running command with extra verbosity, savegrp -D 3 (usual other flags also) will instigate debug messaging which is different.
Regards,
Bill Mason
wlee
263 Posts
0
November 11th, 2010 19:00
How big is the drives thatg fail? If they are large, then the time needed may be an important symptom.
The server is running solaris 10. Did you disable tcp fusion?
Your description of savegroup stalling sounds similar to existing known issues with savegroup. Try installing the latest cumulative builds.
Is your server running 7.6.0? The 7.6.0.9 install kits can be found at:
ftp://ftp.legato.com/pub/NetWorker/Cumulative_Hotfixes/7.6/
If you are running 7.6.1, the next cumulative build (7.6.1.1) will be released in a few days, so watch for that, and then upgrade and see if that helps.
If after all that, savegroup still stalls, then you may need to run a truss against the savegroup to see what it is doing. Then open a tech support case to get it analyzed.
Also check for core files in /nsr/cores/*
escott123
12 Posts
0
November 18th, 2010 06:00
Update:
I am now running an adhoc backup of the G: drive at debug level 3. My first attempt at this led to a successful completion so I'm running it again to see if I can capture the error.
Ewan
savegrp -vvv -D3 -l full INET_ESX_PROXY_adhoc