After enabled Auditing on folder & Files - archive bit gets reset
Experts,
Environment:
OS: Windows Unified Data Storage server - Windows 2003 standard R2.
Role: File server
HW : Dell Power Vault NX series.
Backup SW: Veritas Netbackup.
Problem:
We use to take weekly full backu and daily incremental backup - file server data is >1TB.
Recently we enabled auditing on folders and files for DELETE & DELETE SUBFOLDERS AND FILES.
Now incremental backup is not happening - everytime it takes only full backup.
we know why this happens - archive bit is getting reset.
We got this article: http://seer.support.veritas.com/docs/277419.htm, but it is GP related.
Thanks in advance.
>>>> Veera.
Environment:
OS: Windows Unified Data Storage server - Windows 2003 standard R2.
Role: File server
HW : Dell Power Vault NX series.
Backup SW: Veritas Netbackup.
Problem:
We use to take weekly full backu and daily incremental backup - file server data is >1TB.
Recently we enabled auditing on folders and files for DELETE & DELETE SUBFOLDERS AND FILES.
Now incremental backup is not happening - everytime it takes only full backup.
we know why this happens - archive bit is getting reset.
We got this article: http://seer.support.veritas.com/docs/277419.htm, but it is GP related.
Thanks in advance.
>>>> Veera.
ASKER
Raja,
Thanks for the response.
Auditing was not done through GP.
We enabled it directly on the folders, because it is not for all the folders.
only few subfolders which are critical.
>>>> Veera.
Thanks for the response.
Auditing was not done through GP.
We enabled it directly on the folders, because it is not for all the folders.
only few subfolders which are critical.
>>>> Veera.
Veera,
1.Does the inc backup fail or skips the folder ?
2.Did you check for any errors on the backup log?
3.Any errors on the Event log of the server.
Also,Basically, after each file gets backed up its archive bit gets reset.
So then it depends on how your backup job failed. Netbackup has the habit of flagging a job as failed even when files actually have been backed up.
Check your job log. The files that were backed up would have their archive bit reset. The ones that didn't back up, wouldn't
1.Does the inc backup fail or skips the folder ?
2.Did you check for any errors on the backup log?
3.Any errors on the Event log of the server.
Also,Basically, after each file gets backed up its archive bit gets reset.
So then it depends on how your backup job failed. Netbackup has the habit of flagging a job as failed even when files actually have been backed up.
Check your job log. The files that were backed up would have their archive bit reset. The ones that didn't back up, wouldn't
If you setup auditing, the SACL of the file gets altered and this is a change to the file so the archive bit is reset. But this should only happen once, so the second backup afterwards should be incremental again. Did you really already run subsequent backups?
ASKER
Raja,
1. Inc. backup does not fail, instead it takes a full backup everytime.
2. No errors because backup never fails.
3. No errors on the event logs too.
McKnife,
Yes. As you mentioned it should reset the archive bit only once when we enable the auditing.
But in our case, we are not sure what is going on in the background. But everytime we run incremental it takes full backup only for those folder where we enabled auditing. Backup on other folders are good.
>>>> Veera.
1. Inc. backup does not fail, instead it takes a full backup everytime.
2. No errors because backup never fails.
3. No errors on the event logs too.
McKnife,
Yes. As you mentioned it should reset the archive bit only once when we enable the auditing.
But in our case, we are not sure what is going on in the background. But everytime we run incremental it takes full backup only for those folder where we enabled auditing. Backup on other folders are good.
>>>> Veera.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks McKnife.
We have not used group policy to enable auditing. We enabled auditing directly from Advanced option of security settings.
Do we really need GP?
what is the impact If we enable it directly?
>>>> Veera.
We have not used group policy to enable auditing. We enabled auditing directly from Advanced option of security settings.
Do we really need GP?
what is the impact If we enable it directly?
>>>> Veera.
There is no "enabling it directly". The settings at the auditing tab have no effect as long as you don't modify the auditing policy either via gpedit.msc/secpol.msc or via domain group policy. Please check your policy: secpol.msc - local policies - audit policy. To enable logging, audit object access has to be configured.
ASKER
Thanks McKnife.
Yes. we have enabled "Audit Object Access" in our Group Policy.
So, we need to apply the hotfix specified here http://seer.support.veritas.com/docs/277419.htm.
We will apply this hotfix during our regular maintenance window and update you.
Thanks again to make me clear on this.
>>>> Veera.
Yes. we have enabled "Audit Object Access" in our Group Policy.
So, we need to apply the hotfix specified here http://seer.support.veritas.com/docs/277419.htm.
We will apply this hotfix during our regular maintenance window and update you.
Thanks again to make me clear on this.
>>>> Veera.
ASKER
Thanks to make me understand few things on Auditing which I did not know earlier.
It looks like you manually changed the auditing permissions on the server, but still a group policy is with different setting is applied on the server...
Probably you can run rspo.msc from the server and try to identify the settings on the group policy....
to view the applied gp's on the server run gpresult on the server