There is a build-up of savesets
I have small problem,
There is a huge journal task running. Safety copies immidiately removed. But during day, I have warning at the site level saying ;
"There is a build-up of savesets"
This is I guess a EVOM setting which I can change and let site give this warning at different treshold? Does this error cause any performance issue?
Sometimes during the middle of the day following message appers;
There are xxxxxx savesets that have not yet been backed up or replicated for Vault Store
If I put site in backup mode (At the night I have already took successfully backup , I see "IgnoreArchiveBitTrigger.txt file turns to old") , Took another backup and clear the backup mode, This error disappers.
How many times do I have to take EV backup in a 24 hours?
If I see savesets error, Archived items are not indexed, If I take backup, items are indexed.
I cant take 5 times backup in a day. How to avoid this?
Thanks in advance..
Comments
No, it is just a warning to
No, it is just a warning to let you know savesets have not been backed up. Since the threshold is too low for your environment you can adjust it. I would recommend setting it to what you expect for the entire day, that way when you see it you know your backups didn't run correctly.
Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK
You need to set backup mode
You need to set backup mode before the backup and then clear it after the backup. When EV comes out of backup mode it looks for the trigger file which should have a creation date / time of the end of the backup. If it finds one it knows that all files older than the time of the trigger file have been secured, the trigger file is then renamed it to .old and ev starts the post processsing of the files.
So the issue you have is not really an issue but one of timing. I suggest you review your backup schedule so that things happen at the right time in the right order. This technote should help:
http://www.symantec.com/business/support/index?page=content&id=TECH66202
Agreed
I agree with above, but should also say that this should not be affecting your indexing. I would ensure your backup process is set properly (using backup mode) but most likely you have an issue where you simply need to tune the threshold to a number that will accomidate the expectations of what you will archive in a day.
That said it sounded like there were almost some other issues involved in your posting:
- Do you have a backlog of items in teh Journal mailbox? I felt that you did but could be wrong
- Indexing should not be affected by the items which have not been backed up.. . .so I am not sure what is going on there
Hope this helps.
J
Would you like to reply?
Login or Register to post your comment.