osa2
asked on
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??
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??
ASKER
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?
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?
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?
ASKER
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.
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.
ASKER
The backup server has only 1 nic.
The sbs server has 2 nics
The sbs server has 2 nics
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.
Try to disable one NIC and run backup. If it fails enable it and disable the other one. Try to backup.
ASKER
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
I will update as soon as possible
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
it fixed itself. So no solutions from experts found
It could be you iSCSI problem but if you do not test it with internal drive or standard network share you never know.