04-19-2013 08:00 AM
Hello everyone,
I just finished a backup and my DVS files are with the attribute N
In VAC there is a critical error still saying that my files aren't backep up, by the backup job on Netbackup was 100% fine
Any suggestions ?
Thanks!
Solved! Go to Solution.
04-19-2013 12:16 PM
04-19-2013 12:33 PM
It was A, but after backup it turned out to N
I could ran the query, there are Archives with BackupComplete 1 and others with 0, I want then to be 1 right ?
04-19-2013 12:39 PM
04-19-2013 12:49 PM
Here after the ran of the query:
Them I went to the location of this file here
Maybe the lines are not equal, but that file is in this folder, and all the files in this folder are marked with N
04-20-2013 08:38 AM
*g*
N is for "Not Content Indexed" it has NOTHING to do with backup....
FILE_ATTRIBUTE_NOT_CONTENT_INDEXED
04-21-2013 06:57 PM
Well, if anyone is having the same problem, here is what I experienced:
With the differential incremental backup the archive bit is cleared, BUT NOT ON THE FIRST TIME, if it is a new partition, run first a full backup, and then run differential incremental backups.
This should solve
Thanks everyone for the replies
04-23-2013 01:33 PM
We were experiencing this problem intermittently with Netbackup on EV 10.0.1. Sometimes the archive bits would not be toggled even though the backup job had completed successfully. Switching to the Trigger File method solved the problem permanently. Netback automatically creates the trigger file when backing up EV, so it was simply a matter of selecting the Check for Trigger File option on the VS partition properties backup tab.
04-23-2013 03:08 PM
04-25-2013 02:17 PM
Rob,
Yes, that's correct. What I saw was that the archive bit was simply not being set by Netbackup even though the backup job completed successfully. The issue usually only happened on incremental backups and happened intermittently on the same job/profile/schedule. We verfied in the netbackup logs that the savesets were being properly backed up. Once the archive attributes were not set by a differential job, they continued to be left unset until the next full backup. Once the archive bit was successfully set on a saveset, EV always flagged the item as secured during it's partiton scan. The trigger file method has worked flawlessly.
04-25-2013 02:30 PM
04-25-2013 03:00 PM
Jesuswept,
We are using a supported version of Netbackup with the EV agent. I made several pretty thorough investigations of the netbackup logs and could see that the savesets were definetly being successfully wrtitten to tape.
There was another thread on this a few months ago from a user with an identical configuration to ours who was experiencing the same issue and who worked it through with Symantec Support. Their soultion was to use the trigger file method. https://www-secure.symantec.com/connect/forums/items-stuck-pending-all-users