Arcserve job that won’t run

Have you ever seen a job in Brightsor Arcserve that is correctly scheduled but won’t run? If you have a look at the job closely in the Job Status screen you will see that, most likley, the backup job doesn’t have a Job ID number. All this indicated that the Job Queue has become corrupt and needs to be recreated.

Prior to any changes it ius always a good idea to save your existing backup job to a file. Simply right mouse click on the job in the Job Status screen and select “Modify Job“. At the modify job screen selecet File | Save As and save the backup job.

So, the first step is to stop all the Brighstor Arcserve Engines. To do this simply right mouse click on the three green circles in the top middle of the Brightstor Manager and select “Stop all Engines”. After a few moments all the indicators should go to red. You can also stop the engines via Services in Administrative tools.

Now locate the :\program files\ca\brighstor arcserve backup folder on your hard disk. Under this folder is a queue directory, which looks something like 000000001.qsd. Right mouse click on this and rename it to something ( ie 00000001.bak ).

If you return to the Brighstor Manager and right mouse click on the three red circles and select “Start all Engines” from the menu that appears. A new queue ( and directory ) will now be automatically created. The queue will be totally empty ( of even a database prune job ), so you’ll need to re-create both your backup job and the normal database prune job. To recreate the prune job you will need to go into “Server admin” and follow a few steps to recreate the standard prune job (I’ll run over this in my next post maybe). If you saved your backup job out previously then you can simply create a new backup job and restore it from the file you saved previously.

Beware that if you are using an autoloader, once you create a new queue and recreate the backup job the link between the media pool and the backup job is broken. You will therefore need to move the media in the autoloader into the correct pool set (scratch or save). We have found issues doing this and recommend that the best bet maybe to erase the tapes one at a time so they are blank. A blank tape should get picked up automatically, reformatted and placed in the right media pool. We also found that sometimes you need to restart all the engines again to get Brightstor to accept the newly created blank tape. Why? We don’t know but we do know that starting and stopping the engines have fixed our problems.

Recreating Arcserve Database Prune job

You asked for it, well here it is. if you have blown away the Brighstor Arcserve queues then you will usually need to rereate the Arcserve database pruning job. This is a regular maintenance program that Arcserve runs that removes old records from the backup database into which Arcserve records all manner of information about each backup it runs. As you can imagine this can get pretty big after a while, so the pruning job ensures that it doesn;t consume your whole hard disk.

To recreate the pruning job :

1. Open Arcserve Brightstor Backup Manager

2. Select Quick Start | Server Admin

3. Brightstor Arcserve Backup Server Admin should now appear. Select the Database Engine tab

4. Now select Admin | Configuration from the menu

5. The Configuration window whould now appear. Check the option to Enable Database Pruning. Set any parameters that you need, the default option of 30 days is usually fine. Also select at which time you wish the prune job to run ( not when the backup is running generally ). Leave the Delete media related database records option unchecked.

6. Now check the Submit Prune Job option and press the OK button

7. Close the Brightstor Arcserve Backup Server Adim window and return to Arcserve, where you should now see you prune job

Recovering deleted public folder

So you thought you could use the Exchange Server 2003 recovery group to recover a deleted public folder? Sorry to tell you that you can’t. The Exchange recovery group is only for Mailboxes, not public folders. So how do you restore it? Unless you have a backup program like Brightstor or Veritas, with the appropriate agents then you have these options.

1. Attempt a restore of the deleted folder.

Go to Microsoft website and search for PFDAVadmin.  Download the public folder tool and you can recover your deleted folder
 
http://support.microsoft.com/kb/287110/en-us
The above is a command list.
 
You can also try and use Outlook to recover the deleted folder by going to the location where it was deleted, on the user that deleted and select Tools | Recover Deleted Items.
 
Another method is to use OWA.

 
1. Go to OWA and login as the user that deleted the folder.
2. Click on the button for public folders and it will open up a new windows with the public folder structure.
3. Browse to the parent folder of the deleted item, right click on the parent public folder and select “Open in New…”
4. Change the URL from
http://servername/public/toplevel/subfolder/?cmd=content
to
http://servername/public/toplevel/subfolder/?cmd=showdeleted&btnClose=1 (replacing servername with the name of your server).
4. Find the deleted folder, highlight the folder, and click Recover.
 
2. Restore the Exchange store
 
If the above options fail then you are going to have to restore the whole public folder store. If you attempt this on the same server it will overwrite the public store that is already there. To avoid this you will need to build a new server ( same name ), with the same AD name, install Exchange and then do a complete restore of the databases from the original server. Then you should be able to recover the deleted public folder.
 
The second option isn’t that nice but it maybe you only option. This issue should make you stop and think about wide spread usage of public folders, because they are so cumbersome to restore.

Computer Associates (CA) licensing

Something we have always found very mysterious is the way Computer Associates (CA) license their products. Generally, it is hard to locate exactly what product may be generating an out of license error. Hopefully the following information will make it easier for people to locate.

Computer Associates (CA) licensing information is usually held in
 
c:\program files\ca\shared components\ca_lic
 
in here you’ll find a file called lic98.log. This contains a log of all the license errors. Check this log to see what products aren’t licensed.
 
Also in this directory you’ll find a file calicnse.exe which when run will display the products that are licensed and their license count. Prior to selecting a product listed here you are able to enter additional licenses at the bottom of the window.
 
The license details are held in the register at hklm\software\computerassociates\license\products. Under this key you will find a number of subkeys that designate the products ( like 31AM, 3EPP ). A list of the corresponding product code can be found at :
 
http://supportconnectw.ca.com/public/reglic/infodocs/itcodes.asp
 
Under each product key should be a folder 011 and under that ( if the product is licensed ) you will find a key ( folder ) with the license code. If the product doesn’t have a license key ( folder ) under it then the product is not licensed.
 
To re-license the product simply delete the product key (folder) and return to the licensing options in the product ( usually under Help | About ) to re-license the product.

Try new filters first

We’ve been mucking around with ADSL2 lately and it has proved to be very frustrating. The problem is trying to locate the issues. Firstly, you change all the equipment at your end. Next you upgrade everything at your end. After that you blame the ISP and give their tech support a hard time and just when you think you are going to pull all your hair out you replace the ADSL filter on the phone line and viola, everything works.

From what we can work out ADSL, operating at higher frequencies, is much more sensitive to interference than normal ADSL. So using an older ADSL filter on an ADSL2 line may not provide enough “filtering” to allow adequate reliability. If you are having issues, the first thing that we would recommend you try is buying and installing a new line filter. It worked for us.

We have also seen some cases where ADSL filters have caused issues on lines so for what it is worth go out and buy a few filters and keep ’em handy and if problems develop try a new filter first. It may save you the hours that we wasted.

There are multiple accounts with name MSSQLSvc

Having nothing better to do over the Christmas / New Year break (yeah right) we thought we might enjoy a good swing. A swing migration that is. Firstly, all credit to Jeff Middleton for his excellent guide on how to get a new SBS server working without disrupting and old SBS server. It doesn’t even have to be an SBS server but we know that it works with SBS. For information about the process see www.sbsmigration.com.

Our only criticism of Jeff’s work is that although it is very through we found it a little disjoined. To overcome this we developed our set of custom migration notes that made it clear for dummies like us. During this process we have come across a few interesting tips and issues that aren’t mentioned in Jeff’s notes.

The first of these is the following error that started appearing in the logs :

There are multiple accounts with name MSSQLSvc/:1433 of type DS_SERVICE_PRINCIPAL_NAME.

Turns out what happens was that our initial SBS Premium server ( with SQL 2000 installed ) was set to run the SQL services under a specific user. However, when we installed the new SBS server we set up the new version of SQL to run under another account. This means that two different users in the Active Directory think that they in control the SQL service accounts generating the above error.

The fix is pretty simple. Use the setspn utility to check the accounts and then change the setting so only one is registered for SQL.

Use

setspn -l account1

&

setspn -l account2

to check that both accounts were registered for mssqlsvc. Now use

setspn -d mssqlsvc/:1433 account2

to remove the suplicate SPN from the second account (in this case account2).

So for all you SBS swingers out there keep this in mind if you are planning to change the service accounts logins for accounts during migration.

Windows updates fail to install

Having a problem installing Windows Updates from the Microsoft web site on your XP machine? Typically they download but when they actually go to install the message you get says “failed”. If so try this :

1. On the machine with issue, locate and stop the service “Automatic Updates” in Services under Administrative Tools from Control Panel.

2. Locate C:\WINDOWS\SoftwareDistribution and delete all the contents in this folder but do not delete the folder C:\WINDOWS\SoftwareDistribution, just all files and folders underneath it.

3. Return to Services and restart “Automatic Updates

4. Re-run Microsoft Updates from the web site. You will need to reinstall the Microsoft Update ActiveX control but updates should now download and install.

SBS2003 standard and VPN issues

We were recently trying to get VPN access to an SBS 2003 standard install. Everything we tried just didn’t work. We ran and re-ran the wizards, checked that the right ports on the hardware firewall were forwarded but still no luck. Typically, we would get the message that the VPN was connecting but during authentication it would simply timeout and we would receive a message that the VPN had been disconnected.

Turns out that the problem lay with the hardware firewall. What finally ended up resolving the problem was a simple upgrade of the firewall firmware. Once completed the VPN worked a treat. Initially you just never stop and consider that the hardware firewall ( external to SBS2003 ) could be the issue. It works and has always worked so why should it be a problem? Well, in this case it certainly was the problem.

Another handy tip we’d give is you is to always backup the configuration of the hardware firewall before you upgrade the firmware. Over time a lot of changes can be made to a hardware firewall that are note always documentated.