12-21-2015 04:25 AM
Solved! Go to Solution.
12-22-2015 06:47 AM
Just for reference it appears that because Shadow Copy Components is not available against the actual cluster that the correct way to backup clustered DFSR is via the active node
http://www.veritas.com/docs/000023896
This of course does mean tifthe cluster fails over then that job will fail and you will need a different job (perhaps kept on hold) for when the other node is active.
If you go down the route of disabling Active File Exclusion be aware that:
- the backup jobs could try to backup files that do not need backing up (Swap files etc), which will cause a larger overall byte count and a longer job.
- It may also attempt to backup open files that are locked by application in a way that the open file technology cannot get round, which will result in lots of skipped files being reported and a generally slower backup
- for some databases technologies the VSS request against the file system might interrupt log sequence numbers and therefore cause issues for your database agent backups
12-21-2015 04:47 AM
Afaik, backing up via the nodes is the only option.
What problem does he encounter once the disk switches ?
12-21-2015 05:39 AM
Let's say he prefers to use the old backup through Clustername he used to perform safely.
I am going to redirect him here.
12-22-2015 06:17 AM
How to disable the Active File Exclusion feature in Backup Exec
We will check whether this regkey is still valid for BE15.
12-22-2015 06:29 AM
12-22-2015 06:47 AM
Just for reference it appears that because Shadow Copy Components is not available against the actual cluster that the correct way to backup clustered DFSR is via the active node
http://www.veritas.com/docs/000023896
This of course does mean tifthe cluster fails over then that job will fail and you will need a different job (perhaps kept on hold) for when the other node is active.
If you go down the route of disabling Active File Exclusion be aware that:
- the backup jobs could try to backup files that do not need backing up (Swap files etc), which will cause a larger overall byte count and a longer job.
- It may also attempt to backup open files that are locked by application in a way that the open file technology cannot get round, which will result in lots of skipped files being reported and a generally slower backup
- for some databases technologies the VSS request against the file system might interrupt log sequence numbers and therefore cause issues for your database agent backups