OK...This is out of hand.
I'm not a SQL guy by any means other than the systems admin portion. I dont claim to be dba in any sense.
Our asdb.mdf is only about 500MB. However, the .ldf is now over 25GB. CA says to run this maintenance plan. So I set it up, step by step, try to execute it...
I want to migrate my SQL database for Arcserve to a centralized SQL2k5 server. The local instance on the Arcserve box is also on our big file server, and is just sitting there chewing up resources for one asdb database.
The host is SQL2k5 and the central server is SQL2k5.
I've been searching...
My advice...
Bring the new 2003 server online, patch/update, and dcpromo it up to a DC.
With both DC's online in AD, work on migrating your exchange to exch2003 on the new DC.
There are tons of migration tools out there for this. It's not as bad as it may sound going from 2000 to 2003.
Once...
LOL
For what it's worth, I've brought 6 enterprise domains online, from NT4-to-2000, and 2000-to-2003, and mixed.
I have never...not once in 10 years, used any kind of prep tool (aside from exchange migration tools) to build active directory.
I have a feeling that the ADPREP tool may have...
You could also put the .msi file in the SYSVOL folder
(%systemroot%\SYSVOL\sysvol\domain.com\scripts)
and this replicates across all of your domain controllers. Give it 24 hours to replicate (or force the KCC) and then script it into the logon script, or create a new GPO-based logon script.
These types of errors are usually related to DNS.
From your other server, can you resolve/ping the AD server by NETBIOS name?
So, if server1.domain.com is pinged from server2, does it correctly resolve an ip address and Reply/Reply/Reply?
I assume your AD server is also hosting internal DNS...
1) dcpromo the 2000 machine. this will remove all AD components from it, remove it from the AD structure and leave your 2k3/exch box as the sole DC in the AD Domain.
2) backup what you need, data-wise, and do a fresh install of 2003 onto the other server.
3) Once Server 2003 is installed...
Some things to try....shut both the server and tape down.
Turn on the tape device, and then power up the server and watch the SCSI BUS detection process during bootup.
As I found, check to make sure there are no bent pins in your SCSI cable. Maybe try a different cable.
I've found Veritas...
Well, long story short, whoever plugged the SCSI cable in didnt line it up correctly, and bent several of the pins.
After spending a good hour with some fine tools straightening things out and plugging it in correctly, it worked perfectly.
That's it. It was the last thing we thought to check...
Having some issues here with our autoloader...
My engineer cohort is on the phone with Symantec to see if they can figure it out so I thought I would post here to see if any of you had any ideas.
We migrated all of our servers into new cabinets last weekend.
One of the glitches we have found...
Didnt see this one coming.
We have two backup jobs that both start at 7pm on a 2-drive ADIC100.
The first of the two jobs failed with this error:
E3705 Unable to Format media (MEDIA=1/02/07 7:00 PM, EC=BAD DEVICE NUMBER)
The second job ran fine.
Looking for suggestions on things to check...
[01/01/2007-19:13:46 ,0,0,0,0,0,2,0,0,0] W3404
[01/01/2007-19:13:46 ,0,0,0,0,0,2,0,0,0] Unable to open file. (FILE=C:\Program Files\CA\BrightStor ARCserve Backup\CATALOG.DB\1-01-07 7_02 PM.DF26\1-01-07 7_02 PM [ID=DF26,SEQ=1,SES=1,SN=000157L1].TMP, EC=Access is denied.)
Had this in the log...
While I DO love a good chat about different technologies, I think we may be delvinga bit too deep into this.
Taking a step back for a second, we have BE running at all other sites, but BAB is still running our corporate office, and has been for 5-6 years. Our maintenance with BAB just expired...
Im taking a total stab at this here, but from what I've observed in the job logs, the difference between incomplete and failed is this:
Let's say one session backs up most of the stuff but has a couple of open file/sharing errors.
That is an Incomplete.
If you have authentication problems, or...
vschumpy,
Thanks for the reply.
Out of everything you listed, and a few of the warnings posted, they are not really issues to be concerned about.
My SQL database (asdbdat) is 120MB, while my Catalog.DB folder tree encompasses 1.2GB. This only includes the 14 jobs that have run since the...
We've recently reconstructed our database schema from the ground up, and when it was installed, the one installing enabled this option.
We use a local SQL2k5 asdb instead of the Brightstor model.
My question is: What is the purpose of the catalog? And is it just duplicating information...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.