181407:save: Step (1 of 5) for PID-8564: Save has been started on the client '********.com'. 174412:save: Step (2 of 5) for PID-8564: Running the backup on the client '********.com' for the save set 'pseudo_saveset'. 174424:save: Step (3 of 5) for PID-8564: Creating the snapshot for the selected save sets. VSS OTHER: ERROR: VSS failed to process snapshot: 90108:save: Unable to save the SYSTEM STATE save sets: cannot create the snapshot.
174918:save: Step (3 of 5) for PID-8564: Unable to complete the backup. See the savegrp log to track the closure steps of the backup. 175023:save: Unable to back up the save set 'pseudo_saveset'.
@rajinder.k, Looks like a VSS error. So check if all the writers are stable using `vssadmin list writers` and may be check the space on the C drive as well. Moreover some additional information like what is failing, any recent changes, if this is a new configuration also could help us help you
we have just removed the storage drives in client and added the drives with same drive letter from new storage. and then rebooted the server. after that scheduled backup failed with the same error
How dare you to ask for help if you are not willing to provide at least the most minimal information! - What else does it say than '... it does not work ...' ?
Could be a compatibility issue. Did it ever work before?
So let's start with the very basics - a manual backup. On the client, issue the command:
save -v [-s nw_server] [-b backup_pool] your_small_directory
crazyrov
6 Operator
•
1319 Posts
1730
0
Posted August 3rd, 2021 04:00
@rajinder.k, Looks like a VSS error. So check if all the writers are stable using `vssadmin list writers` and may be check the space on the C drive as well. Moreover some additional information like what is failing, any recent changes, if this is a new configuration also could help us help you