And how did this turn out?
Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael Link with me at: http://www.linkedin.com/in/theessentialexchange From: Rob Bonfiglio [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 23, 2008 2:24 PM To: NT System Admin Issues Subject: Re: Server Core and Windows Server Backup I appreciate the help Michael. 1. Yes, the destination folder does exist. However, I also get the same error if I run "wbadmin get disks" just to get a list of the disks...so I'm thinking that perhaps there is something wrong with the service? I haven't changed any permissions on the server either on the disk or in the registry since it was setup. 2. The last "scheduled" backup would have been through Backup Exec. And yes, it completed successfully. 3. Am I supposed to manually allocate space for VSS to use wbadmin.exe? I hadn't seen this in the documents I've looked at for using wbadmin. 4. Yes, the volume is idle while I'm trying to perform the backup. I'll look into allocating space for VSS to see if that makes any difference. On Mon, Sep 22, 2008 at 6:59 PM, Michael B. Smith <[EMAIL PROTECTED]> wrote: Ok, I'm sure I could fiddle around with it and get it to work, I'm just trying to think what I've had happen in the past to help you: 1] Does the destination folder exist? 2] did the last "scheduled" backup work? 3] do you have space allocated for VSS? 4] is the volume idle (more or less) while you are doing the backup? Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael Link with me at: http://www.linkedin.com/in/theessentialexchange From: Rob Bonfiglio [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2008 5:59 PM To: NT System Admin Issues Subject: Re: Server Core and Windows Server Backup Unfortunately this didn't change a thing. On Mon, Sep 22, 2008 at 5:43 PM, Rob Bonfiglio <[EMAIL PROTECTED]> wrote: I'm doing that as we speak actually....realized that was the one thing I hadn't removed yet. Just removing the DPM agent didn't do anything for me. So, while the DPM agent is uninstalled I am removing the feature, rebooting, and then will reinstall the backup feature. I'll let ya know if I have any luck. Thanks for the suggestion. On Mon, Sep 22, 2008 at 5:25 PM, Michael B. Smith <[EMAIL PROTECTED]> wrote: Have you tried removing the dpm agent? Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael Link with me at: http://www.linkedin.com/in/theessentialexchange From: Rob Bonfiglio [mailto:[EMAIL PROTECTED] Sent: Monday, September 22, 2008 4:55 PM To: NT System Admin Issues Subject: Server Core and Windows Server Backup I am having trouble getting Windows Server Backup to run properly on all 3 of my 2008 Server Core installations. Initially I had installed the Backup Exec remote agent on the machines, but we are moving to DPM. I installed the DPM agent on the machines, and installed the Windows Server Backup feature, but I wasn't getting a backup of my system state. So, I went to the machines to try and use wbadmin to do a local system state backup to see if I could perform one apart from DPM. Here is the syntax I am using, and the error message that is given back to me: ---------------------------------------------------------------- E:\>wbadmin start systemstatebackup -backupTarget:e:\Backup The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. ---------------------------------------------------------------- I get the same error if I attempt to perform the backup from the C: drive (to the folder on the E: drive.) I uninstalled the Symantec remote agent using MSIExec. I uninstalled the WindowsServerBackup role, rebooted, installed the role, rebooted, and tried running the above command again, yet I still have the same result. To install the feature I simply entered: ---------------------------------------------------------------- start /w ocsetup WindowsServerBackup ---------------------------------------------------------------- Looking in the event logs I see where the Block level backup engine service successfully started. After about 5 minutes the event logs show that the BLB service successfully stops. If I look at the services, I see the BLB service is set to manual. Before I run the wbadmin command the service is stopped. After I run it the service starts. I get no errors related to the backup in the event logs beyond what the program spits back out to me (see above.) Has anyone had any similar problems? Any suggests, or care to point out anything obviously stupid that I have done so far? ;-) Thanks for any help! Rob ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
