The error indicates a possible issue with VSS or disk connectivity. First, ensure that the disk or device mentioned is accessible and exists. Then, check the VSS writer status on the Windows 2022 server using vssadmin list writers and restart any failed services. Finally, update Veeam agents and drivers to the latest version to avoid compatibility issues.

Is this a new job or an existing one that has already been successfully completed?

Is this the same server as in your other post?https://community.veeam.com/vug-usa-63/windows-agent-backup-error-vss-0x80042306-8958?postid=69868#post69868

Are you managing the backup from the agent or VBR server?  Also what type of backup are you doing full, drive level, etc?  Need a bit more information but check the VSS writers as noted and ensure the agent is current.

Verify that the VSS writers are working correctly open a command prompt on the file server and run the following command to check the VSS writers.

vssadmin list writers

If any writers are in a failed stat  you might need to restart the VSS service.

vssadmin list writers run this command is not error status

yes managed agent,and type is drive level

run this command result is not error

no last post is great than 64tb of server ,and issue show is not same

At this point I would suggest a support ticket to get further assistance.

thanks respone,I have open ticket!

but free ver can use ticket?

Yes but it will be best effort support.

How long does it take to open a ticket and start responding?

Again opening a ticket is fairly easy but you will need to wait on response it is not instant!

Thanks for the response but it's been a week since I opened it last month.

That is how best effort works with the free edition unfortunately.

OK

I see

thanks

@mike.chen thank you to confirmed let's go with these steps.

Possible Solutions below.

Verify Disk Existence:

Check if the disk (with ID 95cb709e-eaa2-4f35-9c97-c0e73e353753) is still present in the environment. Ensure it’s properly attached to the virtual machine or system that requires it.

Check Disk Configuration:

If this is a cloud-based virtual machine, verify the disk configuration settings. Make sure the disk is correctly mapped and has the necessary access permissions.

Restart Services:

Try restarting the relevant agent or service managing disk transfers. This might resolve connectivity or protocol-related issues.

Check Network/Connectivity:

Ensure that there are no network or connectivity issues that could be causing the "reconnectable protocol device" error.

Reattach the Disk:
If the disk is not found or the connection was lost, try reattaching the disk or recreating it if necessary.

following these steps might be helpful for you.

thanks your respoen!

But my file server is not vm!

thank you for confirming let me share my experience with you and how my FS is working in the below scenario.

VM Base:

My FS is hosted on GCP and has more than 40 TB size I have created a separate standalone backup job for FS and I have assigned a dedicated repo for FS backup in that case it is working fine with me.

VAW Base:

I have installed agent on FS through VBR and I have added FS in protection group after that I have add the protection group into production backup job while selecting the backup mode file level backup then i have chose objects to backup operating system and the following file system objects.

thank you for confirming let me share my experience with you and how my FS is working in the below scenario.

VM Base:

 

My FS is hosted on GCP and has more than 40 TB size I have created a separate standalone backup job for FS and I have assigned a dedicated repo for FS backup in that case it is working fine with me.

 

VAW Base:

 

I have installed agent on FS through VBR and I have added FS in protection group after that I have add the protection group into production backup job while selecting the backup mode file level backup then i have chose objects to backup operating system and the following file system objects.

 

 

I use volume level backup

thank you for confirming let me share my experience with you and how my FS is working in the below scenario.

VM Base:

 

My FS is hosted on GCP and has more than 40 TB size I have created a separate standalone backup job for FS and I have assigned a dedicated repo for FS backup in that case it is working fine with me.

 

VAW Base:

 

I have installed agent on FS through VBR and I have added FS in protection group after that I have add the protection group into production backup job while selecting the backup mode file level backup then i have chose objects to backup operating system and the following file system objects.

 

 

I use volume level backup

here you go backup the following volume only select os volume then click on add object enter the volume name example below and try if you face any issue share screenshot we can see if not works i explain above please try with that procedure.

in my current environment i m securing backup like that and i have multiple scenarios in my production environment.

thank you for confirming let me share my experience with you and how my FS is working in the below scenario.

VM Base:

 

My FS is hosted on GCP and has more than 40 TB size I have created a separate standalone backup job for FS and I have assigned a dedicated repo for FS backup in that case it is working fine with me.

 

VAW Base:

 

I have installed agent on FS through VBR and I have added FS in protection group after that I have add the protection group into production backup job while selecting the backup mode file level backup then i have chose objects to backup operating system and the following file system objects.

 

 

I use volume level backup

here you go backup the following volume only select os volume then click on add object enter the volume name example below and try if you face any issue share screenshot we can see if not works i explain above please try with that procedure.

 

in my current environment i m securing backup like that and i have multiple scenarios in my production environment.

 

 

as you same