Wbadmin backup jobs fails at 30% cannot find the file specified

Hi all,

I'm having problem running a backup of my servers build in harddisk drive C: to an iscsi target

I use wbadmin to do the backup. Everything is going oké to up and around 30%

It the stops with the next message:

Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).

Backup stopped before completing.

Summary of backup:
------------------


Backup stopped before completing.
The system cannot find the file specified.

H:\>

the command start out okay

H:\>wbadmin start backup -backupTarget:h: -include:c: -allCritical -vssFull -quiet
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.

Retrieving volume information...

This would backup volume Local Disk(C:) to h:.

Backup to H: is starting.

Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Creating the shadow copy of volumes requested for backup.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running consistency check for application Exchange.
Running backup of volume Local Disk(C:), copied (0%).
Running backup of volume Local Disk(C:), copied (0%).
Running backup of volume Local Disk(C:), copied (0%).
Running backup of volume Local Disk(C:), copied (0%).
Running backup of volume Local Disk(C:), copied (0%).
Running backup of volume Local Disk(C:), copied (1%).
Running backup of volume Local Disk(C:), copied (1%).
Running backup of volume Local Disk(C:), copied (1%).
Running backup of volume Local Disk(C:), copied (1%).


Where can I found out why the backup is failing?


the h: drive is an iscsi target which I can read and write to using the server.
So normally Windows sees the h: drive as a local drive.

If however I do the wbadmin to g: (usb drive) all works fine and backup goes 100%
So, I was thinking it has something to do with the iscsi target??
LVL 1
osa2Asked:
Who is Participating?
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.

 
noxchoGlobal Support CoordinatorCommented:
If I were you I would just test the same backup to local drive or network share.
It could be you iSCSI problem but if you do not test it with internal drive or standard network share you never know.
0
 
osa2Author Commented:
I have tested it with a usb drive and then all works correct.

That is Why I suspect the Iscsi target to be the issue here.
But why? I can read / write the iscsi target without any problem.

I'm now thinking of deleting the catalog to see if this has anything to do with the catalog being corrput?
0
 
noxchoGlobal Support CoordinatorCommented:
My first thoughts were about the stability of your network connection. The fact that it starts writing and then fails point to this. Is this server using single NIC or more?
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
osa2Author Commented:
Launch an elevated command prompt. type the following at the commandline --

wbadmin delete catalog


.. this will clear the all the old backup data from the backup catalog.

Tried this it gets 4 times more
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
Running backup of volume Local Disk(C:), copied (30%).
and then displays the same error.

Backup stopped before completing.

Summary of backup:
------------------


Backup stopped before completing.
The system cannot find the file specified.
0
 
osa2Author Commented:
The backup server has only 1 nic.
The sbs server has 2 nics
0
 
noxchoGlobal Support CoordinatorCommented:
Why do I asked about NIC. Recently I met a problem where 2 NIC server was interrupting network writing operations. I found out that the API was trying to use both NICs at the same time but only one of them had NAS connected.
Try to disable one NIC and run backup. If it fails enable it and disable the other one. Try to backup.
0
 
osa2Author Commented:
I have not yet had the opportunity to do this with the client as I havn't got time to go to this clients.
I will update as soon as possible
0
 
osa2Author Commented:
Long time has gone by now.
And the issues has fixed itself kind of.

So, at the moment the issue is resolved.
0

Experts Exchange Solution brought to you by ConnectWise

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
 
osa2Author Commented:
it fixed itself. So no solutions from experts found
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.