Wishlist 0 ¥0.00

中国两个全球卫星互联网络年内发射首星 总数将超456颗

  美国航天业冒险家马斯克近日号称要发射约1.2万颗低轨道卫星组成“星链”(StarLink)星座通信网,让Wifi信号阀盖全球每一个角落。

可是,马斯克的雄心壮志并不是只有马斯克一人才有。

虽然不及马斯克“海口”下1.2万颗的数目,但我国 航天科技集团和航天科工集团也都分别提出了建设300余颗和156颗低轨通信卫星星座的计划。两个计划的首颗技术验证星都预定在今年发射。

航天科工集团“虹云工程”动画演示(视频截图)

中国的低轨星座计划

全国两会开幕在即。全国政协委员、中国航天科技集团科技委主任包为民3月2日接受中新网采访时表示,航天科技集团正在部署一个低轨道通信卫星星座。一期工程将有54颗星,至二期工程时实现系统能力平滑过渡,卫星总数最终将超过300颗。

全国政协委员、中国航天科技集团科技委主任包为民(中新闻 图)

包为民称,计划在年内启动全球移动宽带卫星互联网系统建设。建成后,它将成为全球无缝覆盖的空间信息网络基础建设,为地面固定、手持移动、车载、船载、机载等各类终端提供互联网传输服务。

包为民补充道,这个卫星互联网系统可以在深海大洋、南北两极、“一带一路”等区域实现宽带窄带相结合的通信保障能力。通过该系统,处于地球上任何地点的任何人或物在任何时间实现信息互联。

包为民在采访中提到的这个“低轨道通信卫星星座”,应该就是在2016年珠海航展上公开的“鸿雁星座”。“全球低轨移动互联网卫星系统鸿雁星座”由航天级科技集团领导,长城公司与一院、五院等单位共同推出。

鸿雁星座宣传图(航天科技集团 图)

在2016年珠海航展上,航天科技集团所属的中国长城工业集团有限公司副总裁张晓东介绍,鸿雁星座计划将由60颗低轨道小卫星及全球数据业务处理中心组成,具有全天候、全时段及在复杂条件下的实时双向通信能力。60颗卫星将在2020年组网完毕,届时将促进国际通信互联互通。

在航天科技集团的2018年商业航天布局中,鸿雁星座的规模提升到了“300余颗低轨道小卫星”。工程具体将分3期建设,最终形成全球低轨移动互联网卫星系统。

鸿雁星座首发星由西安分院负责研制, 预计将于2018年第一季度发射。这颗首发星搭载的相关载荷具有在轨可重构技术,能够开展通信体制验证,实现小型终端联试联调、星地业务试运行,并对卫星测控运管系统进行验证。

长城公司介绍,对于个人用户来说,鸿雁星座的双向数据交互功能,可以保证这些用户在无国内地面网络覆盖的区域,如科考、登山、探险等活动的通信需求,同时可以为应急救援提供有力保障。鸿雁星座可为北斗导航卫星增强系统提供信息播发通道,提高北斗导航卫星定位精度,为航空运输、地信应用、海洋工程、交通物流、精准农业、自动驾驶等需要高精度定位的行业提供定制化服务。

鸿雁星座搭载的AIS载荷,可在全球范围内接收船舶发送的AIS报文信息,全面掌握船舶航行状态、位置、航向等动态和静态信息,实现对远海海域航行船舶的监控及渔政管理。鸿雁星座搭载的ADS-B载荷,具有全天候、大范围、远距离、卫星探测合法性等优点,可从外层空间对全球航空目标进行位置跟踪、监视及物流调控,增强飞行安全性及突发航空事故搜救能力。

此外,通过植入手机芯片,人们在国外旅游、航海、郊外郊游期间,即便没有手机信号,也能够发送信息、语音和图片。如果遇到紧急情况,例如落水,手机还能自动播报位置信息和求救信号,为个人野外通信、安全和救援提供有力帮助,未来就不会再有人员失联现象,“鸿雁”让世界永不失联。

航天科技集团展望,鸿雁星座推向市场后,“将成为(国内)首个能够满足基本卫星数据通信需求的系统。”

另一支“国家队”的筹划

除了航天科技集团外,我国还有另一支“国家队”——航天科工集团。航天科工集团对于建设低轨道通信卫星星座也有自己的计划。

航天科工的“虹云工程”是“基于小卫星的低轨宽带互联网接入系统”。虹云工程脱胎于航天科工之前提出的“福星计划”, 计划发射156颗在1000千米运行的低轨小卫星,组网构建一个星载宽带全球互联网络。

虹云工程动画演示:卫星正展开太阳能电池板(视频截图)

2016年9月举行的第二届中国商业航天高峰论坛上,航天科工集团提出重点实施五大商业航天工程。五个“云”中就包括了“虹云工程”。

虹云工程总设计师向开恒表示,虹云工程最重要的意义就是改变了现有的互联网接入方式,实现可覆盖全球的天基互联网接入。目前互联网的使用还不能离开陆基和海底光缆,但在很多情况下,受制于成本和地理环境的制约,并不具备光缆铺设的条件。

但在虹云二期工程完成后,卫星之间可以实现信息互联和信息处理。届时,装有客户端的飞机和船舶,即使处在远离陆地信关站2500千米以上的大洋深处,也可以实现网络互联,从而实现真正意义上的全球网络覆盖。

虹云工程动画演示(视频截图)

虹云工程的另一大特点就是 使用Ka波段。无线波段历来是先到先得,Ka波段虽然速度和质量不比传统的C波段,但却远没有C波段那么拥挤。国外One Web公司的低轨星座也计划使用Ka波段。虹云工程越早建设,就越有利于中国抢占波段资源,争取主动。

此外,向开恒介绍称,虹云工程将是世界上第一种实现每颗卫星达到4G/s信息传输速率的天地一体化宽带信息系统。“借助于前所未有的带宽,以及1000千米的低轨高度(相比于传统的同步轨道,距地面约35000千米以上),卫星信息传输的速度将有大幅提升,这对于改善新闻直播中的延时现象、提高远程遥控操作的质量有着重要意义。”

整个工程也分为3步。在早期规划中,第一步计划在2018年前发射第一颗技术验证星,实现单星关键技术验证;第二步到“十三五”末,发射4颗业务实验星,组建一个小星座,让用户进行初步业务体验;第三步到“十四五”末,实现全部156颗卫星组网运行,完成业务星座构建。

但在2017年8月的第三届中国商业航天高峰论坛上,向开恒虽然提及技术验证卫星已进入初样试验阶段,但把技术验证卫星发射时间修正到了“明年中”,也就是2018年。他同时坦言,“虹云工程”在发射、测控等方面尚存问题,商业化也还在摸索中。

第二次向低轨道的大进军

太空低轨道在通信上的巨大潜力,人类早在20多年前就已经发现。1999年,摩托摩拉推出了人类首个大规模低轨星座通信计划——由77颗星组网的“铱星”计划。但受制于当时条件所限,运营成本过高且实际速度很慢。最后使用者寥寥。相较于卫星通信,地面通讯的发展更为迅速,立刻占据了大部分市场。

铱星星座

但在20年后的今天情况已经有了很大改观。航天科技的进步降低了卫星研制、量产和发射的成本,而卫星通信资费的降低又催生出无时无刻的互联网接入和大数据需求。低轨通信卫星的复兴也自然水到渠成。

尤其是我国疆域辽阔,自然地形复杂。在面对偏远山区的自然村落时,与地面光缆相比,“从天上”解决很可能成本更低。2016年12月的《十三五国家信息化规划》中也明确提及“通过移动蜂窝、光纤、

低轨卫星等多种方式,完善边远地区及贫困地区的网络覆盖。”

2018年对于全球多个低轨卫星计划都将是关键一年。马斯克的“星链”在上个月刚发射了两颗验证星。One Web公司也打算在今年开展发射计划。而我国“鸿雁”和“虹云”这两个低轨卫星工程,同样将在今年发射首颗卫星。

发令枪已经响起,最后谁能跑赢比赛?

GitHub 发布 2018 年开源项目趋势预测

Github 发布了一篇博客,预测了 2018 年开源项目的发展趋势,这些趋势可以帮助开发人员在共享知识的同时,寻求方法简化流程,并 get 新技能。

去年,Github 有来自将近 200 个国家的 2400 万的开发者聚集在一起,共同编写更好更强大的代码。2017 年,从框架到数据可视化,共构建了 2500 多万个存储库,今年的数据似乎还会有所上升。

今年,Github 整理了 2017 年社区上贡献者、访问者和最受欢迎活动的数据,以预测 2018 年开源项目的发展趋势。

项目趋势

跨平台开发

 

跨平台开发和网页开发是 2017 年增在最快的领域。例如,2017 年,Angular/angular-cli 的贡献者数量比 2016 年多 2.2 倍。Angular / Angular,Facebook / React 和 Electron / Electron等相关项目的贡献数、访问数、Star 数更加多。这些项目都帮助简化了开发流程,缩短了从桌面和移动平台开始到部署的时间。

 

深度学习

 

2017 年深度学习也受到了广泛的重视,人工智能帮助解决了存在于多个行业的,复杂而有趣的问题。开发者对 Keras-team / Keras 和 Mozilla / DeepSpeech 等项目的贡献与参与推动了这一领域的发展。2017 年,TensorFlow / TensorFlow 的访问量比 2016 年增加 2.2 倍,TensowFlow/models 的访问量增加了 5.5 倍。

 

新技能

 

开发者一直致力于开发编码技能,2017 年 Star 的项目都与编码学习、获取编码工作和编码最佳实践的项目有关。例如,Chalarangelo/30-seconds-of-code 和 norvig / pytudes 分别在 javascript 和 python 中提供代码示例,以帮助您提高这些语言的流畅度。jwasham/coding-interview-university 和 yangshun/tech-interview-handbook 为如何通过软件工程师的面试提供了资源。i0natan/nodebestpractices,alibaba / p3c 和 thedaviddias/Front-End-Checklist 为编写代码和组织项目提供了最佳实践。

 

方法

 

Github 通过三种不同类型的活动发现了这些趋势:

  • 首先,评出 2016 年至少有 2000 个贡献者,并且在 2017 年贡献者数量增幅最大的 Top100 项目

  • 然后,评出 2017 年项目 repo 访问量增幅最大的 Top100 项目

  • 最后,评出 2017 年获得最多新星的 Top100 项目

结合这三个列表对项目进行社区分类,并查看了列表中排名最高的社区。

[SOLVED] Windows Server Backup - Went from 100+ copies...to 1 copy available

    • Hi everyone,

      I'm using Windows Server Backup on a Windows Server 2012 R2 system that has been in production for half a year or so.  The server has around 60GB used, and the backup drive is a 160GB external drive that I had sitting around and put it in place until they can afford a larger external drive.  The setup has been working great, and just yesterday when I opened the Windows Server Backup utility, I noticed that all backups have been successful and there were well over 100 backups available.  The external hard drive was showing "in the red" for space available, about 15GB free or so if I remember right.  But that's fine, since I understand that Windows Server Backup should delete the oldest backup available.

      ...OR...you know, it deletes everything.  So I log in today, and what do you know?  60ish GB used on the external drive, so plenty of free space.  But only 1 copy available.  Is...like...am I missing something?  Is that how it's supposed to work when the drive gets full?  I was under the impression it would delete files from the oldest snapshot and create a new backup.  Or delete several old snapshots.

      Did something happen in a recent Windows update?  Any way to fix it?  In my little bit of searching before this, I found that some others have had experiences with at least Server 2008 where Windows Server Backup would all the sudden only keep 1 copy.  So I guess I'll know tomorrow whether or not that's happening to me; whether I see "1 copy available" again, or "2 copies available".

      Thanks in advance for any advice!

      • Edited by link470 Thursday, November 27, 2014 6:25 PM
      Sunday, November 16, 2014 10:50 PM
      Avatar of link470
       
      45 Points
       
 

Answers

    • Hi,

      The backup type is changed to Full from incremental automatically?

      I checked, and it hadn't done that.  The backup was still set to Normal [Full].

      And if it is caused by a corrupted hard disk, you can try to do a check disk on it first and you may need to get a disk analysis tool from the hard disk manufacturer for accurate testing.

      This is what I'm thinking is the most likely cause.  I ended up stopping the backup schedule for the drive that was getting I/O errors in Event Viewer and releasing the old backup drive and pulling it.  Then I added a new external backup drive and created a new nightly schedule, and that's working great.  The backup completes very quickly and is a full backup every time, using VSS for block backups so the disk space isn't all eaten up [how it always was before this incident], and the drive is now carrying multiple backups again. 

      Something just got very confused when the last backup drive had I/O errors.

      The other thing I thought was interesting this time around is that I could no longer select VSS Copy Backup.  Only VSS Full backup was selected and I couldn't find an option anywhere to change it to VSS Copy Backup.  I'm assuming either VSS Copy was removed in 2012 R2 but not in 2012, or my backup settings I chose didn't allow for that option to be shown during the wizard.  Does anyone have any insight on this?

      Note: VSS Full is fine, and is working great.  But just curious, since one 2012 server I operate is set to VSS Copy, and the other is set to VSS Full.  Both appear to work the same and I understand how it really only effects the archive bit being set, but just curious why VSS Copy didn't present itself as an option.  I've also recently updated the third large 700ish MB update for Server 2012 R2/Windows 8.1, so maybe that changed something.

      Either way, resolved!  Backup appears to be fine.  But what I'm still really curious of is what caused the backup to start only holding 1 copy.

      • Marked as answer by link470 Thursday, November 27, 2014 6:07 PM
      • Edited by link470 Thursday, November 27, 2014 6:09 PM
      Thursday, November 27, 2014 6:06 PM
      Avatar of link470
       
      45 Points
       
 

All replies

    • Hi,

      As it has been a while, whether new backup copies are created these days?

      As you said Windows Server Backup should not delete all backup at a time even it is for releasing disk space - it will not delete more than 1/8 space and if it has to, it will provide an error "no enough space" instead of just deleting all backups.

      Since you mentioned Windows Update, have you checked if any new update is installed just before the issue occurs?


      If you have any feedback on our support, please send to This email address is being protected from spambots. You need JavaScript enabled to view it..

      Thursday, November 20, 2014 5:54 AM
      Avatar of MedicalS
      (MSFT CSG)
      64,325 Points
      Moderator
 
    • Hi,

      As it has been a while, whether new backup copies are created these days?

      I've been monitoring the server in question, and the backups are still only maintaining 1 copy.  I did notice though that the "Advanced option:" in Windows Server Backup schedule settings shows up as "VSS Full Backup", instead of "VSS Copy Backup" which other Windows Server 2012 servers [not R2] are using.  VSS Full seems to only store 1 copy, and the backups take an incredibly long time to run.  What used to take 1 hour now takes more like 18 hours.

      As you said Windows Server Backup should not delete all backup at a time even it is for releasing disk space - it will not delete more than 1/8 space and if it has to, it will provide an error "no enough space" instead of just deleting all backups.

      That's what I thought, glad to know that isn't the usual behavior I'm experiencing.  I did have a look in the event viewer as well and noticed that there was I/O errors on the external drive.  So I'm wondering if that's contributing to why the backup is running so incredibly slow, and also what may have caused Windows Server Backup to delete all the previous backups.

      Since you mentioned Windows Update, have you checked if any new update is installed just before the issue occurs?

      No new updates were installed before.  The last updates would have been the October patch Tuesday, where all updates were successfully installed.  Windows Server Backup was fine after that until right up before I ran these past updates in November.  So I can't see that directly being the cause, at least not immediately taking effect. 

      My bets right now are with the external hard drive possibly failing.

      Thursday, November 20, 2014 10:34 PM
      Avatar of link470
       
      45 Points
       
 
    • Hi,

      The backup type is changed to Full from incremental automatically?

      Full Backup will take a long time - actually the first backup of an incremental backup schedule is a full backup which will also take a long time. The rest ones will be incremental so they will be finished much quicker.

      In this situation can you change the backup type to incremental again?

      And if it is caused by a corrupted hard disk, you can try to do a check disk on it first and you may need to get a disk analysis tool from the hard disk manufacturer for accurate testing. 


      If you have any feedback on our support, please send to This email address is being protected from spambots. You need JavaScript enabled to view it..

      Thursday, November 27, 2014 6:19 AM
      Avatar of MedicalS
      (MSFT CSG)
      64,325 Points
      Moderator
 
    • Hi,

      The backup type is changed to Full from incremental automatically?

      I checked, and it hadn't done that.  The backup was still set to Normal [Full].

      And if it is caused by a corrupted hard disk, you can try to do a check disk on it first and you may need to get a disk analysis tool from the hard disk manufacturer for accurate testing.

      This is what I'm thinking is the most likely cause.  I ended up stopping the backup schedule for the drive that was getting I/O errors in Event Viewer and releasing the old backup drive and pulling it.  Then I added a new external backup drive and created a new nightly schedule, and that's working great.  The backup completes very quickly and is a full backup every time, using VSS for block backups so the disk space isn't all eaten up [how it always was before this incident], and the drive is now carrying multiple backups again. 

      Something just got very confused when the last backup drive had I/O errors.

      The other thing I thought was interesting this time around is that I could no longer select VSS Copy Backup.  Only VSS Full backup was selected and I couldn't find an option anywhere to change it to VSS Copy Backup.  I'm assuming either VSS Copy was removed in 2012 R2 but not in 2012, or my backup settings I chose didn't allow for that option to be shown during the wizard.  Does anyone have any insight on this?

      Note: VSS Full is fine, and is working great.  But just curious, since one 2012 server I operate is set to VSS Copy, and the other is set to VSS Full.  Both appear to work the same and I understand how it really only effects the archive bit being set, but just curious why VSS Copy didn't present itself as an option.  I've also recently updated the third large 700ish MB update for Server 2012 R2/Windows 8.1, so maybe that changed something.

      Either way, resolved!  Backup appears to be fine.  But what I'm still really curious of is what caused the backup to start only holding 1 copy.

      • Marked as answer by link470 Thursday, November 27, 2014 6:07 PM
      • Edited by link470 Thursday, November 27, 2014 6:09 PM
      Thursday, November 27, 2014 6:06 PM
      Avatar of link470
       
      45 Points
       
 
    • Hello,

      it took us a few weeks and lots of trial and error to figure this out.

      Despite backing up every day successfully only the previous day was restorable on one of our servers (2012) and the windows server backup GUI showed only 1 copy on the ISCSI drive. Recreating the backup from scratch (and prior deleting all shadow copies) did not help.

      It turned out the assigned space for the volume shadow service for the specific drive (drive properties) was set way too low. After increasing that amount the backup has created several copies and we could now restore more than just a single day.

      Best regards,
      complingua

      • Edited by complingua Thursday, April 13, 2017 10:43 AM
      Thursday, April 13, 2017 9:58 AM
      Avatar of complingua
      (Partner)
      0 Points
       
 
    • Similar issue here.

      A disk error caused the back up to fail several times.  Solved the disk error issue, but was only getting 1 copy available (yesterdays).

      Turns out the Advanced back up settings had been changed from VSS Copy to Full.  Restored this to VSS copy and we had the multiday copies available after that.

      rossh

      Saturday, May 06, 2017 5:57 AM
      Avatar of rossh_hm
       
      5 Points
       
 
 
 
 
 

对win2008服务器备份功能的介绍——Backup Version and Space Management in Windows Server Backup

This article answers following questions related to Windows Server Backup in Windows Server 2008 and Windows Server 2008 R2:

Q1. How does Windows Server Backup store backups and maintain backup versions?
Q2. How do I query backup stored versions on a backup storage location?
Q3. How do I delete non system state backups created using Windows Server Backup?
Q4. How do I delete system state backups created using Windows Server Backup?

Overview

  • Windows Server Backup is the built-in backup solution in Windows Server 2008 and Windows Server 2008 R2. Using Windows Server Backup, an administrator can schedule periodic backups of a server and also create backups on demand. For details on using Windows Server Backup, please see the Installed Help for Windows Server 2008 (http://technet.microsoft.com/en-us/library/cc770757(WS.10).aspx) and for Windows Server 2008 R2 (http://technet.microsoft.com/en-us/library/cc770757.aspx).
  • Windows Server Backup in Windows Server 2008 allows administrators to back up entire volumes. More flexibility is available in Windows Server 2008 R2 where administrators can pick and choose individual files and folders to be included in a backup. The technology used by Windows Server Backup to perform a backup differs based on the nature of the backup:
    • If you back up an entire volume, Windows Server Backup creates a block-level backup that reads directly from the volume by passing the file system.
    • If you back up just specific files and folders, Windows Server Backup reads individual files going through the file system.
  • Windows Server Backup stores backups at the following path: <BackupStorageLocation>WindowsImageBackup<ComputerName>. A back up operation performs following steps:
  1. Windows Server Backup reads data from source volumes and then creates a .vhd file per source volume on the backup storage location and writes the backup metadata.
  2. Windows Server Backup stores backup versions in volume shadow copies. After the data write is complete, Windows Server Backup creates a shadow copy of the volume where the backup is stored using Volume Shadow Copy Service (VSS). This shadow copy retains the state of the storage volume as a “backup version” or “point-in-time” of the backup and must restore using this backup version. VSS is the underlying Microsoft technology required for maintaining backup versions. (For more information about VSS, see http://technet.microsoft.com/en-us/library/cc785914.aspx.)
  3. After creating the shadow copy, Windows Server Backup updates the backup catalog which is stored on both the system volume of the server that is being backed up and the backup storage folder with the following information:
    • The backup time − The local system time of the server when the backup operation started.
    • The shadow copy identifier (Shadow Copy ID) − Used by Windows Server Backup to associate the backup version to the correct shadow copy.
    • Version identifier − Used by Windows Server Backup to uniquely identify a backup version. Users using command line tools (Wbadmin and the Windows PowerShell cmdlets for Windows Server Backup) will specify the version identifier as a parameter to the command to work with a backup version.
  • If the backup storage location is full, Windows Server Backup automatically deletes the oldest backup version to make space for the current backup. Since each backup is stored inside a shadow copy, deleting a backup version is accomplished by simply deleting the corresponding shadow copy. However, space for a system state backup in Windows Server 2008 is not automatically managed by Windows Server Backup. See the section “How to Delete System State Backups” below for managing system state backups in Windows Server 2008.
  • Windows Server Backup can store only one backup version on a network share (remote shared folder). You can store backups from multiple computers to a network share. A backup from a computer to a network share will be saved at: \<RemoteServer><SharedFolderPath>WindowsImageBackup<ComputerBackedUp>. To delete the backup on network share, you need to delete the <ComputerBackedUp> directory from network share.
  • Windows Server Backup uses the .vhd format for writing backups. The current virtual hard disk specification limits the size of a virtual hard disk to be 2040 GB, which can fit a volume of size 2040 GB – 2 MB, (i.e., 2088958 MB). Windows Server Backup in Windows Server 2008 also limits the maximum source volume size to be 2088958 MB. In Windows Server 2008 R2, if you are not backing up a full volume and, instead, creating a backup of selected files/folders, your source volume size can be more than 2088958 MB, provided your actual data size is less than equal to 2088958 MB. If you are creating a full volume backup, the maximum source volume size limit continues to be 2088958 MB.

How to Query Backup Versions

To see the backup versions present in a particular computer, use the Wbadmin get versions command. Note that, to use the Wbadmin command, you must be a member of the Administrators group or Backup Operators group and must open an elevated instance Cmd.exe (click Start, right-click Command Prompt, and then click Run as administrator). For detailed Wbadmin command documentation, see: http://technet.microsoft.com/en-us/library/cc754015.aspx.

Sample output of Wbadmin get versions command:

wbadmin 1.0 – Backup command-line tool

(C) Copyright 2004 Microsoft Corp.

 

Backup time: 3/12/2009 10:55 AM

Backup target: Fixed Disk labeled New Volume(I:)

Version identifier: 03/12/2009-05:25

Can recover: Volume(s), File(s)

Snapshot ID: {f5e946da-5cc7-44c3-a747-9f1079e639b0}

 

Snapshot ID in the above output is new in Windows Server 2008 R2. Snapshot ID is same as Shadow Copy ID. It corresponds to a specific backup version and can be used to delete that backup version.

 

To view all backup versions on a particular backup storage location, type:

Wbadmin get versions -backupTarget:<BackupStorageLocation:>

 

For example, if you want to view all the backup versions on the backup storage location K:, type:

Wbadmin get versions –backupTarget:K:

 

In the output of Wbadmin get versions command, Backup time is the local system time and Version Identifier is the GMT time at the time the backup was created. If you change your system time zone, the value for Backup time will also change. Note that Version Identifier is a unique identifier for a given backup version and remains constant for a backup.

 

How to Delete Non-System State Backups

Windows Server Backup deletes a backup by just deleting the corresponding shadow copy and updating the backup catalog. You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during the next backup. In short, to delete a backup version manually, you need to delete the corresponding shadow copy from the backup storage location.

To delete a shadow copy, follow these general steps:

  1. Identify the backup version you want to delete by querying the backup versions on your backup storage location.
  2. Determine the shadow copy ID of the version you want to delete.
  3. Delete the shadow copy.

 

Identify the backup version:

To list all the shadow copies on a volume, use the Vssadmin command. (For the complete syntax for Vssadmin, see: http://technet.microsoft.com/en-us/library/cc754968(WS.10).aspx.) The following command line lists all shadow copies on a specified backup storage location:

Vssadmin list shadows /for=<BackupTarget>

For example, to list the shadow copies on the location Y, type:

Vssadmin list shadows /for=Y:

Determine the shadow copy ID:

On Windows Server 2008 R2, the shadow copy ID is same as Snapshot ID given in the output of querying backups. On Windows Server 2008, you can find your backup’s shadow copy ID by looking at output of Vssadmin list shadows /for=<Backup Target>. Match the shadow copy creation time with your backup’s Backup time value.

 

Delete the Shadow Copy for the specific Shadow Copy ID:

  1. To open a command prompt with elevated privileges, click Start, right-click Command Prompt, and then click Run as administrator.

About Us

Since 1996, our company has been focusing on domain name registration, web hosting, server hosting, website construction, e-commerce and other Internet services, and constantly practicing the concept of "providing enterprise-level solutions and providing personalized service support". As a Dell Authorized Solution Provider, we also provide hardware product solutions associated with the company's services.
 

Contact Us

Address: No. 2, Jingwu Road, Zhengzhou City, Henan Province

Phone: 0086-371-63520088 

QQ:76257322

Website: 800188.com

E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.