Mr.X
asked on
server 2012 R2 - shadow protect failure
Got a server 2012 R2, shadow protect installed for backup . backups going to nas drive. backing up the whole server.
server has few drives. like ",c,d,e,f,g" . all drive successfully backing up. but "d" alone fails few times in a week.
not sure why it is failing. i went through shadow protect, found its failing with "503 fatal i/o error"
i just attached a screenshot for more info.
could anyone help with this issue.
server has few drives. like ",c,d,e,f,g" . all drive successfully backing up. but "d" alone fails few times in a week.
not sure why it is failing. i went through shadow protect, found its failing with "503 fatal i/o error"
i just attached a screenshot for more info.
could anyone help with this issue.
The problem seems to occur after probing for 4GB file support. Can this NAS support that? Could be it is failing on the fulls, where the smaller incremental's would work.
ASKER
Hi, thanks for the reply.
Sorry I did not get it. What do you mean by probing for 4gb ?
Sorry I did not get it. What do you mean by probing for 4gb ?
About half way down in your log file the activity is "probing the target media for > 4GB file support". It could be that the target media (NAS partition) does not support > 4GB files and then potentially causing the failure.
ASKER
Well that certainly makes it more confusing.. Hopefully someone has more direct knowledge of Shadow Protect. Sorry I couldn't offer more.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi ,
I will try running the chkdsk on the "d" on server. That's where the problem is
Permissions are good. Because it works with other drives on the same server. And even "d" works few days and fails few days too
It's a virtual server. Got hyper v. And I don't think I can change to another host. As I got just one hyper v
Ya finally, I will try these things and will let you know.
1. Will do chkdsk
2. Will create test unit
I will try running the chkdsk on the "d" on server. That's where the problem is
Permissions are good. Because it works with other drives on the same server. And even "d" works few days and fails few days too
It's a virtual server. Got hyper v. And I don't think I can change to another host. As I got just one hyper v
Ya finally, I will try these things and will let you know.
1. Will do chkdsk
2. Will create test unit
Hello very well, perform the tests and tell me the results.
You can also perform a test vm, which is similar to the server you are backing, such as the number of disks and drives and test the backup with a different configuration to see if it works.
In the same way, validate the unit that is presenting problems and notify me.
regards
You can also perform a test vm, which is similar to the server you are backing, such as the number of disks and drives and test the backup with a different configuration to see if it works.
In the same way, validate the unit that is presenting problems and notify me.
regards
ASKER
Hi,
I did not run chkdsk.
I just disabled the normal full backup. Made another test backup just to back up the "d" drive alone and it finished successfully without any issues.
Am not sure what to do next. Don't know is it just another lucky day. Because Usually "d" sometimes succeeds as well as I told before.
I did not run chkdsk.
I just disabled the normal full backup. Made another test backup just to back up the "d" drive alone and it finished successfully without any issues.
Am not sure what to do next. Don't know is it just another lucky day. Because Usually "d" sometimes succeeds as well as I told before.
Ok very well, leave the unit d in monitoring until tomotrow and notify me please
Regards
Regards
Hello
everything is due to a communication problem between your backup tool and the server, but you indicate that it fails sometimes and sometimes it does not, I also recommend that you talk with the network staff, and that they can validate your part to see if it exists some failure at the network level.
That usually happens a lot with the backup tools.
Regards...
everything is due to a communication problem between your backup tool and the server, but you indicate that it fails sometimes and sometimes it does not, I also recommend that you talk with the network staff, and that they can validate your part to see if it exists some failure at the network level.
That usually happens a lot with the backup tools.
Regards...
ASKER
Again, if it's some network issue. Why it's always the "d" alone failing. All other drives in same server backing upto same destination succeeds all time. It's just " d" drive
Last night, I disabled the backup and made a seperate backup just for "d" drive, it succeeded
I planned to do 2 jobs tonight. 1- just "d" alone as last night and second job- remove "d" drive from usual backup job, so it runs all others drives as usual.
Just wanted to see, if I make it as 2 seperate jobs, what will happen.
Last night, I disabled the backup and made a seperate backup just for "d" drive, it succeeded
I planned to do 2 jobs tonight. 1- just "d" alone as last night and second job- remove "d" drive from usual backup job, so it runs all others drives as usual.
Just wanted to see, if I make it as 2 seperate jobs, what will happen.
Hello
There is no problem with what you indicate. Then proceed with the following:
1- Configure a backup with all the units, the "D" unit does not configure it.
2- Configure another backup only with unit D.
3-You can also free space and defragment drive D and make a backup as you have been running to validate if it works without problems.
Any of the three options are valid, perform the tests and notify the results.
Regards...
There is no problem with what you indicate. Then proceed with the following:
1- Configure a backup with all the units, the "D" unit does not configure it.
2- Configure another backup only with unit D.
3-You can also free space and defragment drive D and make a backup as you have been running to validate if it works without problems.
Any of the three options are valid, perform the tests and notify the results.
Regards...
ASKER
Yea sure. Will run tonight and will let you know the results tomorrow morning again.
Thanks for following up this post
Thanks for following up this post
in mind, do not worry, do not hesitate to contact me if you have any questions
best regards.
best regards.
ASKER
Hi,
As I told yesterday, I ran 2 backup jobs. One for just "d"drive and another for all other drives.
Both backup jobs succeeded last night.
So I can't figure out why "d" drive alone failing if all drive runs in same backup job. But still will monitor for few more days. If It did not fail. Can say it for sure the problem is running all drives in single backup.
As I told yesterday, I ran 2 backup jobs. One for just "d"drive and another for all other drives.
Both backup jobs succeeded last night.
So I can't figure out why "d" drive alone failing if all drive runs in same backup job. But still will monitor for few more days. If It did not fail. Can say it for sure the problem is running all drives in single backup.
hello, the backups were executed successfully, it's that good.
We will monitor them for two more days to see their behavior and let me know the results.
In the same way, I recommend you to talk with the network staff and make the respective revisions of your layer. because it is a communication problem.
let me know the results.
regards..
We will monitor them for two more days to see their behavior and let me know the results.
In the same way, I recommend you to talk with the network staff and make the respective revisions of your layer. because it is a communication problem.
let me know the results.
regards..