vSphere 6.0 update sequence KB 2109760 says to update SSO and vCenter before upgrading VDP.  I have a lot of customers that want to take advantage of the VDPA features that are now included with VDP 6.0 but don't want to upgrade the rest of vSphere for several months.  What is the downside with upgrading or deploying VDP 6.0 on vCenter 5.5?

The VDP 6.0 Admin guide says its compatible with vCenter 5.5 and 5.1 (see page 20).  Although the Interoperability Matrix says VDP 6.0 only supports vCenter 6.0 and 5.5.  Is the admin guide or interoperabiltiy matrix wrong about using VDP 6.0 with vCenter 5.1?

Hi all,

Can you anyone advise me how troubleshooting this issue.

Configuring VDP is stuck at 20%.

See the screenshots in the attachment.

Version VDP - 6.1.3.

Thank you for your help

Ales

.

VDP 6.1.3.70   config screen "vCenter Registration" Fields are correct, test connection fails with message "Unable to connect to the provided SSO server/port combination. Please re-check values and try again."

Host ESXi 6.0 4600944

VCSA  6.0.0.20000

VCSA PSC 6.0.0.20000

Tested VDP login via web to VCSA, logs fine. Network adapters moved from DVS to standard switch, no change.

DNS entries have been checked.

All 3 VMs reside on same host.

Any help? Any additional information needed?

We have recently deployed qty(2) VDP appliances and loaded the patch so they are accessible in the vCenter web client. However, we also need to deploy some external proxies to backup some VMs via Hot-Add. However, after logging into the configuration portal for the VDP appliance and selecting "Add external proxy", the first page displaying Host and Storage contains blank drop down menus with no hosts available to select. I couldn't find any posts about this, any ideas?

This is VDP version 6.1.2, vCenter 6.0U2 and a mix of ESX 5.5/6.0. I did redeploy an appliance to be on the same subnet as vCenter, with similar results.

Good afternoon people

I am updating my VDP from 6.1.2 to the current version 6.1.3, but after all configuration and restart of the Appliance .... it also caught:

VDP: Configure appliance (20%)

More than 2 hours ago and it does not go out of this status, has anyone been through this?

Hi there,

we currently hace at the office 2 ESXi hosts with a SAN using FreeNAS.

We recently got a third ESXi that we want to set up in another physical location outside the office but connected through a VPN network, so we can backup our environment at the office and send it somehow to that new ESXi.

What is the simplest set up you would do in this case? We don't need HA, but somehow send a daily backup of all the VMS and Datastores and somehow manually recover the VMS and data in that third ESXi so we can keep working, even if is not with a great performance. The downtime can be some hours.

Thank you

Is it feasible to Image & Restore a Windows Server OS from within a Virtual Machine?

It seems like it would be feasible. However, I have no experience with this situation.

It seems like you could install an Imaging Solution on the Windows OS of a Windows VM and schedule image backups to an external backup server. If the VM that you imaged gets corrupted and you want to restore an image you could boot the VM from the Imaging Solution's WinPE Recovery Media and restore the latest image from the backup server. Of course, you would have add the appropriate Network Drivers to the WinPE Recovery Media when you build it.

Would this idea work?

The reason that I ask this is that I have a bunch of VM's that are being backed up from a VM using Veeam. I was told that if the Veeam backup VM every had problems that I could just install Windows again, install Veeam again followed by loading the Veeam backup configuration file which is being backed up weekly to another server. This seems like a lot of work, especially since you have to install all of the Windows patches again. Note: A Veeam backup VM cannot backup itself.

I know about VDP backups.  I have never used the VDP backup function.  However, I don't want to use space on my Datastore to store the backups.  I would prefer to backup to a couple of NAS Servers.

Note:  Someone told me about the simplicity of copying the contents of VM's folder on the DataStore.  However, the disk allocation size is about 600 GB and it would take a long time to copy that much uncompressed data across a network.

Thanks in Advance.

Hi, At the beginning I'm sorry, but I don't speak English well.

I have the following problem. When making copies (backup) using the VDP - jobs is suspended. After a long time I had to finish the job manually. Then the job is finished, but remained snapshot. Following more I removed snapshot. Then he showed a message "virtual machine disks consolidation is needed", but in the console snapshot manager - snapshot is gone.

In the configuration dialog guest (vSphere Client) - disk configuration is set to file, which is a snapshot (xx-Server-000001.vmdk).

In the configuration file xx-Server-000001.vmdk it is used in the virtual disk xx-Server-000001-delta.vmdk. In the virtual machine working location are:

Please help to reverse this situation and not lose the new data

Good morning

Someone already got this error in VDP 6.1?

root@vdp01://#: mccli activity show --active=true

1,22801,User login failure.

Attribute Value

--------- --------------------

reason    Locked user account.

Hi,

So here's the setup :

1 x vcenter

2 x ESXi

Very small setup. Not a lot of VM (it's a lab). Now we need to backup VM from time to time but the boss doesn't want to pay.

So I looking for a tool that :

1- Can do backup of VM while they are running (a tool that create a snapshot for application-consistency ?)

2- Don't need file recovery inside vm. Just need a tool that makes a backup of vmx, vmdk, etc.. and dump it in a folder (so I can backup this backup offsite)

3- can connect to vcenter

4- can schedule backup

5- free

I tried like 10 apps and it seems none of them can do all of this (most of the time free version of apps can't schedule backup)

VDP was easy to setup but the backup are stored within vmdk of VDP which I found to be a pain in the .... There must be a tool that juste backup to a simple folder.

thank you !

I was trying to restore a backup crash-consistency. The process of restore works great, but when i try to power up the VM  the system say that Operation System not found. In the boot menu i can't found any virtual disk. Anyone can help me?

Hi

We have a VMWare setup with 2 Nodes as below.

1. Physical Machine - Windows Server 2008 With vCenter 5.1

2. 2 Physical Hosts Running ESXi 5.1.0 HP Custom

We would like to upgrade the setup to 6.0 version with the conditions.

A. System is live & running 6 Virtual Machine, a minimum downtime is needed.

B. What should be the sequence for upgrade, first vCenter upgrade or ESX

C. Could we move all VMs to one ESX & upgrade the setup with 1 vCenter & 1 Node, then move all VMs to upgraded setup & then upgrade the rest & add to the cluster.

Kindly guide.

Thanks a lot!

Hey guys,

With a fresh VDP 6.1.3 install on top of vSphere 6.5, most backup jobs hang at 92%.  This is not the issue documented in the release notes, and the backups almost never complete. I DID NOT have this issue with VDP 6.1 under vSphere 6.0.

I have tried backing up photon OS machines, centos 6.5 machines, centos 6.6+ machines, and centos 7 machines.  So far the only ones to successfully complete are some of those old centos 6.5 ones.  I'm not sure if the O/S version is a red herring here, or if it's related to some other pattern I just can't identify at the time.

I have tried backing up images with the quiesce option both on and off, and it doesn't seem to make a difference in the result.  The backups hang regardless and are unsuccessful.

I should mention the storage was created along with the appliance and is on VSAN, if that makes any difference, but - this absolutely all worked with VDP 6.1 and vSphere 6.0.

I looked in a failed job's vmimage log in /usr/local/avamarclient/var/ and noticed this at the end:

2017-01-17T04:02:15.693+04:00 avvcbimage Info <9679>: Virtual disk connection to '[vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1.vmdk' has been closed
2017-01-17T04:02:15.693+04:00 avvcbimage Info <19718>: Found Disk from Device Key: '2001'.
2017-01-17T04:02:15.693+04:00 avvcbimage Info <9674>: virtual disk [vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1_1.vmdk will be connected readonly
2017-01-17T04:02:15.693+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_OpenEx: Open a disk.

2017-01-17T04:02:15.693+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_GetNfcTicket: Get NFC ticket for [vsanDatastore-Neo-Cloud] 50c54958-6741-9944-301e-001ec93c076e/photonos-2cpu-4gb-is-vcpsc1_1.vmdk.

2017-01-17T04:02:16.008+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: Request RandomAccessRO diskKey = 2001, readOnly = 1, openSnapshot = 0.

2017-01-17T04:02:16.094+04:00 avvcbimage Info <16041>: VDDK:VixDiskLibVim: VixDiskLibVim_FreeNfcTicket: Free NFC ticket.

2017-01-17T04:02:16.101+04:00 avvcbimage FATAL <5889>: Fatal signal 11 in pid 15065
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  FATAL ERROR: <0001> uapp::handlefatal: Fatal signal 11
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006b93b1
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba127
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba44b
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000006ba53e
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 0000000000628810
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56c90850
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5050193f
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5051c277
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5051c75e
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5052b142
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e5052b678
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56ecab73
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56ecb123
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004284bc
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004291f9
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00000000004993c4
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 000000000070ac4c
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e56c88806
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  | 00007f2e558cd9bd
2017-01-17T04:02:16.103+04:00 [VcbImageBackupAssistThread]  ERROR: <0001> uapp::handlefatal: aborting program pid=15065, sig=11
2017-01-17T04:02:16.103+04:00 avvcbimage FATAL <5890>: handlefatal: Aborting program with code 176, pid=15065, sig=11
2017-01-17T04:02:16.103+04:00 avvcbimage Info <16041>: VDDK:VixDiskLib: VixDiskLib_Exit: Unmatched Init calls so far: 1.

2017-01-17T12:00:07.999+04:00 avvcbimage Info <40660>: vcbimage_progress::terminate

the log ends there.

This looks serious to me, but it's hard to figure out where to go from here.

Does anyone have any advice as to how to proceed?

Thanks for any assistan

Hi,

I tried to upgrade from 6.1.2.19 to 6.1.3, in order to upgrade vmware to 6.5

It failed, because after upgrade I'm still in 6.1.2 and MCS service is down.

Itried to retart or force retore it, without success.

Here is what I found in log :

2017/01/19-19:47:50 dpnctl: INFO: subsystems to act upon: mcs

2017/01/19-19:47:50 dpnctl: INFO: subsystems not to act upon: maint, cron, firewall, axionfs, sched, avi, emt, gsan

2017/01/19-19:47:50 /bin/touch /var/lock/subsys/zzdpn

2017/01/19-19:47:50 INFO: environment variable USERNAME is undefined or empty

2017/01/19-19:47:50 /usr/bin/ssh-agent /bin/bash -c '/usr/bin/ssh-add /home/dpn/.ssh/dpnid && /tmp/dpnctl-run-self.5310'

2017/01/19-19:47:51 dpnctl: INFO: ======= dpnctl 7.2.80-118 (1.139) RESTARTING at 2017/01/19-20:47:51 CET (UTC +0100), running as admin =======

2017/01/19-19:47:51 dpnctl: INFO: log file time stamps are in UTC; local time is 2017/01/19-20:47:51 CET (UTC +0100)

2017/01/19-19:47:51 dpnctl: INFO: PATH=/opt/emc-tools/bin:/usr/local/avamar/bin:/sbin:/usr/sbin:/usr/local/avamar/bin:/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/local/apache/bin:/usr/local/ssl/bin:/opt/vmware/bin

2017/01/19-19:47:51 dpnctl: INFO: Argument list: "--mcs_user=root" "start" "mcs"

2017/01/19-19:47:51 dpnctl: INFO: subsystems to act upon: mcs

2017/01/19-19:47:51 dpnctl: INFO: subsystems not to act upon: maint, cron, firewall, axionfs, sched, avi, emt, gsan

2017/01/19-19:47:51 INFO: environment variable USERNAME is undefined or empty

2017/01/19-19:47:51 [ pid = 5371 ]

2017/01/19-19:47:51 /usr/bin/ssh-add -l

2017/01/19-19:47:51 The agent has no identities.

2017/01/19-19:47:51 INFO: environment variable USERNAME is undefined or empty

2017/01/19-19:47:51 [ pid = 5371 ]

2017/01/19-19:47:51 /usr/bin/ssh-add -l

2017/01/19-19:47:51 The agent has no identities.

2017/01/19-19:47:51 /usr/bin/ssh-add /home/admin/.ssh/dpnid

2017/01/19-19:47:51 Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)

2017/01/19-19:47:51 [ pid = 5371 ]

2017/01/19-19:47:51 /usr/bin/ssh-add -l

2017/01/19-19:47:51 3072 dc:c8:3e:84:f5:99:88:b7:49:07:3f:b8:8b:ee:be:34 [MD5] /home/admin/.ssh/dpnid (RSA)

2017/01/19-19:47:51 dpnctl: INFO: no update context, so not checking for MCS and EMS restore indication

2017/01/19-19:47:51 gsan status check:

2017/01/19-19:47:51 - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:47:51 server up: idle

2017/01/19-19:47:51 - - - - - - - - - - - - - - - END

2017/01/19-19:47:51 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1

2017/01/19-19:47:53 dpnctl: INFO: "([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1" - exit status 0

2017/01/19-19:47:53 /bin/cat /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:47:53 [ "/bin/cat /tmp/dpnctl-get-mcs-status-output-5371" exit status = 0 ]

2017/01/19-19:47:53 dpnctl: INFO: - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:47:53 INFO: Administrator Server status: down

2017/01/19-19:47:53 dpnctl: INFO: - - - - - - - - - - - - - - - END

2017/01/19-19:47:53 /bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1

2017/01/19-19:47:53 [ "/bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1" exit status = 0 ]

2017/01/19-19:47:53 dpnctl: INFO: "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test" exit status = 2

2017/01/19-19:47:53 rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:47:53 dpnctl: INFO: "rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371" - exit status 0

2017/01/19-19:47:53 rpm -q --quiet connectemc

2017/01/19-19:47:53 dpnctl: INFO: "rpm -q --quiet connectemc" - exit status 1

2017/01/19-19:47:53 gsan status check:

2017/01/19-19:47:53 - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:47:54 server up: idle

2017/01/19-19:47:54 - - - - - - - - - - - - - - - END

2017/01/19-19:47:54 dpnctl: INFO: Starting MCS...

2017/01/19-19:47:54 dpnctl: INFO: [no passthrough options found for program "mcserver.sh" in context "start"]

2017/01/19-19:47:54 dpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-mcs-start-output-5371

2017/01/19-19:47:54 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start ; echo $? >/tmp/dpnctl-mcs-start-status-5371) >/tmp/dpnctl-mcs-start-output-5371 2>&1

2017/01/19-19:48:02 dpnctl: INFO: "([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start ; echo $? >/tmp/dpnctl-mcs-start-status-5371) >/tmp/dpnctl-mcs-start-output-5371 2>&1" - exit status 0

2017/01/19-19:48:02 /bin/cat /tmp/dpnctl-mcs-start-output-5371

2017/01/19-19:48:02 [ "/bin/cat /tmp/dpnctl-mcs-start-output-5371" exit status = 0 ]

2017/01/19-19:48:02 /bin/cat /tmp/dpnctl-mcs-start-status-5371 2>&1

2017/01/19-19:48:02 [ "/bin/cat /tmp/dpnctl-mcs-start-status-5371 2>&1" exit status = 0 ]

2017/01/19-19:48:02 output of "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start":

2017/01/19-19:48:02 - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:48:02 Database server is running...

2017/01/19-19:48:02 INFO: Starting messaging service.

2017/01/19-19:48:02 INFO: Started messaging service.

2017/01/19-19:48:02 === BEGIN === check.mcs (prestart)

2017/01/19-19:48:02 check.mcs                        passed

2017/01/19-19:48:02 === PASS === check.mcs PASSED OVERALL (prestart)

2017/01/19-19:48:02 Starting Administrator Server at: Thu Jan 19 20:47:59 CET 2017

2017/01/19-19:48:02 Starting Administrator Server...

2017/01/19-19:48:02 java.net.SocketException: java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)

2017/01/19-19:48:02 - - - - - - - - - - - - - - - END

2017/01/19-19:48:03 dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" - exit status 1

2017/01/19-19:48:03 rm -f /tmp/dpnctl-mcs-start-status-5371 /tmp/dpnctl-mcs-start-output-5371

2017/01/19-19:48:03 ([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1

2017/01/19-19:48:04 dpnctl: INFO: "([ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test ; echo $? >/tmp/dpnctl-get-mcs-status-status-5371) >/tmp/dpnctl-get-mcs-status-output-5371 2>&1" - exit status 0

2017/01/19-19:48:04 /bin/cat /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:48:04 [ "/bin/cat /tmp/dpnctl-get-mcs-status-output-5371" exit status = 0 ]

2017/01/19-19:48:04 dpnctl: INFO: - - - - - - - - - - - - - - - BEGIN

2017/01/19-19:48:04 INFO: Administrator Server status: down

2017/01/19-19:48:04 dpnctl: INFO: - - - - - - - - - - - - - - - END

2017/01/19-19:48:04 /bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1

2017/01/19-19:48:04 [ "/bin/cat /tmp/dpnctl-get-mcs-status-status-5371 2>&1" exit status = 0 ]

2017/01/19-19:48:04 dpnctl: INFO: "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --test" exit status = 2

2017/01/19-19:48:04 rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371

2017/01/19-19:48:04 dpnctl: INFO: "rm -f /tmp/dpnctl-get-mcs-status-status-5371 /tmp/dpnctl-get-mcs-status-output-5371" - exit status 0

2017/01/19-19:48:04 dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

2017/01/19-19:48:04 rm -f /usr/local/avamar/var/dpnctl.lck

2017/01/19-19:48:04 ======= dpnctl 7.2.80-118 (1.139), running as admin, RETURNING at 2017-01-19 20:48:04 CET =======

2017/01/19-19:48:04 [user "admin"] program (pid 5371) exit status = 1 (error)

2017/01/19-19:48:04 ======= dpnctl 7.2.80-118 (1.139), running as root, ENDING at 2017-01-19 20:48:04 CET =======

2017/01/19-19:48:04 [user "root"] program (pid 5310) exit status = 1 (error)

I always see this : INFO: environment variable USERNAME is undefined or empty

I'm able to connect via the web client, but can't even call a rollback.

I also destroyed my snapshot, because at the end of the update process everything seemed to be good.

If someone can help me ! Otherwise I think I will have to delete and reinstall it, loosing my backups...

HI,

I am really struggling to get my VDP plugin running in webclient 6.5 after the upgrade.

I Can se the VDP plugin 6.1 under Administration--> plugins, but not on the start page of the web client.

all the services on the VDP are running, I have tried to remove the extensions com.vmware.vdp and tried to re-register the VDp on vCenter bit it does not work. Anybody that can help me with this issue.? I am out of ideas... I am using Winows based vcnter.

Hello.

Anyone using replication here ? I'm thinking about replication to to other location, we have VDP 6.1 (not advanced), and, according to docs, there is still a product called  RTI (Replication Target), available only in version 5.8, that does not need an additional license. Could I install free ESXi on remote location, install that RTI and use replication ?

Is it possible to force the integrity check to a certain time, we've set the the maintenance window but integrity check always occurs 15:00-16:00, which is outside of the mantenance window.  It seems that it ignores the configuration so is there a setting or command that defines this?

Hi!

I'm looking how could be automated "Site pair" in Site Recovery -> Sites -> site_address in "Summary" tab (as shown on the picture):

Any kind of scripting is acceptable (PowerCLI, esxcli, "magic commands" , whatever) just to be automated without user interaction.

Thank in advance for your help!

Hi,

I installed VDP appliance (5.1.1). Registered to the vcenter, setup several backup jobs. The appliance worked for 2 months quite reliably, but suddenly  something happened and I cannot start any job. Neither scheduled  not manual. The Web GUI reports that the job was succesfully scheduled, but the backup does not start. The problem lasts 2 weeks.

I have restarted VDP several times, executed integrity checks, but it does not help.

All appliance services are running (checked by health check by VDP web interface):

VDP status in Vcenter Web Client is "Normal" :

I have noticed, that in /space/avamar/var/mc/server_log/mcserver.log.0 there are lot of  repeating messages :

03/07-02:17:59.00667 com.avamar.mc.wo.JobScheduler._gotVmWork
WARNING: Backup job skipped because server is read-only
03/07-02:17:59.00667 com.avamar.mc.wo.JobScheduler.gotReadOnlyWork
FINE: bug 4261 --- checking for readonlywork
03/07-02:17:59.00667 com.avamar.mc.cr.bcConnection.sendWOReply

The time of the message is evidently in backup window. It seems, that the appliance is internally in readonly mode for some reason, but i am not able find out why.

     Any ideas ?

          Thanks

               Jiri

I currently have a VDP 6.1 appliance with 12TB of stoage capacity. I'm using less than 1TB (it has been set up for a year). Is there a way to reduce the capacity? Ideally, I would like to reduce it to 4TB.