hello Colleagues I'm experiencing the following puzzling problem...
when I execute the backup on one vcsa v.6.5 all goes well (duration +/- 30min). When I call for backup from remote using the following script it takes few seconds and it backups few files only:
C:\Scripts\Pro\VCSA-Backup\Backup-vMGMT.ps1 -vcenter vcsa12 -vcsa $true -ftpip 'x.x.x.x' -executionpolicy bypass
the same script is used for many more vcenter servers and they all go well. Only this vcenter is giving me problems. PSC was externalised long time ago and cannot merge it back as yet. It will be, but the other vcenter servers are in the same situation and don't give problems. I have the impression that the process to externalize psc didn't complete successfully.
also in the backup-metadata.json I read:
"HashAlgorithm": "sha256",
"SizeInfo": {
"/dev/mapper/dblog_vg-dblog": 6,
"/dev/mapper/db_vg-db": 9943,
"/dev/mapper/imagebuilder_vg-imagebuilder": 6,
"/dev/mapper/netdump_vg-netdump": 6,
"/dev/mapper/core_vg-core": 9943,
"cpu": 2,
"/dev/mapper/log_vg-log": 9943,
"/dev/mapper/autodeploy_vg-autodeploy": 6,
"memory": 3942,
"/dev/mapper/updatemgr_vg-updatemgr": 6,
"/dev/mapper/seat_vg-seat": 6,
"/dev/sda1": 119,
"/dev/sda3": 10829
},
"NodeType": "infrastructure",
"Compression": "gzip",
"DomainName": "vsphere.local",
"Encrypted": "False",
"Messages": "Full Backup vcsa12-06/25/2020 13:32:16.ToString('yyyy-MM-dd')",
"BackupSize": 795560635,
"Parts": [
"common"
],
"Duration": "0:00:47.511255",
"PNID": "psc1",
"EndTime": "2020-06-25T11:33:18.310Z",
"DcPort": 443,
"Build": "16275158"
while in the successful backup the same file reads:
"HashAlgorithm": "sha256",
"SizeInfo": {
"/dev/mapper/dblog_vg-dblog": 14982,
"/dev/mapper/log_vg-log": 9943,
"/dev/mapper/imagebuilder_vg-imagebuilder": 9943,
"/dev/mapper/netdump_vg-netdump": 984,
"/dev/mapper/core_vg-core": 50260,
"cpu": 4,
"/dev/mapper/db_vg-db": 9943,
"/dev/mapper/autodeploy_vg-autodeploy": 9943,
"memory": 16038,
"/dev/mapper/updatemgr_vg-updatemgr": 100657,
"/dev/mapper/seat_vg-seat": 554227,
"/dev/sda1": 119,
"/dev/sda3": 10829
},
"NodeType": "management",
"Compression": "gzip",
"DomainName": "vsphere.local",
"Encrypted": "False",
"PSCNode": [
"psc1"
],
"Messages": "Pre U3j patching",
"BackupSize": 11457269690,
"Parts": [
"common",
"seat"
],
"Duration": "0:31:07.083554",
"PNID": "vcsa12",
"EndTime": "2020-06-25T08:28:03.599Z",
"DcPort": 443,
"Build": "13638625"
I'm afraid that it is indeed a PSC-VCSA thing.
Good luck.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
What is in that .ps1 script?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
the Brian Graf's modules PowerCLI-Example-Scripts/Backup-VCSA.psm1 at 6ca366e8c4f46d5e412ed17024e12e9bb7e59a69 · rmbolger/Pow... It works on any other vcenter server but this.
Can you check in /var/log/vmware/applmgmt/applmgmt.log if there is any additional info on what goes wrong?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
this afternoon I'll go back there and check
unfortunately such file does not exist
Are there any other files (like backup.log) in the /var/log/vmware/applmgmt folder?
Anything in there?
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference
yes, the backup.log which was three lines long and it reported that the PNID is the fqdn of the vcsa and it also reported the IP address which was correct. There is a mismatch of info with what seen when running the script.. where the psc shows to be the vcsa.. while the psc is external. I'm trying to find on the web the article that lists the steps to externalize the psc. I'm thinking to go over it and see where some files maybe are not coherent with the architecture in place So I'm guessing nothing to do with the PowerCLI here.. thanks anyway!!
I'm afraid that it is indeed a PSC-VCSA thing.
Good luck.
Blog: lucd.info Twitter: @LucD22 Co-author PowerCLI Reference