Network drive - Backup keeps cancelling

Hi,

 

You might need to look at importing the B2D as a legacy folder...see the below:

http://www.symantec.com/docs/HOWTO74274

Thanks!

For BE 2012, all B2D folders will be treated as Legacy B2D Folders and these are read-only. If you want to continue backing up to your share, you would have to go to the Storage tab and define a disk storage on that share. The old B2D folder can be used for restores

If the folder is online but the icon for the folder shows a pencil with a red strike through it, then it is in Read Only mode. (In other words online for restores)

 

The properties of the drive will show a similar setting that can be changed back to Read write

 

BE 2012 does not allow multiple Disk storage devices on the same volume (12.5 dis) as such both during an upgrade and ongoing will put a number of disk storage devices into the Read Only mode if it finds a violation of this requuirment.

 

EDIT: We also put device into Read Only if they have been offline from the media server for too long (default 14 days) reason for this is that sometimes customers will vault USB disks and eventually bring them back for a one off restore. However if DLM reclaim starts against expired media, the sets you need to restore from might get deleted before you can restore unless we marked the drive as Read Only to give you chance to restore from a really old set.

I decided to start again from scratch with the network storage and thats where I found what the problem was. It seems there is something wrong with the permissions of the folder. I wanted to delete all the data but wasn't able to from Windows. I logged on to the Linux server hosting the folder and I can't even delete the data or folder from their either.

I created a new folder and also a new network drive in BE. The backup started and was able to access the folder but it created over 100 4mb .bkf files?? and then the job failed with:

The job failed with the following error: A failure occurred accessing the Writer metadata.

I looked at the job log and it says that the remote agent is running a previous version?? The only reason I can think this has happened is that the agent was installed prior to the SP and hotfix. I'll update it and try again.

...that error message could also refer to the VSS writers, so after running th eagent upgrade, open a command prompt and type: vssadmin list writers, and make sure all the writers are running and stable.

Thanks!