Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. akertesz

    unable to get minimum quite time

    The main problem with that is, if you are a true 24/7/365 production environment, with a large amount of data to be backed up, "Can you afford to stop critical services long enough for that backup window?" If you are only getting 5 - 10 GB/hr throughput and backing up 70 -- 100 GB...
  2. akertesz

    Event ID 2009 errors

    We are consistently getting 2009 errors, and the 11th d-word is 000003ea, which is indicative of table reaching it's maximum size and could not be expanded. We are running NT4.0 sp6a, 2GB RAM. We have approximately 30 DOS spoolers running FoxPro 2.6 that are talking to this server on a...
  3. akertesz

    unable to get minimum quite time

    We had this problem as well. After talking to the Veritas engineers, there is essentially no way around it. You can change the setting in the registry, but they recommend a minimum of 2 seconds, our servers are so intesive that I can't even get the 2 seconds they recommend. This will cause your...
  4. akertesz

    "Media provided to continue backup already contains data" -error messa

    I am using an Exabyte 220 Autoloader, with 2 Mammoth drives, partitioned into 10 partitions using the Veritas software. Server is NT4, sp6a, 2GB RAM, BE v8.5 build 3572. I run two concurrent jobs nightly at 9:00pm, all jobs complete successfully except the very last one on Friday. The jobs are...

Part and Inventory Search

Back
Top