Your error messages are a combination of 2 issues. One is wrong directive syntax and the second xdr issue. First issue can be resolved with Tim's suggestion the xdr is disk related, please check if you are running multiple save for the same saveset.
If client is a windows server, please run "vssadmin list writers" command on client and see if all writers are stable and there is no error.
The error message posted by you is not enough to understand the issue. You can try to run backup of small folder/file from client using CMD, if it fails you will get error message.
What is the client OS ? As I said earlier, error message posted by you is not enough. Please either run a small backup from CMD or run backup with client retry 0.
You have posted VSS error - hr = 0x800706ba, The RPC server is unavailable.
This error occurs when there is ports issue between client and server or vss writers are unstable.
Since you have checked that VSS writers are stable, it could be ports issue and to find out why this port issue is occurring, we need more clear error message.
There should not be much difference its basically the same except that you are triggering the group manually. Something much have changed other than this. Are the scheduled jobs still failing ?
Mandri
91 Posts
0
December 23rd, 2013 01:00
I use the following directive:
< >
+skip: *.iso
< >
+skip: *.iso
It looks like in this case.
TimQuan
4 Operator
•
1.2K Posts
0
December 25th, 2013 17:00
please try:
<< "E:" >>
+skip: *.iso
<< "F:" >>
+skip: *.iso
I suggest copying above to your directory.
crazyrov
4 Operator
•
1.3K Posts
0
December 25th, 2013 19:00
Your error messages are a combination of 2 issues. One is wrong directive syntax and the second xdr issue. First issue can be resolved with Tim's suggestion the xdr is disk related, please check if you are running multiple save for the same saveset.
--- Original Message ---
crazyrov
4 Operator
•
1.3K Posts
0
January 22nd, 2014 07:00
Mandri,
Can you reduce the client retries on the affected group from 1 to 0 so that we have a clearer error to work with.
pawankumawat
355 Posts
0
January 22nd, 2014 07:00
Hello,
If client is a windows server, please run "vssadmin list writers" command on client and see if all writers are stable and there is no error.
The error message posted by you is not enough to understand the issue. You can try to run backup of small folder/file from client using CMD, if it fails you will get error message.
Regards,
Pawan
Mandri
91 Posts
0
January 22nd, 2014 07:00
Good afternoon.
On the file server periodically such errors.(starts incremental backup)
This is the problem with the server or the client, or with NTFS or VSS?
NetWorker savegroup: (alert) File Server Backup completed, Total 1 client(s), 1 Failed. See group completion details for more information.
Failed: server1.local
Start time: Tue Jan 21 21:00:00 2014
End time: Tue Jan 21 21:03:38 2014
--- Unsuccessful Save Sets ---
server1.local:E:\R: retried 1 times.
server1.local:F:\R\BackupUser: retried 1 times.
--- Successful Save Sets ---
* server1.local:savefs 76677:savefs: RPC receive operation failed; errno = Unknown error * server1.local:savefs 76677:savefs: RPC send operation failed; errno = Unknown error * server1.local:savefs 76677:savefs: RPC send operation failed; errno = Unknown error * server1.local:savefs 76677:savefs: RPC send operation failed; errno = Unknown error * server1.local:savefs 76677:savefs: RPC send operation failed; errno = Unknown error * server1.local:savefs 76677:savefs: RPC send operation failed; errno = Unknown error * server1.local:savefs 76677:savefs: RPC send operation failed; errno = Unknown error * server1.local:savefs savefs server1.local: succeeded. * server1.local:index 86705:save: Successfully established DFA session with adv_file device for save-set ID '1893647456' (serverNetWork.local:index:48f6f4ae-00000004-527b919f-527b919e-00022500-5665c090). serverNetWork.local: index:server1.local level=9, 1781 MB 00:00:42 41 files * server1.local:index completed savetime=1390330976
On the server there is nothing except the VSS error:
Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface. hr = 0x800706ba, The RPC server is unavailable.
. This is often caused by incorrect security settings in either the writer or requestor process.
bingo.1
2.4K Posts
1
January 22nd, 2014 07:00
As this could potentially become an endless thread, let me suggest ...
- you start a new one
- you at least specify the OS type and version
- the NW version
Believe me - this would improve the feedback ;-)
In general, let me suggest you look at the network components and settings. NetWorker must rely on
- a unique name resolution
- UPD and TCP connections
- RPC support (obviously this does not work here, so the NW server cannot even save its own data)
It looks like a local backup on the NW Windows (?) server using at least NW 8.0. But this is just my personal guess.
pawankumawat
355 Posts
0
January 22nd, 2014 08:00
Hello,
What is the client OS ? As I said earlier, error message posted by you is not enough. Please either run a small backup from CMD or run backup with client retry 0.
You have posted VSS error - hr = 0x800706ba, The RPC server is unavailable.
This error occurs when there is ports issue between client and server or vss writers are unstable.
Since you have checked that VSS writers are stable, it could be ports issue and to find out why this port issue is occurring, we need more clear error message.
Regards,
Pawan
Mandri
91 Posts
0
January 22nd, 2014 08:00
I set retry to 0 and wait for automatic start today at 9PM.
Mandri
91 Posts
0
January 22nd, 2014 08:00
Sorry, here are the technical details:
The server and client versions of the NW 8.1.1.
Server version 2012R2, 2008R2.
For client and Server TCP settings: http://nsrvalley.com/2012/03/19/rpc-error-rpc-send-operation-failed-errno-an-existing-connection-was-forcibly-closed-by-the-remote-host-74209save-quit-signal-received/produced
Forgot to say, the client has NTFS errors, but they do not exist at the time of launch of the process of archiving.
crazyrov
4 Operator
•
1.3K Posts
0
January 22nd, 2014 08:00
Mandri, can you please run the backup again with retry set to 0. This would provide us the error and then we can point you to the right direction.
Mandri
91 Posts
0
January 22nd, 2014 08:00
vssadmin list writers show all: No error
Mandri
91 Posts
0
January 22nd, 2014 11:00
This error was Exited with exit code:: Unknown, completion severity: INFORMATION (10) exited unexpectedly status: completion (2)
Mandri
91 Posts
0
January 22nd, 2014 13:00
Launched in manual mode - all work, no errors.
Can someone explain what this is and why is it so?
crazyrov
4 Operator
•
1.3K Posts
0
January 23rd, 2014 00:00
There should not be much difference its basically the same except that you are triggering the group manually. Something much have changed other than this. Are the scheduled jobs still failing ?