Issue with Backup Exec and Terastation
Hi there, having a few issues at work and hope you can shed some light on this,
Currently we have a Server 2003 machine running Veritas Backup Exec 9.1 which a backup to disk on a Buffalo Terastation. All of a sudden last month, the b2d folders all went "offline" and the backups to the terastation fail.
Ive been reading up on the issue and many of the suggestions seem to be to reintegrate AD permissions on the terastation. Firstly the terastation says it is on a workgroup in the web interface, and it always has been, and secondly ive tried to add permissions to the terastation shares via windows but it is unable to look anywhere other than on itself (presumably because its on a workgroup?)
The other suggestion is to create a local account in backup exec and give it the same username and pwd as the terastation, which i have, but this doesnt work.
The errors i get when i try to create a fresh backup to disk to the terastation is "access denied"
Anyone come across this before? Cheers
Currently we have a Server 2003 machine running Veritas Backup Exec 9.1 which a backup to disk on a Buffalo Terastation. All of a sudden last month, the b2d folders all went "offline" and the backups to the terastation fail.
Ive been reading up on the issue and many of the suggestions seem to be to reintegrate AD permissions on the terastation. Firstly the terastation says it is on a workgroup in the web interface, and it always has been, and secondly ive tried to add permissions to the terastation shares via windows but it is unable to look anywhere other than on itself (presumably because its on a workgroup?)
The other suggestion is to create a local account in backup exec and give it the same username and pwd as the terastation, which i have, but this doesnt work.
The errors i get when i try to create a fresh backup to disk to the terastation is "access denied"
Anyone come across this before? Cheers
Comments
-
Slowhand Mod Posts: 5,161 ModIntegrating the Terastation into AD is the ideal solution, but if I remember correctly, you can still access it when it's part of a workgroup so long as the permissions are set properly in the GUI. You need to make sure all users can access it, and if I'm not completely senile, there's an "all users" or "guest" type of account you can grant permission to through that GUI. If things worked before, but now they don't, that guest/anonymous access may have been reset.
Free Microsoft Training: Microsoft Learn
Free PowerShell Resources: Top PowerShell Blogs
Free DevOps/Azure Resources: Visual Studio Dev Essentials
Let it never be said that I didn't do the very least I could do. -
kctxau Member Posts: 130You may be able to get more help/ideas here on Symantec BE 9.1 forum.
https://forums.symantec.com/syment/board?board.id=101