Forum Discussion

xious's avatar
xious
Level 2
16 years ago
Solved

Symantec Livestate 8: Issues backing up from a dynamic disc?

I am running into problems backing up a new domain controller I just installed on my network.  I can back up the c drive of my dc to its f drive, but I can't back it up to a disk on another server.  I have verifed that the permissions (sharing and ntfs) are what they need to be on the remote share, but it still fails at 5% when I am trying to back it up with Livestate 8 to another server.  I am able to back up my other servers to the same share just fine.  The DC I am having problems with is running server 2003 standard sp2.  The only thing I can think of that is different about this DC is that I converted its disk to dynamic.  Does 8.x have problems backing up dynamic disks to basic disks or does anyone else know what may be the problem?  Below are the three errors I keep getting when I try to run the backup:

Error EC8F17B7: Cannot create recovery points for job: GA075PCDC004. Error E7D1001F: Unable to write to file. Error EBAB03F1: The semaphore timeout period has expired. Error E7D10046: Unable to set file size. Error EBAB03F1: The handle is invalid.
Details: 0xEBAB0005
Source: Backup Exec System Recovery

Error EC8F17B7: Cannot create recovery points for job: GA075PCDC004. Error E7D1001F: Unable to write to file. Error EBAB03F1: The semaphore timeout period has expired. Error E7D10046: Unable to set file size. Error EBAB03F1: The specified network name is no longer available.
Details: 0xEBAB0005
Source: Backup Exec System Recovery

Error EC8F17B7: Cannot create recovery points for job: GA075PCDC004. Error E7D1001F: Unable to write to file. Error EBAB03F1: The semaphore timeout period has expired. Error E7D10046: Unable to set file size. Error EBAB03F1: An unexpected network error occurred.
Details: 0xEBAB0005
Source: Backup Exec System Recovery

Thanks in advance for any help given,
X
Backup and Recovery
BESR 8.x
Compatibility
Configuring
System Recovery
  • xious's avatar
    xious
    16 years ago

    Sorry for taking a couple weeks to respond.  Apparently the server was having probelms with  being set at auto for speed and duplex.  I set the network card to 100 Mb full duplex and the EBR software started working correctly.  Really wierd since I was able to do everything else I needed to do over the network fine with it set to auto.  Thanks, for your time and help.

  • criley's avatar
    criley
    Moderator
    16 years ago
    I wouldn't expect dynamic disk to be an issue here. Are you able to create a basic disk on this server and then backup a dynamic disk to this? If this works then you are most likely looking at a network type issue. Some articles that may help:

    http://support.veritas.com/docs/300739
    http://support.veritas.com/docs/319573

  • marcogsp's avatar
    marcogsp
    Level 6
    16 years ago
    You might also try using the \\ip-address\sharename convention instead of the the \\servername\sharename convention when specifying the remote location to write the images to:  That would bypass any DNS issues that may affect this process.  You should also try switching netwok cards/interfaces and cabling to isolate a bad/chatty NIC or faulty wiring.  You can also try moving this server's connection to another port on the switch

    Do any of the servers that are imaging sucessfully, also have dynamic disks?
  • xious's avatar
    xious
    Level 2
    16 years ago
    The server only has a single hard disc so I can't try changing it back to basic as doing such will wipe the hard disk.  I looked at the links provided by Chris as well as other an none had a fix.  From the live state server I can ping, RDP, and copy items back and forth to the DC.  I can do it the opposite way aswell from the DC.  When I ping one the devices from each other all the responses are very fast.  So network speed does not seem to be the issue at all.  I can ping or RDP using either the IP address or the computer name.   I tried setting the destination of the back up using the IP address of the DC, but that did not work.  None of the other servers/workstations were set up using a dynamic disk which could just end up being a coincidence.
  • marcogsp's avatar
    marcogsp
    Level 6
    16 years ago
    I had to test a DC scenario in my lab yesterday, so I tried duplicating your issue.  I converted the disk on one of my DC's to dynamic and sucessfully imaged it to a share on another DC.  I don't think your disk being dynamic is affecting this issue.  I'm leaning toward a creeping corruption in the TCP/IP protocol installation on the affected DC.  While the utilities you tested with are great for testing routes and paths, they really don't put a huge strain on the TCP/IP stack when used properly.  I've only had to reinstall TCP/IP on a domain controller a few times in my career, since it is rarely required in the first place.  The instructiions to do so are located here:

    http://support.microsoft.com/kb/325356

    Record your IP address info because this procedure will wipe out this info.

    There is a fairly safe way to restore the basic disk configuration:
    • Image the logical drives on the dynamic disk with BESR
    • Delete the partitions on the dynamic disk.  On the SRD you con use DiskPart to do this.  You can also use the "Delete Disk" portion of the SRD when editing the drive recovery settings during the recovery process.
    • Restore the logical drives within the SRD environment
    The recovered logical drives will be restored to a basic disk with this procedure
  • xious's avatar
    xious
    Level 2
    16 years ago
    I followed the instructions provided and ran "netsh int ip reset c:\resetlog.txt" from in command prompt.  I restarted the box and re-entered its network informaion: ip address, subnet, gateway, and dns.  It still failed with the same errors.  I uninstalled symantec endpoint and restarted the DC since Symantec mentioned that end point sometimes can interfere with livestate.  Still did not work.  To verify the switch config is not an issue, I moved my DC to another area where I have other servers that back up fine.  I disconnected a server which is used for test purposes and hooked up my DC to the same exact port that the other server was using.  I verifed I had network connectivity and then tried to back up the DC.  It failed again.  I reinstalled the back up software on the DC just to verify it was done correctly, and it still failed.

    To give a little more info on this DC, it is a Dell Power Edge SC 440.  This server was repurposed to serve in a new capacity.  It did not show any signs of hardware errors before being wiped and having server reinstalled on it.  It still does show any signs of there being hardware issues.  When you are logged on locally to the DC and try running the back ups it pops up messages about "Delayed Write Failed."  Write after wards, though, I can copy files directly to the location it said it could not write to.

    This is starting to get very frustrating.

    Thanks for all your assistance thus far.
  • marcogsp's avatar
    marcogsp
    Level 6
    16 years ago
    This is going to sound odd, but try updating the ATI RN50 video driver for your server.  I've read cases where an older ATI driver can cause enough interference to cause Delayed Write Failure errors.  Just for laughs, try booting the server and use the F8 menu to "Enable VGA Mode"  If it is a video driver issue, that should help isolate it.

    Does this server have SATA or SAS drive(s)?  I've seen some Delayed Write Failures myself with some Hitachi SATA drives when paired with certain drive controllers.  Are the drive(s) OEM from Dell  or aftermarket.  Dell usually does a good job of testing compatible drives with their servers, so I check their specs first when considering installing aftermarket drives in their servers.
  • xious's avatar
    xious
    Level 2
    16 years ago

    Sorry for taking a couple weeks to respond.  Apparently the server was having probelms with  being set at auto for speed and duplex.  I set the network card to 100 Mb full duplex and the EBR software started working correctly.  Really wierd since I was able to do everything else I needed to do over the network fine with it set to auto.  Thanks, for your time and help.