Problem using SNAP server as Backup-To-Disk folder

[cabraun]

Hi all, I am having a problem using a share on a SNAP server as a Backup-To-Disk folder.

This was working OK under BE 8.6, but we recently upgraded to 9.1 and now when my job kicks off (A Monthly full-backup job) it will go into queued status for 30Sec to 1Min and then fail with access-denied.

The funny thing is, if I then rename the folder on the SNAP and then delete and recreate the B2D folder in Backup Exec (No changes to permissions or anything) and then restart the job, it will run perfectly. Only once though. Next month when the job is scheduled to run again, it will fail the first time with access denied and I will go through the process again of renaming, deleting and recreating. Then the job will run once again until the next month or if a restore needs to be done.

So basically, my fix only works once per job. I am looking for something a little more permanent. Anyone have any suggestions?

 

[Qdog]

Only type of backup-to-disk folder location recommended by Veritas is a Windows Powered OS with either FAT, FAT32 or NTFS. (NTFS recommended). Otherwise, there is a good chance the .bkf file will be corrupt when you go to restore your data. According to them, the problem lies in the difference in filesystems when the backup to disk folder is on a Unix/Linux filesystem....their backup to disk functions are just not supported on them.

Hope this helps.