A fast way to backup a data partition


  1. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
       #1

    A fast way to backup a data partition


    If you are in a hurry and don't want to use any particular backup program to save your data, use Command Prompt. The command example is:

    WBADMIN START BACKUP -backupTarget:F: -include:M:

    Where M is the data partition you want to backup and F is the volume where you put the backup.

    This is very fast backup method and the result is a Windows image containing a VHD of your data partition. That VHD can be attached via Disk Management > Action button and you can retrieve your data from the virtual volume in Computer.

    You can do the same with any partition including the OS partition. Problem is that I have not yet found a method to restore a partition with this image. But attaching the VHD makes it suitable for data partitions.
      My Computer


  2. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #2

    Have you seen the Tech-Net resources? Wbadmin

    Would this work?
    wbadmin start recovery -version: (Enter version Date here) -itemType:Volume -items:F:

    I'm not sure you would need to include M because it would already be included in the Volume; Right??
    Wbadmin start recovery


    Also: Wbadmin start systemstaterecovery Shows:
    wbadmin start systemstaterecovery -version: (Enter version Date here)

    Watch your spacing I included an extra space at -versionEnter version Date here) to stop the 7F server from creating the smiley.


    This is what I got when I entered wbAdmin start recovery ? into an elevated CMD prompt, I believe the syntax error was caused by the "?" I added and it isn't needed.

    Code:
    C:\Windows\system32>wbAdmin start recovery ?
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.
    
    ERROR - Command syntax incorrect. Error: ?. See the command
    syntax below.
    
    Syntax: WBADMIN START RECOVERY
        -version:<VersionIdentifier>
        -items:{<VolumesToRecover> | <AppsToRecover> | <FilesOrFoldersToRecover>}
        -itemtype:{Volume | App | File}
        [-backupTarget:{<VolumeHostingBackup> | <NetworkShareHostingBackup>}]
        [-machine:<BackupMachineName>]
        [-recoveryTarget:{<TargetVolumeForRecovery> | <TargetPathForRecovery>}]
        [-recursive]
        [-overwrite:{Overwrite | CreateCopy | Skip}]
        [-notRestoreAcl]
        [-skipBadClusterCheck]
        [-noRollForward]
        [-quiet]
    
    Description:  Runs a recovery operation based on the parameters that you
    specify.
    To use this command, you must be a member of the Backup Operators group
    or Administrators group.
    
    Parameters:
    -version       Specifies the version of the backup to recover in
                    MM/DD/YYYY-HH:MM format. If you do not know the version
                    identifier, type WBADMIN GET VERSIONS.
    
    -items         Specifies a comma-delimited list of volumes, applications,
                    files, or folders to recover.
                    -If -itemtype is Volume, you can specify only a single volume
                    by providing the volume drive letter, volume mount point, or
                    GUID-based volume name.
                    -If -itemtype is App, you can specify only a single
                    application. To be recovered, the application must have
                    registered with Windows Server Backup. You can also use the
                    value ADIFM to recover an installation of Active Directory
                    Domain Services. See Remarks for more information.
                    -If -itemtype is File, you can specify files or folders, but
                    they should be part of the same volume and they should be
                    under the same parent folder.
    
    -itemtype      Specifies the type of items to recover. Must be Volume, App, or
                    File.
    
    -backupTarget  Specifies the storage location that contains the backup that
                    you want to recover. The parameter is useful when the
                    location is different from where backups of this computer are
                    usually stored.
    
    -machine       Specifies the name of the computer that you want to recover
                    the backup for. The parameter is useful when multiple
                    computers have been backed up to the same location. Should be
                    used when -backupTarget is specified.
    
    -recoveryTarget  Specifies the location to restore to. This parameter is
                    useful if this location is different than the location that
                    was previously backed up. It can also be used for
                    restorations of volumes, files, or applications. If you are
                    restoring a volume, you can specify the volume drive letter
                    of the alternate volume.
                    If you are restoring a file or application, you can specify
                    an alternate recovery location.
    
    -recursive     Valid only when recovering files. Recovers the files in the
                    folders and all files subordinate to the specified folders.
                    By default, only files which reside directly under the
                    specified folders are recovered.
    
    -overwrite     Valid only when recovering files. Specifies the action to take
                    when a file that is being recovered already exists in the
                    same location.
                    -Skip causes Windows Server Backup to skip the existing file
                    and continue with recovery of the next file.
                    -CreateCopy causes Windows Server Backup  to create a copy
                    of the existing file so that the existing file is not
                    modified.
                    -Overwrite causes Windows Server Backup to overwrite the
                    existing file with the file from the backup.
    
    -notRestoreAcl Valid only when recovering files. Specifies to not restore
                    the security access control lists (ACLs) of files being
                    recovered from backup. By default, the security ACLs are
                    restored (the default value is true). If this parameter is
                    used, the ACLs for the restored files will be inherited from
                    the location to which the files are being restored.
    
    -skipBadClusterCheck  Valid only when recovering volumes. Skips checking
                    the disks that you are recovering to for bad cluster
                    information. If you are recovering to an alternate server or
                    hardware, we recommend not using this parameter. You can
                    manually run the command CHKDSK /B on these disks at any time
                    to check them for bad clusters, and then update the file
                    system information accordingly.
                    Important: Until you run CHKDSK as described, the bad
                    clusters reported on your recovered system may not be
                    accurate.
    
    -noRollForward  Valid only when recovering applications. This allows for
                    previous point-in-time recovery if the latest version from
                    the backups is selected. For other versions of the
                    application that are not the latest, previous point-in-time
                    recovery is done by default.
    
    -quiet         Runs the command with no prompts to the user.
    
    Examples:
    WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:Volume -items:d:
    WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:App
    -items:Registry -recoverytarget:d:\
    WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:File
    -items:d:\folder -recursive
    WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:Volume
    -items:\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\
    WBADMIN START RECOVERY -version:04/30/2005-09:00 -backupTarget:\\servername
    \share -machine:server01
    
    Remarks:  To view a list of items available that are available for recovery
    from a specific backup version, use WBADMIN GET ITEMS. If a volume did not
    have a mount point or drive letter at the time of backup, then this command
    would return a GUID-based volume name that should be used for recovering the
    volume.
    When the -itemtype is App, you can use a value of ADIFM for -item to perform
    an install from media (IFM) operation to recover all the related data needed
    for Active Directory Domain Services. ADIFM creates a copy of the Active
    Directory database, registry, and SYSVOL state, and then saves this
    information in the location specified by -recoveryTarget. Use this parameter
    only when -recoveryTarget is specified.
    Note: Before using WBADMIN to perform an Install from Media operation, you
    should consider using the NTDSUTIL command because NTDSUTIL only copies
    the minimum amount of data needed, and it uses a more secure data transport
    method.
    
    
    C:\Windows\system32>
      My Computer


  3. Posts : 47
    Windows 7
       #3

    support Win8?
      My Computer


  4. Posts : 47
    Windows 7
       #4

    sorry, I didn't notice that this is Windows seven forum
    forgive me
      My Computer


  5. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #5

    pabuman said:
    pabuman said:
    support Win8?
    sorry, I didn't notice that this is Windows seven forum
    forgive me
    Your forgiven,


    From: Wbadmin
    Wbadmin
    8 out of 18 rated this helpful - Rate this topic Published: April 17, 2012
    Updated: April 17, 2012
    Applies To: Windows 8, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Vista
    It should, get an elevated CMD prompt open in your 8OS and type in C:\Windows\system32>wbAdmin ? <- notice space; with or without the "?" If you get a positive response, you should be good to go.

    More:
    We previously reported that the system image backup feature was removed in Windows 8.1. This isn’t entirely true — while the graphical interface for creating system images was removed, you can still create system images with a PowerShell cmdlet.


    This is good news for system administrators, as it allows them to create and restore system image backups without switching to third-party tools like Norton Ghost. System images are different from recovery images created with recimg because they contain a full snapshot of the system’s hard drive, including user files and settings.

    Source: How to Create and Restore System Image Backups on Windows 8.1
      My Computer


  6. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
    Thread Starter
       #6

    Thank you Steve. I shall investigate that further. Need to make some 'experiments'. But I'll first make a Macrium image in case I brick my system.
      My Computer


  7. Posts : 5,605
    Originally Win 7 Hm Prem x64 Ver 6.1.7600 Build 7601-SP1 | Upgraded to Windows 10 December 14, 2019
       #7

    Your welcome Wolfgang, an image would be a wise decision.

    This CMD might be helpful in restoring the backup:
    Code:
    -recoveryTarget  Specifies the location to restore to. This parameter is
                    useful if this location is different than the location that
                    was previously backed up. It can also be used for
                    restorations of volumes, files, or applications. If you are
                    restoring a volume, you can specify the volume drive letter
                    of the alternate volume.
                    If you are restoring a file or application, you can specify
                    an alternate recovery location.
    You can find it listed here: Wbadmin start systemstaterecovery, its listed under syntax and parameters, but doesn't show any examples.

    Maybe??
    wbadmin start systemstaterecovery -version: (Your version date) -recoveryTarget:{<TargetVolumeForRecovery> | <TargetPathForRecovery>}


    I have run across other users that wbadmin won't work with Windows 7 unless you use a WinRE disk to boot into, then run the wbadmin commands.

    See: Windows 7 backup/restore strategies, you can read them, but ignore the 3rd and 4th posts down from Samhanye and rbgrove.

    #5 by sjm-austin used Arcronis, and #6 by Evolve_or_Die is the one that used the WinRE method.

    Backups of all versions of the Windows OS with wbadmin seem to work okay with wbadmin, but it also seems Microsoft has crippled the recovery/restore to client side OS versions, But not for Server versions.
      My Computer


  8. whs
    Posts : 26,210
    Vista, Windows7, Mint Mate, Zorin, Windows 8
    Thread Starter
       #8

    That is correct. Wbadmin seems to have been designed mainly for the server versions. But it is such a neat function that one should be able to use it universally. When I get some more time, I'll continue to play around with it.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:10.
Find Us