Search results for query: *

My apologies, David is right. I wrote the other way in my last post by mistake

there should be an option in groupshield to exclude outgoing emails and check if that helps. I am sure even windows 'ntbackup' will suffer the same problem. Best is to get in touch with mcafee to see if they have any workaround for backups.

okay, does the restore to machine (target) have domino servcies running ?

if you have a copy of 000000.qsd folder from the BAB directory saved, then you can do a cstop rename the current folder and replace it with the old one

okay that message has got nothing to do with the throughput. What is your database level throughput?

this error is completely different from the other. Lot of things to check, as a first step need to ensure if latest device support for ARCserve in place

BTW, here is the recommendation from ca which is a different version of my previous post http://supportconnect.ca.com/sc/kb/techdetail.jsp?searchID=TEC419740&docid=419740&bypass=yes&fromscreen=kbresults (if you dont get the page, simply log on to http://supportconnectw.ca.com and type...

Is that an error? does activity log show any warning or error message for this job ?

what version of the agent on the blackberry server ? If you are running a lower build/version of the agent than your main backup base product then you must upgrade.

okay, lets dissect this. Can you put the current job on hold, create a new test job with media pool and start with all blank medias ? may be the old job is corrupt or has a problem which needs a closer look

we can try setupsql but I am not positive that it may change because the way sql works. By default any new db in sql is case insensitive (though you can set the coalation during sql server installation). Setting a custom coalation name is possible only at the time of new db creation from sql ent...

not sure what algorithm or logic is used to resolve..

the question is what tape we are assigning to the scratch set? When you manually assign tapes to the scratch set it may also show some of the tapes that you dont have in the tape drive, need to make sure if the tape id of the one in the drive matches with the one that you assign to the scratch...

...which will cause issues storing case sensitive OS info like solaris. Best to change the coalation mode of sql to case sensitive mode. you can find this info by doing a right click on the sql asdb from sql ent manager and going into properties. A '**CI**' in the coalation name is case insensitive

what is the file size of 11.5 sp3 you downloaded ? If you have a cd try it from there

*there were three Thursday tapes, none of which were in the Scratch set or anywhere in the Media Pool*" - Thats the problem... the tape with the id's it was looking for was not in the drive/group0

so you talking about ARCserve sql db (asdb) ?

Could you pls modify the job that is failing, go to destination tab and check to which group it is pointing to. According to job it says Group 0. If it is then check the media id for those tapes and see if there are same as that of what we see in the media pool. We can do a quick erase plus on...

Are they RUN once jobs are they have been scheduled to run on a daily basis? If it is run once then the retention time is 24 hrs which can be changed from server admin config option.

You can try few more steps to try and make it work. Did you check if the tapes that you assigned in the scratch set is in the tape drive as well as in the same device group in the "destination tab" to which the job is pointing to ? Media pool backup jobs check if the media in the scratch set...