Search results for query: *

We have over 200 FSD's and have no issues. I believe the limit increased to 256 or greater after a recent update (SP3 possibly).

That's exactly what I've been looking for; I will try to replicate this in my test environment and post back if I have any troubles. If I do not post back in the next week, then that means all is working well. Thanks again.

I'm kind of stumped on this one: I have approx. 10 Windows 2000 Servers that I backup through Arcserve 11.5 w/DR option and universal windows agents (all updated). The backups are dynamic and all of the disaster recovery information is saved properly to an alternate NAS location. I have...

Update I was in fact able to go over the 128 FSD limitation as davidmichel stated. Everything is still running smoothly.

Malas, I didn't find any PM option on this forum to send this directly to you, so - Here is the link to the Arcserve 11.5 download page (For Windows): http://supportconnectw.ca.com/public/storage/downloads/nt/115/basbr115-solpatch.asp You are looking for: QO86307 Take note of the Languages...

Thanks davidmichel, That gives some hope; I will create some future FSDs over 128 and see if I run into any issues and repost. Do you know if this was an increase in SP3? I cannot seem to find anything in the documentation / change log that says anything about this increase.

There are predefined batch files in C:\Program Files\CA\BrightStor ARCserve Backup called cstop.bat and cstart.bat The cstart.bat file might be a temporary fix until you can figure out why the backup job(s) is killing the database engine. Just schedule this to run after your backups with the...

Hi pachichous, You can also apply a filter to this file; these files will get automatically recreated in the event of a restore and I haven't found any reason that they MUST be backed up. Here is what I have applied to some of my windows backups running .NET: (Modify backup, choose filter...

I would make sure that you have all of the latest device updates from CA. I had this problem many times with a tape autoloader and a patch solved it. I also had this issue with File System Devices prior to 11.5 SP3 which appeared to be due to a tape engine bug. 11.1 patches...

I currently backup 11 Production servers which are a combination of Win2k Server, Netware 4.x, 5.x, 6, and 6.5 (all with the latest service packs and latest tuned agent). The central backup server is running on Win2k server and has Arcserve 11.5 SP3 build 4402. All of the servers are backed up...