05-27-2015 10:27 AM
Hello,
We have a server that is constantly having orphan files when the backups run.
I’m assuming it’s because of the snapshots.
This server contains a lot of data and has 4 drives. Server has 8GB of ram.
C:\ 60GB
D:\ 2TB
F:\ 2TB
G:\ 20GB (12GB Swap file)
I made sure there was an exclusion in MacAfee for the D:\ and F:\ drive.
Are there any best practices for servers that fall in this category?
Has anyone experience this issue?
Does anyone have advice on how I should change the backup job?
Thank you,
Solved! Go to Solution.
05-29-2015 04:53 PM
Okay. So this is VMware backups.
You will agree that there was no indication whatsoever in your opening post?
Please tell us more about the environment.
What rights have been given to the user account in the VMware credentials?
See this TN:
What are the minimum permissions needed to properly backup and restore using vStorage api?
http://www.symantec.com/docs/TECH130493
05-29-2015 01:50 AM
Please tell us what you consider to be 'orphan files'?
Give us examples?
NBU 7.6 on Windows uses Microsoft VSS for snapshots.
Snapshot activity can be seen in Windows Event Viewer logs and in NBU bpfis log.
Any files created by the snapshot should be logged in bpfis.
We can probably offer better advice if we have a better understanding of these 'orphan files'.
The last time I saw issues with left-over snapshot files was in older NBU versions with VSP (Veritas Snapshot Provider).
05-29-2015 01:39 PM
Hi Marianne,
Below is a screenshot of the orphaned VMDK files. Thanks
05-29-2015 04:53 PM
Okay. So this is VMware backups.
You will agree that there was no indication whatsoever in your opening post?
Please tell us more about the environment.
What rights have been given to the user account in the VMware credentials?
See this TN:
What are the minimum permissions needed to properly backup and restore using vStorage api?
http://www.symantec.com/docs/TECH130493