Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

This forum supports questions for the default backup utility in Windows Vista, Server 2008 and beyond. For questions on NTBackup or Windows Server 2003/XP, please use the “File services and storage" forum.

older | 1 | .... | 54 | 55 | (Page 56) | 57 | 58 | .... | 148 | newer

    0 0
  • 09/02/14--05:55: windows 2008 r2 backup
  • Hi,

         i have running windows server backup 2008 r2 to external drive since from 2012.  the functionality is good and normal.

    but last 3 days back i have cleared some GB of data from the backup folder list then backup ran successfully.

    after that i am trying to restore some data of previous dates i couldn't see older backup date of present hard disk on recover wizard.but i can see the older backup dates of previous hard disk.

    Further more i found the log on the windows for the recent dates.but i can't see older backup dates in recover wizard.

    Please any one help on this if you have any solution for this.

     


    0 0

    Hi,

    Recently setup a brand new 2012 R2 server, using hyper v to host 3 VM's, backing up with backup exec 2014.The backups are failing, backup exec stating...

    V-79-40960-38521 - Snapshot Technology: Initialization failure on: "VRTSRV::\\UKBNHV01.ProCam.local\Hyper-V?Virtual?Machine\UKBNDC01". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).A virtual machine snapshot could not be created. Use the Event Viewer on the Hyper-V host to identify the cause. If the virtual machine is not properly configured, it may be necessary to use the Event Viewer in the virtual machine to identify the cause.

    Looking at the Hyper V VMMS event viewer I get the error:

    VSS writers inside virtual machine 'UKBNIT01' failed to perform BackupComplete to its shadow copy (VSS snapshot) set: Catastrophic failure (0x8000FFFF). (Virtual machine ID 7C31CD39-FFAD-4E04-BF92-223BC120BE1B) event ID 10172

    I see there are other posts relating to this, with random answers suggesting fixes relating to disk speeds and all sorts. If i restart the hyper v's and physical server the backup will run maybe 2 or 3 times successfully before failing again. Clearly buying a server to restart it every 2 days isn't an option.

    It seems apparent this isn't just a problem relating to server 2012 R2, but has carried across in all newer versions of windows server.

    My Vss Writers list as follows:

    Microsoft Windows [Version 6.3.9600]
    (c) 2013 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>vssadmin list writers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Writer name: 'Task Scheduler Writer'
       Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
       Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
       State: [1] Stable
       Last error: No error

    Writer name: 'VSS Metadata Store Writer'
       Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
       Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
       State: [1] Stable
       Last error: No error

    Writer name: 'Performance Counters Writer'
       Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
       Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
       State: [1] Stable
       Last error: No error

    Writer name: 'System Writer'
       Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Instance Id: {89a328b7-87eb-48e2-a3e6-9d04b164ba32}
       State: [1] Stable
       Last error: No error

    Writer name: 'Microsoft Hyper-V VSS Writer'
       Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
       Writer Instance Id: {baa1e068-a50f-4d2e-898c-a54920ae4117}
       State: [8] Failed
       Last error: Retryable error

    Writer name: 'BITS Writer'
       Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
       Writer Instance Id: {4986e692-ea2c-454e-813e-9e5f71854adf}
       State: [1] Stable
       Last error: No error

    Writer name: 'SqlServerWriter'
       Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
       Writer Instance Id: {f7f18f2b-660b-4e18-9aa1-5caa5115045e}
       State: [1] Stable
       Last error: No error

    Writer name: 'ASR Writer'
       Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
       Writer Instance Id: {bfa584a7-72b3-47c1-90d7-87e71074e875}
       State: [1] Stable
       Last error: No error

    Writer name: 'Shadow Copy Optimization Writer'
       Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
       Writer Instance Id: {954a91e4-8c93-4f21-9ceb-53f2df3fefc5}
       State: [1] Stable
       Last error: No error

    Writer name: 'Registry Writer'
       Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
       Writer Instance Id: {a254fab5-d160-4a2d-9f8f-e43e7ea0708e}
       State: [1] Stable
       Last error: No error

    Writer name: 'COM+ REGDB Writer'
       Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
       Writer Instance Id: {d01d076a-aa1b-4998-8a5b-91b993895405}
       State: [1] Stable
       Last error: No error

    Writer name: 'WMI Writer'
       Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
       Writer Instance Id: {1e7cb515-f73d-4146-838d-74605a77628c}
       State: [1] Stable
       Last error: No error

    Is anyone able to explain how to trace why the Hyper-V VSS Writer gets the retryable error?

    Thanks

    Nick



    0 0

    I have a fresh install of Windows Server 2012 R2 on an IBM x3530 M4 server.  I'm trying to do a full bare metal backup to a local volume, which is presented from a SAN.

    The backup fails stating that there isn't enough disk space.  This is very misleading as the OS on the C:\ is only taking up 15GB and the free Space on the SAN volume is 800GB.

    From doing a little reading online i have found others who have had problems backing up Recovery Partitions, click here.  So i just did a backup of the C:\ to the same SAN volume and that works fine so i have a feeling this is something to do with the Recovery Partition.  I also have a partition which is called the EFI System Partition which i'm unsure what this is.  Below is a screen grab of the Disk Management on the system.  Can someone give me a way to do a full Bare Metal backup without having to reinstall the whole OS.  Thanks


    0 0

    Hi folks,

    We are running into issues when attempting to configure a Windows Backup schedule through either running the Backup Schedule wizard or through using the wbadmin utility. While I have previously posted this issue on a separate forum (with no luck) I’ve restructured this description based on the responses received and am also hoping that this a more suitable forum for the problem we are experiencing.

    On running the backup wizard the backup configuration screen shows the backup size to be 0KB for the Full Server option or if I choose ‘Custom’ and go to ‘select backup items’ the volume list is empty. However the later ‘select destination disk’ screen of the wizard lists all of the disks attached to the server along with the associated volume letters (via clicking the ‘Show All Available Disks’ option).

    On the backup wizard reaching the summary stage it then proceeds to format the destination disk. On completion of this format the wizard status then changes to ‘Creating backup schedule’ at which point it then fails with the message “The specified number of volumes is invalid”.

    Equally running the following wbadmin command:

    wbadmin ENABLE BACKUP -addtarget:{81737a1c-0000-0000-0000-000000000000} -schedule:21:00 -include:c:

    Results in the following error:

    “ERROR - One of the source volumes specified cannot be included: c: Please specify source as a volume drive letter or access path (if volume is mounted in a folder). Only volumes on locally attached disks can be backed up.”

    The server is a Dell PowerEdge R620 running Windows server 2008SP2 and is operating as expected other than for this windows back issue. Everything appears as normal when I view the disks within the Disk Management Console. Backups used to run on this server fine before it was migrated from old hardware to new hardware using Doubletake Move. Everything else is running fine since the migration apart from Windows backup so not why it would only be effecting Windows backup. I have also ran the wbadmin ‘delete catalog’ command to remove reference to the previous backups that were taken.

    Is there any other tests that I can run to determine why Windows backup is having trouble seeing the available volumes at the 'Select Backup items' stage but not at the Select Destination' stage? Any help or pointers in the right direction would be very much appreciated.

    Thanks,

    Niall



    0 0

    Dear sir/madam


    we have window 7 Operating system  . but we have one Domain server .

    all user are domain controller  users . how to know domain control user file transfer history .

    how to know domain control user file transfer to external device (pen drive ) history .

    Problem : one person the transfer data to pen drive .. but i know this matter but i want to see in my server ..

    please help me ...

    Thank you


    0 0

    Dear team

    we are having 2 disks (like Disk 0 and Disk1)  in windows server 2003 by using IM magic partition tool i extended disk 1 space  now unallocated space is available on disk 1 is  30GB, now how to extend  unallocated space to disk 0  on C drive,without losing Data

    please suggest on this please 



    0 0

    how taking a full image from windows server (that holding any product (active directory & exchange & lync & System center family ...........etc))

    i mean as i can back up for example windows xp & 7  by Norton ghost which i can restore by booting using ghost and recover

    Thanks in advance


    0 0

    Hi,

    When running either a scheduled back or a once off backup, I receive the following error around 30 seconds into the backup:

    "The Windows Server Backup service has stopped"

    "A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: The Windows server Backup service has stopped"

    In event viewer the following two events were logged:

    Faulting application name: wbengine.exe, version: 6.1.7601.17514, time stamp: 0x4ce79951
    Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c4102
    Faulting process id: 0x13e8
    Faulting application start time: 0x01cfa9f0936b235a
    Faulting application path: C:\Windows\system32\wbengine.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: e99a55c8-15e4-11e4-9ab5-a01d48c77640


    The Block Level Backup Engine Service service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

    I have tired restarting the Block Level Backup Engine Service service, deleting the backup catalogue, removing and re adding Window Server Backup feature. None of these fixed the problem

    Any help would be greatly appreciated.



    0 0

    

    HI,

    I have One tape & monthly taking normal backup of my files.Today i am trying to take backup i got a message that media full insert the new media or press cancel the current job....So i press cancel..

    Now I want restore the previous back up files..when i insert the tap i am getting below image error

    OS : Windows 2003 Server : LTO-4 Ultrium RW data cartridge.

    Thank you all...




    0 0
  • 08/23/14--06:44: Windows backup not working
  • Hi,

    I'm trying to run a windows backup but it's failing with the following error.

    Server specification: " Microsoft web server 2008 R2 sp1"

    Error showing in backup tool: "The operation was stopped Detailed error The system writer is not found in the backup"

    Error in event logs: Two events one with even 8193(total four entries) and one event with ID 517

    errors: Volume Shadow Copy Service error: Unexpected error calling routine XML document is too long.  hr = 0x80070018, The program issued a command but the command length is incorrect.

    Volume Shadow Copy Service error: Unexpected error calling routine CreateVssExamineWriterMetadata.  hr = 0x80042302, A Volume Shadow Copy Service component encountered an unexpected error.
    Check the Application event log for more information.

    The backup operation that started at '‎2014‎-‎08‎-‎23T13:00:09.593737300Z' has failed with following error code '2155347997' (The operation ended before completion.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    --

    Running "vssadmin list writes" list some writes and all of them showing "no error".

    Could somebody help me on this?

    Regards,


    Jaf




    0 0

    Our primary DPM server keeps shutting down unexpectedly with a BSOD error: BAD_POOL_HEADER caused by volsnap.sys+4dfd. All drivers are up-to-date and im not sure how to tackle this and stop it from happening since it's interfering with our backup jobs.  Please let me know if a mini dump file is needed to further investigate.  All help is appreciated.  

    0 0

    Our backups on our virtual windows server 2012 R2 which is hosted on Hyper-V server 2012 R2 have been taking at least 3 hours longer than they used to.
    We use windows Server Backup for nightly backups which backs up to a local volume. We also use a powershell script for the weekly backup which also runs through wbadmin and backs up to a network share. 
    A couple weeks ago the backups started taking 3-5 hours longer.  I monitored them and noticed that they have been taking hours to compact the virtual hard disks at the end of the backups.
    I refereed to the following link about this process and it should not be happening for every backup.
    http://support.microsoft.com/kb/2524602/en-us

    We installed windows updates after this problem began but its is still happening for every backup.

    What can we do to stop this?




    0 0

    • three node Server 2012 R2 cluster
    • 2 CSVs
    • Veeam Backup software v7

    We've been running out of space on our CSVs. I determined that the hidden System Volume Information directory is huge. It is huge because of large VSS files in the directory.

    Path to CSVs

    c:\ClusterStorage\Volume1

    c:\ClusterStorage\Volume2

    ===========================================================================

    List of VSS providers

    vssadmin list providers
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Provider name: 'SmVssProvider'
       Provider type: Hardware
       Provider Id: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}
       Version: 11.10.0001

    Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
       Provider type: Software
       Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
       Version: 1.0.0.1

    Provider name: 'Microsoft CSV Shadow Copy Provider'
       Provider type: Software
       Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
       Version: 1.0.0.1

    Provider name: 'Microsoft File Share Shadow Copy provider'
       Provider type: Fileshare
       Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
       Version: 1.0.0.1

    Provider name: 'Microsoft Software Shadow Copy provider 1.0'
       Provider type: System
       Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
       Version: 1.0.0.7
    ===========================================================================

    Vssadmin list shadowstorage doesn't reference the location of my CSVs...

    PS C:\Windows\system32> vssadmin list shadowstorage
    vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
    (C) Copyright 2001-2013 Microsoft Corp.

    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{6bf32257-eccb-11e3-80b5-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{6bf32257-eccb-11e3-80b5-806e6f6e6963}\
       Used Shadow Copy Storage space: 0 bytes (0%)
       Allocated Shadow Copy Storage space: 0 bytes (0%)
       Maximum Shadow Copy Storage space: 13.6 GB (10%)

    ============================================================================


    PS C:\clusterstorage\volume1> mountvol
    Creates, deletes, or lists a volume mount point.

    MOUNTVOL [drive:]path VolumeName
    MOUNTVOL [drive:]path /D
    MOUNTVOL [drive:]path /L
    MOUNTVOL [drive:]path /P
    MOUNTVOL /R
    MOUNTVOL /N
    MOUNTVOL /E

        path        Specifies the existing NTFS directory where the mount
                    point will reside.
        VolumeName  Specifies the volume name that is the target of the mount
                    point.
        /D          Removes the volume mount point from the specified directory.
        /L          Lists the mounted volume name for the specified directory.
        /P          Removes the volume mount point from the specified directory,
                    dismounts the volume, and makes the volume not mountable.
                    You can make the volume mountable again by creating a volume
                    mount point.
        /R          Removes volume mount point directories and registry settings
                    for volumes that are no longer in the system.
        /N          Disables automatic mounting of new volumes.
        /E          Re-enables automatic mounting of new volumes.

    Possible values for VolumeName along with current mount points are:

        \\?\Volume{6bf32256-eccb-11e3-80b5-806e6f6e6963}\
            *** NO MOUNT POINTS ***

        \\?\Volume{6bf32257-eccb-11e3-80b5-806e6f6e6963}\
            C:\

        \\?\Volume{bd46bae7-015c-4115-88ca-e6e9067fdea1}\
            C:\ClusterStorage\Volume2\

        \\?\Volume{caf6938a-5faa-4f3b-8e2b-e27d1498dedf}\
            C:\ClusterStorage\Volume1\

        \\?\Volume{6bf3225c-eccb-11e3-80b5-806e6f6e6963}\
            D:\

    ====================================================================



    0 0

    Hi

    We are using Windows server 2008 R2.The hard drive c is going to full .We didn't installed any extra software in the server.The Kaspersky endpoint security 8 is installed in the server.It doesn't occupy a lot of space in the server.

    Day by day c drive is keep on increasing and it is going to full within two weeks.We had already added 500 GB hard drive extra.The total size of the hard drive in the server is 1 tb.

    1TB is also going to full in hard drive c.Because of this,i am not downloading the windows updates.

    Please let me know why the Hard drive c is day by day increasing full and also within a week the c drive is going to full.

    Please guide/suggest me how to stop the hard drive c going to full in the server.I want to stop the hard drive c going to full.

    Your support is highly appreciated.

    Regards

    Pradeep


    0 0

    I have a PowerEdge T110 running Windows Server 2008 R2 Foundation.  I use the Backup feature built into Windows to create a Full backup of the machine.  When I restore this backup to a different Hard Drive, the machine starts, it passes the startup splash screen, a cursor appears, then the machine restarts.   I have used several other backup programs to clone the machine, but I have the same results.    I have used other Windows Server machines without issue.  Does Dell put an overlay on the drive?   What could be causing this issue, and how can I resolve it.   Thanks in advance.

    0 0

    Running Windows Server 2012 Essentials with an external usb 3 drive as a backup device.  Using a Vantec hx enclosure with a WD Red drive. Last night the Dashboard saw the drive with about half the 4TB available for backup. A.M., I get "error code: 2147942403 The system cannot find the path specified".

    Going to the server desktop, I see a message indicating that the usb device malfunctioned.  unplugging it, and plugging it back in, I now have it available via the dashboard.

    This has happened a couple times with two different drives in Vantec hx enclosures.

    A couple possibilities come to mind:

    1. the enclosures may both be bad...
    2. there is some problem with the system software and external usb drive.

    Thoughts?

    Suggestions for external enclosures?

    Thanks!


    0 0

    Have a Windows 2012 Server with a scheduled backup Job to a local attached USB disk. The job is running for months without Errors. The disk is about 30% full. Despite that, I have only 12 generations of backups:

    According my understanding, Windows Backup should fill up the disk with backups and start to delete older backups only when there is insufficient disk space.

    Any advice? Are these "12 copies" configurable?

    Thank you all in advance for any help

    Franz


    0 0
  • 09/13/14--22:57: Import & Export of VMs.
  • If i import a VM from one forest and export it to other forest then how virtual switch and DHCP work for this?

    0 0

    Replaced the hard drive in my Dell 1545 laptop with a Samsung SSD 840 EVO.

    Everything beautiful.

    Am running Windows 8.1 - again everything beautiful.

    Thought I would run "System Image Backup" (off the File History page).

    failed - Microsoft error code 0x80780119

     because Samsung Migration tool created a first partition labeled "data"
    (don't know whose data this might be suspect it has nothing to do with the OS but is required for the SSD, perhaps for MBR boot purposed.)

    This "data" partition is very small and 99% full: no room for the VSS backup requires.

    Bypassed that problem with:

    PS C:\> wbAdmin start backup -backupTarget:H: -include:C:\

    which runs perfectly, except for the warning,

    " Note: the list of volumes included for backup does not include all the volumes that contain operating system components. This backup cannot be used to perform a system recovery. However. you can recover other items if the destination media type Supports it."



    0 0
  • 09/13/14--03:58: back up CA server
  • Hello,

    We have PKI infrastructure in our environment which consists of one Root CA server and 4 issuing CA servers. We are taking regular system state back of CA server and weekly backup of CA database. In case in future if any/all of the servers are crashed and have to build it again from backup, upto what extent the backup we are taking is helpful? will I be able restore all?

    What the ideal backup strategy for CA servers?


    Mahi


older | 1 | .... | 54 | 55 | (Page 56) | 57 | 58 | .... | 148 | newer