vSphere

vSphere Replication 8.1 Pre-Freeze and … |VMware Communities

I was just assuming that snapshots are used like with Windows VMs when the Quiesce.Option is set in vSphere Replication, especially because there is no mentioning of Linux-VMs and somehow the Quiesce has to be done…

 

I’ve made a pastebin about the vmware-tools-install script since you can’t use hide-tags here:

VMware Tools Setup SLES11 SP4 – Pastebin.com

 

The SLES Version:

SLES11SP4:/var/log # cat /etc/os-release

NAME=”SLES”

VERSION=”11.4″

VERSION_ID=”11.4″

PRETTY_NAME=”SUSE Linux Enterprise Server 11 SP4″

ID=”sles”

ANSI_COLOR=”0;32″

CPE_NAME=”cpe:/o:suse:sles:11:4″

 

 

The Scripts:

SLES11SP4:/usr/sbin # cat pre-freeze-script

echo “$(date) pre-freeze” >> /tmp/snapshot.log

 

SLES11SP4:/usr/sbin # cat post-thaw-script

echo “$(date) post-thaw” >> /tmp/snapshot.log

 

SLES11SP4:/usr/sbin # ll pre-freeze-script & ll post-thaw-script

[1] 5539

-rwx—— 1 root root 47 Apr  2 16:19 pre-freeze-script

-rwx—— 1 root root 46 Apr  2 16:19 post-thaw-script

[1]+  Done                    ls $LS_OPTIONS -l pre-freeze-script

 

The Logfile which i use to see if the scripts get activated:

SLES11SP4:/usr/sbin # cat /tmp/snapshot.log

Tue Apr  2 16:21:07 CEST 2019 pre-freeze

Tue Apr  2 16:21:11 CEST 2019 post-thaw

Tue Apr  2 16:27:23 CEST 2019 pre-freeze

Tue Apr  2 16:27:26 CEST 2019 post-thaw

Wed Apr  3 10:31:57 CEST 2019 pre-freeze

Wed Apr  3 10:32:00 CEST 2019 post-thaw

Wed Apr  3 13:24:38 CEST 2019 pre-freeze

Wed Apr  3 13:24:41 CEST 2019 post-thaw

Wed Apr  3 13:31:17 CEST 2019 post-thaw

 

All those entries in the snapshot.log where made at the time i manually created a Quiesced Snapshot.

 

 

Unfortunately it seems i don’t have a vmware.log where i can see more details about the snapshot creation

SLES11SP4:/var/log # ll vmware*

-rw——- 1 root root 14953 Apr  2 16:04 vmware-install.log

-rw——- 1 root root   741 Apr  3 09:25 vmware-network.1.log

-rw——- 1 root root   719 Apr  2 10:50 vmware-network.2.log

-rw——- 1 root root   719 Apr  3 09:26 vmware-network.log

-rw——- 1 root root  7882 Apr  3 09:26 vmware-vgauthsvc.log.0

-rw-r–r– 1 root root 15279 Apr  3 12:49 vmware-vmsvc.log

 

 

 

 

Edit:

So… apparently vSphere Replication uses Magic instead of Snapshots… The vmware.log from the SLES11SP4 VM shows only the following if Guest Quiesce is activated:

2019-04-03T13:52:35.199Z| vcpu-1| I125: ToolsBackup: changing quiesce state: IDLE -> STARTED

2019-04-03T13:52:37.201Z| vmx| I125: ToolsBackup: changing quiesce state: STARTED -> COMMITTED

2019-04-03T13:52:37.201Z| vmx| I125: ToolsBackup: changing quiesce state: COMMITTED -> FINISHING

2019-04-03T13:52:39.203Z| vmx| I125: ToolsBackup: changing quiesce state: FINISHING -> IDLE

2019-04-03T13:52:39.203Z| vmx| I125: ToolsBackup: changing quiesce state: IDLE -> DONE

 

If the Guest Quiesce Option is not activated, the vSphere Replication synchronization is not even mentioned in the vmware.log.

 

 

But it does something with the Descriptor and the Disks if you enable/disable Guest OS Quiesce which looks like a snapshot is produced (without triggering the pre-freeze or post-thaw scripts).

 

 

Logfile after activating Guest OS Quiesce:

2019-04-03T13:59:16.807Z| vmx| I125: VigorTransportProcessClientPayload: opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80159: Receiving HotPlugManager.BeginBatch request.

2019-04-03T13:59:16.808Z| vmx| I125: VigorTransport_ServerSendResponse opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80159: Completed HotPlugManager request.

2019-04-03T13:59:16.810Z| vmx| I125: VigorTransportProcessClientPayload: opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80164: Receiving Hbr.SetHBRDiskInfo request.

2019-04-03T13:59:16.810Z| vmx| A100: ConfigDB: Setting scsi0:0.hbr_filter.rdid = “RDID-be9d8477-98ec-42ba-bb84-29c052394a31”

2019-04-03T13:59:16.810Z| vmx| A100: ConfigDB: Setting scsi0:0.hbr_filter.persistent = “hbr-persistent-state-RDID-be9d8477-98ec-42ba-bb84-29c052394a31.psf”

2019-04-03T13:59:16.810Z| vmx| A100: ConfigDB: Setting scsi0:0.filters = “hbr_filter”

2019-04-03T13:59:16.810Z| vmx| I125: VigorTransport_ServerSendResponse opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80164: Completed Hbr request.

2019-04-03T13:59:16.811Z| vmx| I125: VigorTransportProcessClientPayload: opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80165: Receiving Hbr.SetHBRVmConfig request.

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.configGen = “7”

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.gid = “GID-565f3dc3-9934-4126-a63f-b013d7849882”

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.destination = “vSphere Replication Target Appliance

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.port = “31031”

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.rpo = “15”

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.quiesce = “TRUE”

2019-04-03T13:59:16.811Z| vmx| A100: ConfigDB: Setting hbr_filter.netCompression = “TRUE”

2019-04-03T13:59:16.814Z| vmx| I125: Hbr Vigor: HbrSetVmConfig done. Reloading vscsi filters.

2019-04-03T13:59:16.815Z| vmx| I125: VigorTransport_ServerSendResponse opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80165: Completed Hbr request.

2019-04-03T13:59:16.816Z| vcpu-0| I125: Destroying virtual dev for scsi0:0 vscsi=9305

2019-04-03T13:59:16.816Z| vcpu-0| I125: VMMon_VSCSIStopVports: No such target on adapter

2019-04-03T13:59:16.822Z| vmx| I125: VigorTransportProcessClientPayload: opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80169: Receiving HotPlugManager.EndBatch request.

2019-04-03T13:59:16.824Z| vcpu-0| I125: Closing all the disks of the VM.

2019-04-03T13:59:16.824Z| vcpu-0| I125: Closing disk ‘scsi0:0’

2019-04-03T13:59:16.824Z| vcpu-0| I125: DISKLIB-VMFS  : “/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4-flat.vmdk” : closed.

2019-04-03T13:59:16.824Z| vcpu-0| I125: Checkpoint_Unstun: vm stopped for 9993 us

2019-04-03T13:59:16.826Z| vcpu-0| A100: ConfigDB: Setting scsi0:0.redo = “”

2019-04-03T13:59:16.826Z| vcpu-0| I125: DISK: OPEN scsi0:0 ‘/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4.vmdk’ persistent R[]

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISKLIB-VMFS  : “/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4-flat.vmdk” : open successful (10) size = 21474836480, hd = 7431621. Type 3

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISKLIB-DSCPTR: Opened [0]: “SLES11SP4-flat.vmdk” (0xa)

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISKLIB-LINK  : Opened ‘/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4.vmdk’ (0xa): vmfs, 41943040 sectors / 20 GB.

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISKLIB-LIB   : Opened “/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4.vmdk” (flags 0xa, type vmfs).

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISK: Disk ‘/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4.vmdk’ has UUID ’60 00 c2 9c cc d0 0c 21-1b ae e6 d1 51 8b 28 42′

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISK: OPEN ‘/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4.vmdk’ Geo (2610/255/63) BIOS Geo (0/0/0)

2019-04-03T13:59:16.827Z| vcpu-0| I125: Creating virtual dev for ‘scsi0:0’.

2019-04-03T13:59:16.827Z| vcpu-0| I125: DumpDiskInfo: scsi0:0 createType=11, capacity = 41943040, numLinks = 1, allocationType = 1

2019-04-03T13:59:16.827Z| vcpu-0| I125: SCSIDiskESXPopulateVDevDesc: Using FS backend

2019-04-03T13:59:16.827Z| vcpu-0| I125: DISKUTIL: scsi0:0 : geometry=2610/255/63

2019-04-03T13:59:16.831Z| vcpu-0| I125: SCSIFilterESXAttachCBRCInt: CBRC not enabled or opened without filters,skipping CBRC           filter attach.

2019-04-03T13:59:16.831Z| vcpu-0| I125: SCSIFilterSBDAttachCBRC: device scsi0:0 is not SBD. Skipping CBRC attach SBD way.

2019-04-03T13:59:16.831Z| vcpu-0| I125: VMXNET3 user: Ethernet0 Driver Info: version = 16850432 gosBits = 2 gosType = 1, gosVer = 0, gosMisc = 0

2019-04-03T13:59:16.831Z| vmx| I125: VigorTransport_ServerSendResponse opID=ba8a47e2-1d40-44da-9cf8-eab7621979f4-HMS-148065-8-e0-cf2c-cf2d seq=80169: Completed HotPlugManager request.

2019-04-03T13:59:29.983Z| vcpu-0| I125: HBACommon: First write on scsi0:0.fileName=’/vmfs/volumes/5c63d5b3-716a68f4-6f0d-005056ab0b5d/SLES11SP4/SLES11SP4.vmdk’

2019-04-03T13:59:29.983Z| vcpu-0| I125: DDB: “longContentID” = “d6e4136fd3baca7512ddc27f1869e967” (was “9b4da3aa293d1edfdc281907a96f4e3c”)

2019-04-03T13:59:30.003Z| vcpu-0| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0xa96f4e3c, new=0x1869e967 (d6e4136fd3baca7512ddc27f1869e967)


Source link

Tags

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Close