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.

 
Mr.XAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rich MCommented:
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.
0
Mr.XAuthor Commented:
Hi, thanks for the reply.
Sorry I did not get it. What do you mean by probing for 4gb ?
0
Rich MCommented:
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.
0
Acronis True Image 2019 just released!

Create a reliable backup. Make sure you always have dependable copies of your data so you can restore your entire system or individual files.

Mr.XAuthor Commented:
hi, actually it does not fail everyday. it just fails randomly.
i got one of the success screenshot. and it seems to be the probing for 4gb worked. so i think nas should be supporting this 4gb file support
shadow.PNG
0
Rich MCommented:
Well that certainly makes it more confusing.. Hopefully someone has more direct knowledge of Shadow Protect. Sorry I couldn't offer more.
0
R@f@r P@NC3RVirtualization SpecialistCommented:
Hello

Error 503:
This error occurs when the system has reported a communication problem when trying to read information from the unit being copied, or when trying to write data to the unit where the backup is being saved.

Please validate the unit where you are presenting the problem with the CHKDSK / R or CHKDSK / B command, to validate and verify that the unit has no problems.

Do you have the necessary permissions to run the backup on this unit?

You can also create another test unit and validate if you do the backup.

Error 504:

Indicates communication problem, your backup device does not detect the server or the unit you want to backup.

Error 516:

The backup process starts but fails. Is it a physical or virtual server? Are you making a full backup? or by individual discs?

If it is a virtual server, you can move it to another host and try the backup task again.

Or they also try to change the backup configuration on the server.

So you mention that unit D sometimes fails in the backup but not all the time.

I remain attentive to your comments.

regards..
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mr.XAuthor Commented:
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
0
R@f@r P@NC3RVirtualization SpecialistCommented:
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
0
Mr.XAuthor Commented:
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.
0
R@f@r P@NC3RVirtualization SpecialistCommented:
Ok very well, leave the unit d in monitoring until tomotrow and notify me please

Regards
0
R@f@r P@NC3RVirtualization SpecialistCommented:
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...
0
Mr.XAuthor Commented:
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.
0
R@f@r P@NC3RVirtualization SpecialistCommented:
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...
0
Mr.XAuthor Commented:
Yea sure. Will run tonight and will let you know the results tomorrow morning again.
Thanks for following up this post
0
R@f@r P@NC3RVirtualization SpecialistCommented:
in mind, do not worry, do not hesitate to contact me if you have any questions

best regards.
0
Mr.XAuthor Commented:
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.
0
R@f@r P@NC3RVirtualization SpecialistCommented:
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..
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Software

From novice to tech pro — start learning today.