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 | .... | 37 | 38 | (Page 39) | 40 | 41 | .... | 148 | newer

    0 0
  • 03/10/14--02:27: Windows Backup After Reboot
  • Hello,
    I have a problem with Windows Backup on Windows Server 2012 R2. I'm using Windows Backup for backing up my Hyper-V virtual machines and "Host Component". I'm using planned backup with dedicated external harddrive. Everything works fine, until I reboot host server. After reboot, backup stops working with error code 0x80780049. What helps is deleting and recreating planned backup job, but I can't recreate backup jobs on every Hyper-V host after every reboot. Has someone an idea what can cause this?

    Thank you..


    0 0

    I have taken over in a new role and found that while backups were being conducted on a regular basis, the backup solution was not VSS aware and almost 1TB of log files had accrued since Exchange was installed in 2011!

    I have implemented the use of the Windows Server Backup utility on the Windows 2008 R2 server that hosts Exchange 2010.

    After verifying that I had achieved consistency within the mail databases, I scheduled a Full VSS Backup to run every night to a series of externally attached USB hard drives, and was happy to see that each days Exchange log files are now being flushed after each back up.

    However, when reviewing the backup reports within Windows Server backup utility, I note that each backup following the initial FULL backup to each hard drive is referred to as Incremental? I was under the impression that in specifying a VSS FULL Backup, any existing backup found within the WindowsImageBackup folder on the backup media would be overwritten in it's entirety but it seems that the existing Full backup is instead being 'modified' by each subsequent backup?

    Also, the collective size of the .vhd files created on the backup media is significantly larger than the space shown within Windows Explorer as 'used' on each of the volumes backed up?

    Could someone please explain these apparent anomalies? - Thanks




    0 0

          Our company uses Windows Server Backup to back up our Windows 2012 Server.  We back up the host component and the two virtual machines on the server.  Every time I install windows updates on our server my backup jobs stop working and I get a VSS error.  In order to get backup working again, I have to recreate my backup job.  In order to do this I have to attach all the backup drives to the computer at the same time.  This has been an issue all the way back to when the server was first installed.  At that time the person who installed Windows Server talked to Microsoft.  Microsoft said the problem would be fixed in the first service pack which they ended up never releasing.  I have looked online, but haven’t found any information on these issues.  Are there any fixes for these two problems?


    0 0

    Hi there,

    I have recently configured a server to run a normal scheduled backup from one internal HDD to a second internal HDD with no problem.

    I then created a secondary backup from the first internal HDD to an external USB HDD via the task scheduler which initially worked for the first two backups, creating an incremental copy of the correct files.

    The third day it tried to backup at the scheduled time of 2am, it failed and has continued to fail ever since - the error reports "Failed to create directory". This external backup drive has not been modified, not been disconnected and reconnected, is used for nothing else but these simple backups.

    In short, the scheduled backup is meant to copy a folder from C: drive to the E: drive (the external) at 2am each day of the week. ie C:\Folder -> E:

    I have viewed all of the guides on creating scheduled backups with task scheduler and know the syntax well enough so literally have no idea why all of a sudden they have stopped. There is more than adequate space on the drive - approx 30GB being copied to a 500GB drive.

    If someone would be able to give me an idea or provide me with a task schedule command to create this backup that would be excellent.

    Assuming that incremental backups are the only option - is it possible to create full entire backups each time? Following on from that - once the destination drive is full am I right in assuming Windows Server 2012 would be smart enough to delete the oldest data and continue to back up?

    Kind Regards,

    Ewan


    0 0

    Would like to ask

    let's say if I currently have C:/100GB , E: 200GB,RAID 1

    I wish to restore a image from windows server backup which is C:233GB ,E:100GB,RAID 1 , Bare metal recovery,System State, EFI System Partition.

    Provided the hard disks are the same, can I restore this image?



    0 0
  • 04/04/14--02:00: windows azure
  • how will i get the subscriptions of windows azure.I have already have accounts

    0 0

    I'm doing our normal Clonezilla Backup procedure and ran out of disk space for the first time.  The normal person who does this is on vacation.  I put the new hard drive in for the backup, but when I ran Clonezilla it didn't recognize it.  I looked in Server Manger and it shows it as Unknown with a red arrow and not initialized.  It's shown as unallocated.  What do I need to do at this point?  Do you have instructions or a link to instructions?  I'm new to working with servers, etc.  I probably need to format the new external drive but I'm not sure how.  This is a simple server, without VM's, etc.

    Thanks!


    0 0
  • 04/06/14--06:41: Third-party backup software
  • Hello,

      I have just read that you can restore Windows 2008 to a different hardware, like Windows 7.

      I was wondering: Is there the need of third-party software anymore?. I mean, you just backup the whole system in a network share or a san volume or elsewhere (outside the 2008 box), and that is that, no Acronis anymore.

      Am I missing something?. To me, it looks so great.

    Thanks in advance!


    Luis Olías Técnico/Admon Sistemas . Sevilla (España - Spain)


    0 0

    The Volume Shadow Copy service initially was running under the context of System, so we thought that ‘System’ doesn’t have permissions to access network shares. When the Volume Shadow Copy service was running under the context of System, this was the error logged:

    “failed with following error code '0x8078014B' (There was a failure in creating a directory on the backup storage location.).”

    Which is likely due to not having permissions to write to the network location.  This is a scheduled backup trying to write to a network location, so we changes the service to run under the context of an account that does have permissions to write to the network share.  Then the error changed to this:

    “failed with following error code '0x8078006B' (Windows Backup failed to create the shared protection point on the source volumes.).”

    HRESULT 0x8078006b
    DetailedHRESULT 0x8004230f
    ErrorMessage %%2155348075
    BackupState 12
    VolumesInfo <VolumeInfo><VolumeInfoItem Name="C:" OriginalAccessPath="C:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="1" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="1604" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /><VolumeInfoItem Name="D:" OriginalAccessPath="D:" State="15" HResult="-2139619228" DetailedHResult="0" PreviousState="0" IsCritical="0" IsIncremental="0" BlockLevel="0" HasFiles="1" HasSystemState="0" IsCompacted="0" IsPruned="0" IsRecreateVhd="0" FullBackupReason="0" DataTransferred="0" NumUnreadableBytes="0" TotalSize="0" TotalNoOfFiles="0" Flags="68" BackupTypeDetermined="0" SSBTotalNoOfFiles="0" SSBTotalSizeOnDisk="0" /></VolumeInfo>

    We aren’t really seeing anything that gives any hint on what the issue is. Any ideas?  Thanks in advance!


    0 0

    When will Microsoft rais this Limit.

    With this Limit you can´t install Windows 2012, SQL 2012, SharePoint 2013 on a single machine.

    A systemstate backup will not be possible anymore?


    0 0

    I get an error trying to configure backup on Server 2012 Essentials - only volumes formatted with NTFS/ReFS can be protected.

    I checked disk management and see a Fat32 drive called OS - it this safe to delete or format NTFS? It is a 2GB Partition that I believe shipped with the server from Dell. If I remove or reformat would I be able to configure the backup?

    I checked 3 other WS2012E that I support and none have an FAT32 partitions and the backup setup works great.


    0 0

    Hi, trying to backup system image using SCDPM 2010 RTM.Most of the server are getting healthy backups except for this one server which is giving error:

    Affected area:	Computer\System Protection
    Occurred since:	1/27/2014 2:43:27 PM
    Description:	The replica of System Protection Computer\System Protection on server.DOMAIN.COM is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent. 
    
    For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
    	DPM cannot create a backup because Windows Server Backup (WSB) on the protected computer encountered an error (WSB Event ID: 517, WSB Error Code:  0x80070057). (ID 30229 Details: Internal error code: 0x809909FB)
    	More information
    Recommended action:	For resolution actions and more information on the WSB error, go to http://technet.microsoft.com/en-us/library/cc734488(WS.10).aspx.
    	Synchronize with consistency check.
    	Run a synchronization job with consistency check...
    Resolution:	To dismiss the alert, click below
    	Inactivate alert

    On the server, event viewer show the following events:

    1. Backup Log:

    Backup started at '2014-01-27T11:26:21.356950100Z' failed with following error code '2147942487'.

    2. Application Log:

    The description for Event ID 517 from source Microsoft-Windows-Backup cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    
    If the event originated on another computer, the display information had to be saved with the event.
    
    The following information was included with the event:
    
    27-Jan-14 11:26:21 AM
    2147942487
    %%2147942487
    
    The resource loader failed to find MUI file


    However, when I observe the backup process using "wbadmin get status", it reaches 99% then stops.

    Running backup of volume Local Disk(C:), copied (97%).
    Running backup of volume Local Disk(C:), copied (98%).
    Running backup of volume Local Disk(C:), copied (99%).
    
    Backup stopped before completing.
    
    Summary of backup:
    ------------------
    
    
    Backup stopped before completing.
    The parameter is incorrect.

    The server hardware is HP blade with two disk which are mirrored, and has 12 GB free space. below is the output from systeminfo command:

    Host Name:                 server
    OS Name:                   Microsoftr Windows Serverr 2008 Enterprise 
    OS Version:                6.0.6002 Service Pack 2 Build 6002
    OS Manufacturer:           Microsoft Corporation
    OS Configuration:          Member Server
    OS Build Type:             Multiprocessor Free
    Registered Owner:          Admin
    Registered Organization:   -
    Product ID:                55041-339-7818202-76771
    Original Install Date:     04-Aug-08, 3:15:18 PM
    System Boot Time:          21-Jan-14, 3:58:47 PM
    System Manufacturer:       HP
    System Model:              ProLiant BL460c G1
    System Type:               x64-based PC
    Processor(s):              2 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
                               [02]: Intel64 Family 6 Model 23 Stepping 6 GenuineIntel ~3000 Mhz
    BIOS Version:              HP I15, 02-May-11
    Windows Directory:         C:\Windows
    System Directory:          C:\Windows\system32
    Boot Device:               \Device\HarddiskVolume1
    System Locale:             en-us;English (United States)
    Input Locale:              en-us;English (United States)
    Time Zone:                 (GMT+03:00) Kuwait, Riyadh
    Total Physical Memory:     16,381 MB
    Available Physical Memory: 8,320 MB
    Virtual Memory: Max Size:  21,821 MB
    Virtual Memory: Available: 13,722 MB
    Virtual Memory: In Use:    8,099 MB
    Page File Location(s):     C:\pagefile.sys
    Domain:                    DOMAIN.COM
    Logon Server:              N/A
    Hotfix(s):                 157 Hotfix(s) Installed.
                               [01]: {47740627-D81D-4A45-A215-03B075A18EC7}
                               [02]: {3D019598-7B59-447A-80AE-815B703B84FF}
                               [03]: {A8E86480-A9C1-4414-8AA2-B05A485C82F0}
                               [04]: {C444285D-5E4F-48A4-91DD-47AAAA68E92D}
                               [05]: {DB33A524-845E-4855-9E90-A5619BCDD527}
                               [06]: {ECC3A660-90E3-4A89-9FE8-F8B3C633B12E}
                               [07]: {65AFCB03-3111-47E2-B1ED-198D6B0BC96E}
                               [08]: {F5E29D9D-519A-36C7-87E3-9A22A8180B1B}
                               [09]: KB971513
                               [10]: KB971512
                               [11]: 944036
                               [12]: 982861
                               [13]: KB960362
                               [14]: KB2079403
                               [15]: KB2117917
                               [16]: KB2141007
                               [17]: KB2160329
                               [18]: KB2183461
                               [19]: KB2207566
                               [20]: KB2286198
                               [21]: KB2296011
                               [22]: KB2296199
                               [23]: KB2305420
                               [24]: KB2345886
                               [25]: KB2347290
                               [26]: KB2387149
                               [27]: KB2388210
                               [28]: KB2416400
                               [29]: KB2416470
                               [30]: KB2419640
                               [31]: KB2423089
                               [32]: KB2436673
                               [33]: KB2442962
                               [34]: KB2443685
                               [35]: KB2447568
                               [36]: KB2467659
                               [37]: KB938464
                               [38]: KB942288
                               [39]: KB948609
                               [40]: KB948610
                               [41]: KB949189
                               [42]: KB950762
                               [43]: KB950974
                               [44]: KB951066
                               [45]: KB951698
                               [46]: KB951978
                               [47]: KB952004
                               [48]: KB952287
                               [49]: KB953733
                               [50]: KB954155
                               [51]: KB954459
                               [52]: KB955020
                               [53]: KB955069
                               [54]: KB955302
                               [55]: KB955430
                               [56]: KB955839
                               [57]: KB956250
                               [58]: KB956572
                               [59]: KB956744
                               [60]: KB956802
                               [61]: KB957097
                               [62]: KB957200
                               [63]: KB957321
                               [64]: KB957388
                               [65]: KB958481
                               [66]: KB958483
                               [67]: KB958623
                               [68]: KB958624
                               [69]: KB958644
                               [70]: KB958687
                               [71]: KB959130
                               [72]: KB959426
                               [73]: KB960225
                               [74]: KB960803
                               [75]: KB961371
                               [76]: KB961501
                               [77]: KB967190
                               [78]: KB967723
                               [79]: KB968389
                               [80]: KB968537
                               [81]: KB969058
                               [82]: KB969897
                               [83]: KB969897
                               [84]: KB969947
                               [85]: KB970238
                               [86]: KB970430
                               [87]: KB970653
                               [88]: KB971468
                               [89]: KB971486
                               [90]: KB971557
                               [91]: KB971657
                               [92]: KB971737
                               [93]: KB971930
                               [94]: KB971961
                               [95]: KB972036
                               [96]: KB972270
                               [97]: KB972636
                               [98]: KB973346
                               [99]: KB973507
                               [100]: KB973525
                               [101]: KB973565
                               [102]: KB973687
                               [103]: KB973917
                               [104]: KB974145
                               [105]: KB974318
                               [106]: KB974455
                               [107]: KB974470
                               [108]: KB974571
                               [109]: KB975364
                               [110]: KB975467
                               [111]: KB975517
                               [112]: KB975560
                               [113]: KB975759
                               [114]: KB975929
                               [115]: KB976098
                               [116]: KB976264
                               [117]: KB976470
                               [118]: KB976662
                               [119]: KB976749
                               [120]: KB976768
                               [121]: KB976772
                               [122]: KB977165
                               [123]: KB978251
                               [124]: KB978262
                               [125]: KB978542
                               [126]: KB978601
                               [127]: KB978886
                               [128]: KB979099
                               [129]: KB979306
                               [130]: KB979309
                               [131]: KB979482
                               [132]: KB979687
                               [133]: KB979688
                               [134]: KB979899
                               [135]: KB979910
                               [136]: KB980182
                               [137]: KB980195
                               [138]: KB980218
                               [139]: KB980232
                               [140]: KB980248
                               [141]: KB980302
                               [142]: KB980436
                               [143]: KB980842
                               [144]: KB981322
                               [145]: KB981332
                               [146]: KB981793
                               [147]: KB981852
                               [148]: KB982132
                               [149]: KB982214
                               [150]: KB982519
                               [151]: KB982664
                               [152]: KB982666
                               [153]: KB982799
                               [154]: KB983589
                               [155]: KB948465
                               [156]: KB960568
                               [157]: KB968930
    Network Card(s):           1 NIC(s) Installed.
                               [01]: HP NC373i Multifunction Gigabit Server Adapter
                                     Connection Name: Local Area Connection 2
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: x.x.x.x
                                     [02]: fe80::f494:43c2:7d90:e774
    Hyper-V Requirements:      VM Monitor Mode Extensions: No
                               Virtualization Enabled In Firmware: No
                               Second Level Address Translation: No
                               Data Execution Prevention Available: No

    Things I have tried:

    1. I tried to backup manually to external HDD using wsb snap-in, but it has failed in the same way.

    2. Stop and re-add protection.

    3. I have researched the error, some results suggest that some bad sectors might exist, however, when I run the command, it forces me to schedule the command on next boot. when I reboot, it loads windows after that gives a message "Cannot open the volume for direct access"

    How to end this loop? please help. Thanks for considering my question ...



    0 0

    Environment:

    Windows Server 2012 R2 Essentials running in VirtualBox in a Windows 7 host. Networking is configured and works fine.

    Background:

    My only backup needs are to copy the contents of two folders to a NAS folder every day at 2 AM.

    I configured a backup schedule in Windows Server Backup (wbadmin) to a network location which is hosted as a Samba share on a Synology NAS.

    For authentication, I created a backup user which has the same username and password as a user on the Samba share, with permission to read and write the backup folder. I added this user to the Backup Operators group.

    Problem:

    When I try to run the Backup Once operation to test my backup, I get the following error message:

    "Windows Backup cannot read the backup destination."

    What I've tried:

    I verified that the location is directly accessible in Windows by copying and pasting the address from the Windows Server Backup destination into explorer. Providing the backup user credentials opened the location and creating/reading files worked fine.

    Adding the backup user to the Administrators group did not have an effect.

    Update 2014-02-18

    I checked the backup destination and was surprised to find that the scheduled backup actually completes successfully.However, Backup Once always results in the above error message. So the problem is confined to the "Backup Once" operation.



    0 0

    Server 2008 R2 running Terminal services Hangs  users 12 pm every day

    event logs only show Shadow service running at that time

    is there a way to stop it running at 12pm

    only time the system users it for the backup program Shadow Protect is after 5pm everyday


    0 0

    Hi,

    after last reboot I'm unable to backup our server which is runing latest version of Windows Server 2012. I'm getting this error everytime I try to backup C: or FULL backup:

    The backup operation that started at '‎2013‎-‎02‎-‎18T07:45:12.353531000Z' has failed with following error code '0x8007000D' (The data is invalid.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.

    Log file in windows\logs\WindowsServerBackup\ is empty. I'm unable to get more details even with VSS.ETL debugging. Can somebody help me?

    Thank you


    0 0

    Hello,

    I have a Problem when I try to make Backups to Partition C in Windows Server 2008 R2:Error The Data is Invalid.

    Obs: I can make backups for System Reserved Partition .

    I had the same problem 2 months ago (the data is invalid), Then I folowed this the advice to delete "Framework64\v2.0.50727\Temporary ASP.NET Files" and worked for me , from this post: http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/89052b85-9c9b-479f-ab76-a20da3cc4696

    Now I have the same problem and I delete the Temporary ASP.NET Files , but it is not working , I received the same error on backup:

    "The backup operation that started at '‎2012‎-‎09‎-‎20T07:13:26.024163900Z' has failed with following error code '2147942413'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."

    When I try vssadmin list writers, Everything is ok , "No error" .

    I tried to run :

    net stop "System Event Notification Service"
    net stop "COM+ Event System"
    net stop "Microsoft Software Shadow Copy Provider"
    net stop "Volume Shadow Copy"
    cd /d %windir%\system32
    net stop vss
    net stop swprv
    regsvr32 /s ole32.dll
    regsvr32 /s oleaut32.dll
    regsvr32 /s vss_ps.dll
    vssvc /register
    regsvr32 /s /i swprv.dll
    regsvr32 /s /i eventcls.dll
    regsvr32 /s es.dll
    regsvr32 /s stdprov.dll
    regsvr32 /s vssui.dll
    regsvr32 /s msxml3.dll
    net start "System Event Notification Service"
    net start "COM+ Event System"
    net start "Microsoft Software Shadow Copy Provider"
    net start "Volume Shadow Copy"

    But is not Working

    Any Advice ?

    Thank's




    0 0

    I have taken backup of Windows Server R2 std SP1 from Server Manager it is around 16gb .vhd file from Server Computer

    When I am restoring in other Server PC of Windows server R2 std sp1 from Server Manager it is giving message backup not found.

    Why this message is coming?  I cant restore it?


    0 0
  • 04/09/14--11:37: cleaning heads
  • I need to clean heads on my printer. I just replaced all cartridges and it isn't printing black, I'm thinkink I just need to clean heads


    0 0

    Hi everyone,

    I am using 2012 R2 and I am trying to backup the Host Component via wbadmin:

    wbadmin START BACKUP -backupTarget:E: -hyperv:"Host Component"

    but I have not being successful so far. The error I get is:

    ERROR - Command syntax incorrect. Error: Component. See the command syntax below.

    Any ideas anyone please?


    0 0

    It have two Windows 2003 Servers running IIS 6.0. my aspx applications become unavailable when the IIS stops responding to web users. The only way to make them available is after rebooting the server.

    I already change permissions and change the recycle time of the application pool to 20 minutes, and I am still having the problem daily.


older | 1 | .... | 37 | 38 | (Page 39) | 40 | 41 | .... | 148 | newer