Fixed – “The filename, directory name, or volume label syntax is incorrect" when you add a hard drive to Windows 2008 R2 backup

Apparently, according to Microsoft KB Article 2009365 this issue occurs when a previously hard drive (or the only previously defined) hard drive has been removed from the server and a new drive is being attached. This is typically the case when setting up a new server and preconfiguring the backups to go to the second identical usb drive. Most people are just going to unplug the drive leaving the old power supply and usb cable attached to the server and power and plug in the new drive and then attempt to add it to the backup schedule. At this point the backup program will give the error “The filename, directory name, or volume label syntax is incorrect” as the old drive is no longer attached. Microsoft have a couple of solutions, including adding the first drive back to the server, or removing the first drive. Neither of which are very helpful if you are just swapping the external drive itself. The final solution is to add the drives from an elevated command line using the following.

  1. Run the following command from an elevated command prompt to determine the Disk Identifier of the new disk:
    wbadmin get disks
  2. Based on the output, locate the disk that will be added to the scheduled backup. Make a note of the Disk Identifier. The output will resemble the following:
    Disk name: xxxxxxxxxxx
    Disk number: x
    Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
    Total space: xxx.xx GB
    Used space : xxx.xx GB
  3. Run the following command to add the new disk to the Scheduled backup. Use the Disk Identifier from the previous step as the "AddTarget" parameter.
    WBADMIN ENABLE BACKUP -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
  4. When you receive the following prompt, type Y for Yes.

"Do you want to enable scheduled backups with the above settings?"

5. You may be prompted to format the drive if it was previously used in another server or for another purpose.

The screenshot below shows the addition of a USB drive to my virtualised SBS server.


BackupExec 12 fails to LiveUpdate on Windows 2008

When trying to run LiveUpdate from within BackupExec v12 running on Windows 2008 you may get the error message “To receive updates, Backup Exec must be registered with LiveUpdate. To automatically register now, Click Yes. If you choose not to register now, you will be prompted again when you click LiveUpdate.” The solution is to right click the BackupExec icon and run as Administrator. LiveUpdate will work.

Backups may take some time to complete….

Day 86 - I may be some time. I needed to do a restore of some voicemails on a server and the calculations on how long it was going to take were slightly off as you can see from this screenshot – it actually got as far as 150 days before it reached the data on the file and started the restore off. Typically I have to do this when the voicemail server crashes (due to a power outage when it wasn’t on a reliable UPS). Everytime the server crashes I would have to restore 2 peoples voicemails (out of about 70 voicemail boxes). They are the only two who have their voicemail wiped and Avaya don’t care about the problem. What is weird is that this time the server had a controlled shutdown and not a sudden crash.
I sent the user this screenshot and told them it might take me a while but I’m working on it – they replied saying they didn’t think they had *that* many voicemails!

Removing an Ultrium tape

I didn’t know that you can only eject an ultrium tape drive when it is completely rewound. Detailed instructions from HP on removing an Ultrium drive are provided. Our Dell technician didn’t know this and we were given the ability to remove the tape *any* way we liked when a tape was stuck in a drive that was replaced. Now I’d like to know if this would have solved the problem….
Thanks IT Technobabble

0xe00084af failure in symantec backup exec caused by wsus 3 installation

Fixed! One of my servers has been failing to backup with the error “0xe00084af The directory or file was not found, or could not be accessed. Final error category: Job Errors. For additional information refer to link V-79-57344-33967” I spent ages troubleshooting the errors and trying to work out what was going on and found that it would fail to backup any file on the local hard disk of the machine.
I posted a note in the symantec forums and didn’t hear anything back, but did find a post that upgrading to 10d might fix it (not a current solution as this would mean purchasing an upgrade of the software for the exchange agent and the exchange agent is currently working)
The other solution was to stop SQL servers on the box. This server was the WSUS box and I had also recently upgraded it to version 3 of WSUS. This created (at least) two new services – SQL Server VSS Writer and Windows Internal Database (Microsoft ##SSEE). Through trial and error I discovered that stopping the SQL Server VSS Writer service meant the backup would work, which is weird as why this should affect me backing up something like c:\jobs\fred.bat which has nothing to do with SQLI don’t know.
I’m hoping that my forum posting about the problem will get a better solution but for now I’m just pleased to be able to backup my file server.

cure to 0x800423f4 with ntbackup failing

One of our clients has been having issues with Volume Shadow Copy and SQL (MSDE) causing the backup to fail with the error 0x800423f4. By following the script at TazNetworks it looks like the backup might work tonight. It’s too early to tell but at least when I kicked the job off briefly it started to some work rather than just quit out of ntbackup.
Update Unfortunately the solution didn’t work for me, but I noticed that there was a hotfix available (904418) which is for x86 based operating systems. I noticed that they were trying to register the Sqlvdi.dll file, so I reran the registration of this dll (which wasn’t in the original script above), restarted ntbackup and the system state backup worked ok which was great news as it wasn’t working previously. I then kicked off the nightly backup to run though and it looks like it is working, so in short –

cd C:\Program Files\Microsoft SQL Server\80\COM
regsvr32 sqlvdi.dll

Image ghosting woe’s

I’ve been trying to backup the main pc at home as it’s getting really really slow for a 1 year old pc. Kristen blames it on all the stuff I keep installing on it which is probably true. The weird thing is that I can’t see anything in task manager or perfmon that shows why it is so slow. CPU and memory usage is low yet the machine sometimes takes ages to respond so it’s a reinstall time.

However, before doing that I wanted to image the hard disk – I’ve been attempting to do this since Saturday now. MicroCenter were doing a 160gb hard disk for $40 after rebates so I thought I’d ghost the original disk to my external usb disk and then restore the image to the second disk. (No link as the rebate was only valid until Saturday)

I had several attempts of doing this, but found that the pc would freeze whilst in the middle of the image. Yesterday morning I started the image off and when I came home from work it was still going…. until I shredded something and it crashed ghost with an error back to dos.

I then tried Acronis true image which said it would take 20 hours to ghost the image (of 40gb!) but again this morning it had frozen after running overnight.
By the end of last night I was really fed up with the thing as it shouldn’t be this difficult so I went to sleep and decided to try again this evening.

I’ve a feeling that for some reason my external usb disk is being detected as a USB1 disk instead of USB2 which is why the original ghosting is taking forever.

I’ve now had the idea of ghosting the image direct to the new hard disk from the old one – if that works (which is giving me a realistic time of about an hour to ghost) I may be able to copy the ghost image back to the original disk and then restore it back over to the new disk.

Once I have a working ghost source I can scrub the new disk and reinstall from scratch and also see if I can get vista on the machine too……

Back at last!

We’re back! My site was closed sometime last week as the server it was hosted on was having resource issues. I was offered a move to a new server and unfortunately the flat web pages got moved across but the sql database backend didn’t. It’s now been fixed and we’re live again. Expect a couple of posts from me as I catch up on my blogging from the past couple of days.
Now I’m off to ensure I have a REALLY good sql backup of my data – for some reason my control panel backup didn’t include a valid copy of my mysql databases.

Backup exec jobs won’t run but go to queued.

Discovered today (after a lot of hassles) that Backup Exec may have a problem where backups to a disk folder does not work and ends up in a queued status. Eventually discovered that if you drag the “backup to disk” media to the scratch media pool then the backups start working again.
Didn’t find anything on the veritas/symantec web site about this and nothing in google either so hopefully this will help other people out.

Data recovery

Kristen had an upsetting moment when she plugged in the XD card from the camera and saw the following
It looked like all the photos that she had taken today were corrupt and unreadable (and translated into chinese!). Fortunately I remembered reading about PC Inspector File recovery which I had tried out but not in a real life scenario. One download later and a search of the hard drive returned lots of image files stored on the disk (as expected). Recovering them was just a matter of selecting whereabouts I wanted to put the files (on a different disk). There were two options available. The first was using FAT1 and the second was to use FAT2. When I used FAT1 most of the files came back ok, but there were several files that came back slightly corrupted – this one is one of the worst
Spliced House.
Some of the other photos have been uploaded to my Birdtable zoto gallery as Kristen took some excellent pictures of the birds on the birdtable today.