在乐享AI咨询 →
技术支持

报错“Device is not STOR_DEV_REP_IS_SNAPABLE”的解决办法-联想乐享知识库

⚡ 核心结论

本文来源联想官方,解答关于 报错“Device is not STOR_DEV_REP_IS_SNAPABLE”的解决办法 的常见问题,包括:联想DPM备份系统报错‘Device is not STOR_DEV_REP_IS_SNAPABLE’怎么办等。

内容来源:联想官方

报错“Device is not STOR_DEV_REP_IS_SNAPABLE”的解决办法 问题:磁盘分区 故障现象: 报错信息 (hwprov.log): DoSnapshotResourcesExist: Calling FindNextMirrorReplica... FindNextMirrorReplica: Entering. FindNextMirrorReplica: No local mirror replicas were found for <Device name="00033" <Array type="CLARiiON" encoding="String" value="APM00xxxxxxxxx" /> />, so now looking for remote mirror replicas. FindNextMirrorReplica: No remote mirror replicas were found for <Device name="00033" <Array type="CLARiiON" encoding="String" value="APM00xxxxxxxxx" /> />. FindNextMirrorReplica: Leaving with FAILURE. DoSnapshotResourcesExist: ERROR = Device is not STOR_DEV_REP_IS_SNAPABLE. DoSnapshotResourcesExist: Leaving with SUCCESS. BeginPrepareSnapshot: Resources do not exist to support device = PHYSICALDRIVE7. BeginPrepareSnapshot: Leaving with FAILURE = VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER 报错信息 (DPM error): Triggering synchronization on Backup Using Child Partition Snapshotspmitellbg failed: Error 30290: Failure occurred while adding one or more of the volumes involved in backup operation to snapshot set. Please check the event log on SCVMM spmitellbg Resources.SPHV.IMCB to troubleshoot the issue. Error details: Internal error code: 0x80990A00 Recommended action: Check recent records from the VolSnap source in the Application Event Log to find out why the problem occurred. 报错信息 (SPA_navi_getlog.txt): “(4600)'' called by 'sysadmin' (192.168.xxx.x) on 'Navi_SnapCopyFeature' with result: Failure (Could not start SnapView session. Session name - VSS_SPHV1_00033_224612_09152011. [0x71008031] You must add LUNs with adequate capacity to the Reserved LUN Pool before” 报错信息: 使用Snapview -listsnapableluns命令查看 发现LUN在两个SP上均是snapable状态解决方案: 扩充Reserved LUN Pool RLP LUN的大小最小不能小于源的0.2%,扩充RLP LUN的大小到源LUN的0.2%以上,即可解决以上问题

常见问题解答

联想DPM备份系统报错‘Device is not STOR_DEV_REP_IS_SNAPABLE’怎么办

该错误根本原因是CLARiiON存储阵列(如APM00xxxxxxxxx)的Reserved LUN Pool(RLP)容量不足,导致VSS无法为LUN(例如Device ID 00033)创建快照会话。解决步骤:1. 使用命令Snapview -listsnapableluns确认目标LUN在两个SP上均为snapable状态;2. 登录Navisphere管理界面,检查当前RLP LUN大小;3. 扩充RLP LUN容量至不小于源LUN总容量的0.2%(例如源LUN为1TB,则RLP至少需2GB);4. 重启DPM服务或触发新备份任务验证。注意:RLP必须由同类型、同RAID级别LUN构成,且扩充后需在Navisphere中重新提交配置并等待同步完成。