Video Screencast Help

backing up data from migrated fileserver

Created: 15 Apr 2013 • Updated: 17 Apr 2013 | 2 comments
This issue has been solved. See solution.


We have just sunset our old fileserver and replaced it with a new fileserver/SAN storage. We kept the name of the old file server to avoid certain issues.

It seems that BE2012 is backing up and restoring to the new fileserver correctly but we did notice that some volumes/shares were still displaying in the job definition and they were failing the credential test?

Ideally we would want to remove and add the server back into BE but we would loose all the job definitions/job history so we would like to clean it up if this possible?

Would this be an issue as far as BE is concerned? At the moment everything seems to be working.

How could we clean up the server details listed in BE to just see the new shares.

thanks in advance

ps Our old fileserver was a clustered virtual server connected to the old SAN and the new server is a Hyper-V VM connected to the new SAN.

Operating Systems:

Comments 2 CommentsJump to latest comment

Colin Weaver's picture

If you edit the selection list then there should be two tabs, one tab shows you the graphical way to make the selection (but will ONLY show resources that still exist)

The other tab shows you the text based view of what you actually have selected and does show resources that no longer exist. You can highlight the invalid entries and use the delet option.

DSAI's picture

thanks for the response...We are still having appears the remote agent is not working since the name change.

I've opened up a case with Symantec Tech Support and they are helping me.