☰

유효성 검사 절차에 따라 원격 인증서가 유효하지 않습니다.

tag-icon • tag-icon vmware-esxi vmware-vsphere veeam
유효성 검사 절차에 따라 원격 인증서가 유효하지 않습니다.

내 VM 백업 작업이 실패합니다.

**Job Error**: Failed to create snapshot for LUN NL_Raid6b Details: The remote certificate is invalid according to the validation procedure.

**VM Error**:  Failed to prepare VM for processing from storage snapshot, failing over to using VM snapshot.

23/07/2019 01:30:12 :: Job started at 23/07/2019 01:30:06  
23/07/2019 01:30:13 :: Building list of machines to process  
23/07/2019 01:30:39 :: VM size: 798.5 GB  
23/07/2019 01:30:39 :: Changed block tracking is enabled  
23/07/2019 01:30:43 :: Queued for processing at 23/07/2019 01:30:44  
23/07/2019 01:30:43 :: Required backup infrastructure resources have been assigned  
23/07/2019 01:31:18 :: Creating storage snapshot  
23/07/2019 01:31:20 :: Failed to create snapshot for LUN NL_Raid6b Details: The remote certificate is invalid according to the validation procedure.  
23/07/2019 01:31:29 :: Processing myvm-7  
23/07/2019 01:31:34 :: Processing myvm-6  
23/07/2019 01:32:45 :: Processing myvm-3  
23/07/2019 01:34:00 :: Processing myvm-5  
23/07/2019 01:35:26 :: Processing myvm-2  
23/07/2019 01:36:56 :: Processing myvm-8  
23/07/2019 01:39:01 :: Processing myvm  
23/07/2019 01:41:17 :: Processing myvm-4  
23/07/2019 01:42:37 :: All VMs have been queued for processing  
23/07/2019 01:45:42 :: Load: Source 35% > Proxy 80% > Network 12% > Target 0%  
23/07/2019 01:45:42 :: Primary bottleneck: Proxy  
23/07/2019 01:45:42 :: Job finished with warning at 23/07/2019 01:45:42   

----------

myvm-4

23/07/2019 01:30:57 :: Creating VM snapshot  
23/07/2019 01:31:01 :: Collecting disk files location data  
23/07/2019 01:31:20 :: Failed to prepare VM for processing from storage snapshot, failing over to using VM snapshot.  
23/07/2019 01:31:21 :: Removing VM snapshot  
23/07/2019 01:31:29 :: Queued for processing at 23/07/2019 01:31:30  
23/07/2019 01:31:30 :: Required backup infrastructure resources have been assigned  
23/07/2019 01:42:38 :: VM processing started at 23/07/2019 01:42:38  
23/07/2019 01:42:38 :: VM size: 124.0 GB (87.5 GB used)  
23/07/2019 01:42:38 :: Getting VM info from vSphere  
23/07/2019 01:42:44 :: Creating VM snapshot  
23/07/2019 01:42:59 :: Saving [vfs-sto01-san-04(NL)] myvm-4/myvm-4.vmx  
23/07/2019 01:42:59 :: Saving [vfs-sto01-san-04(NL)] myvm-4/myvm-4.nvram  
23/07/2019 01:43:00 :: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [san]  
23/07/2019 01:43:00 :: Using backup proxy VMware Backup Proxy for disk Hard disk 2 [san]  
23/07/2019 01:43:01 :: Hard disk 1 (64.0 GB) 1.3 GB read at 20 MB/s [CBT] 
23/07/2019 01:43:01 :: Hard disk 2 (20.0 GB) 1.3 GB read at 18 MB/s [CBT] 
23/07/2019 01:44:20 :: Using backup proxy VMware Backup Proxy for disk Hard disk 3 [san]  
23/07/2019 01:44:21 :: Hard disk 3 (40.0 GB) 191.0 MB read at 41 MB/s [CBT] 
23/07/2019 01:44:35 :: Removing VM snapshot  
23/07/2019 01:44:40 :: Finalizing  
23/07/2019 01:44:47 :: Busy: Source 99% > Proxy 27% > Network 3% > Target 0%  
23/07/2019 01:44:47 :: Primary bottleneck: Source  
23/07/2019 01:44:47 :: Network traffic verification detected no corrupted blocks  
23/07/2019 01:44:47 :: Processing finished with warnings at 23/07/2019 01:44:48  



myvm-5

23/07/2019 01:30:57 :: Creating VM snapshot  
23/07/2019 01:31:01 :: Collecting disk files location data  
23/07/2019 01:31:20 :: Failed to prepare VM for processing from storage snapshot, failing over to using VM snapshot.  
23/07/2019 01:31:21 :: Removing VM snapshot  
23/07/2019 01:31:29 :: Queued for processing at 23/07/2019 01:31:30  
23/07/2019 01:31:30 :: Required backup infrastructure resources have been assigned  
23/07/2019 01:35:26 :: VM processing started at 23/07/2019 01:35:26  
23/07/2019 01:35:26 :: VM size: 104.0 GB (97.1 GB used)  
23/07/2019 01:35:26 :: Getting VM info from vSphere  
23/07/2019 01:35:33 :: Creating VM snapshot  
23/07/2019 01:35:44 :: Saving [vfs-sto01-san-04(NL)] myvm-5/myvm-5.vmx  
23/07/2019 01:35:44 :: Saving [vfs-sto01-san-04(NL)] myvm-5/myvm-5.nvram  
23/07/2019 01:35:45 :: Using backup proxy VMware Backup Proxy for disk Hard disk 1 [san]  
23/07/2019 01:35:45 :: Using backup proxy VMware Backup Proxy for disk Hard disk 2 [san]  
23/07/2019 01:35:47 :: Hard disk 1 (64.0 GB) 1.9 GB read at 17 MB/s [CBT] 
23/07/2019 01:35:47 :: Hard disk 2 (20.0 GB) 2.5 GB read at 18 MB/s [CBT] 
23/07/2019 01:42:12 :: Using backup proxy VMware Backup Proxy for disk Hard disk 3 [san]  
23/07/2019 01:42:13 :: Hard disk 3 (20.0 GB) 854.0 MB read at 61 MB/s [CBT] 
23/07/2019 01:42:37 :: Removing VM snapshot  
23/07/2019 01:43:50 :: Finalizing  
23/07/2019 01:43:57 :: Busy: Source 99% > Proxy 29% > Network 2% > Target 0%  
23/07/2019 01:43:57 :: Primary bottleneck: Source  
23/07/2019 01:43:57 :: Network traffic verification detected no corrupted blocks  
23/07/2019 01:43:57 :: Processing finished with warnings at 23/07/2019 01:43:57

답변1

귀하의 애플리케이션이나 인프라의 세부 사항은 모르지만 대부분의 인증서 유효성 검사 절차는 공통된 측면을 공유합니다.

  1. 인증서 존재; 유효한 클라이언트 인증서가 있는지 확인하세요.
  2. 인증서 유효성; 클라이언트 인증서가 만료되지 않았는지 확인하세요.
  3. 신뢰할 수 있는 루트 발급된 인증서의 루트 인증서가 검증 시스템에서 신뢰되는지 확인하세요.
  4. 철회 확인; 발급된 유효한 클라이언트 인증서의 CRL(인증서 해지 목록)이 유효성 검사 시스템에 의해 접근될 수 있는지 확인하십시오.

이전에 이 절차가 작동했고 다른 구성 변경이 발생하지 않은 경우 항목 #2가 원인일 가능성이 높습니다. 항목 #3과 #4는 Active Directory 인증서 서비스 기관을 사용하는 경우와 같이 발급 인증 기관이 내부에 있는 환경에서 인증서 유효성 검사에서 가장 큰 문제가 되는 경향이 있습니다.

관련 정보