How to purge local repository ?

DCIM_Support · ‎2020-07-02

Hi All,

As I received warning: Filesystem for repository Local reports 200.8 MB free, which is less than the failsafe amount of 206.3 MB. Marking this repository as FULL.

(com.netbotz.server.services.repository.impl.RepositoryCapacityJob)

That caused upgrade from 7.2.5 to 7.2.6 failed.

I currently using Remote Struxureware Repository, and Struxureware Server doest not let me select the Local Repository to Run Manual Purge. Please help

Thanks,

Minh

DCIM_Support · ‎2020-07-02

Minh,

Since the local hard drive is so small, once this issue is resolved I suggest selecting the option to use remote storage only. The local disk of 4.03 gig (the rest is for the OS) is full as per your screenshots. What I suggest is turning off the server, adding another drive of at least 20 gig (preferably more) via the VMware administrative interface (probably Vsphere), and then restarting the server. When that is done, create a backup and try your upgrade again. Do NOT try to increase the current drive size as that will not work and can only cause issues.

Steve

See Answer In Context

DCIM_Support · ‎2020-07-02

Hi Minh,

If you are using remote repository only then it may not allow you to choose local when purging. Is this a VM? If it is a VM, how many hard drives are associated with the VM? What is the size of the default drive? What are your repository and purge settings? How much free space is there on the remote share?

Steve

DCIM_Support · ‎2020-07-02

Hi Steven,

Thanks for your respond. Below is our details of VM:

. Is this a VM? Yes, it's VM

.How many hard drives? There is only one 18 Gb hard drive

.What are your repository and purge settings? and How much free space is there on the remote share? See images below

Thanks,

Minh

DCIM_Support · ‎2020-07-02

Minh,

Since the local hard drive is so small, once this issue is resolved I suggest selecting the option to use remote storage only. The local disk of 4.03 gig (the rest is for the OS) is full as per your screenshots. What I suggest is turning off the server, adding another drive of at least 20 gig (preferably more) via the VMware administrative interface (probably Vsphere), and then restarting the server. When that is done, create a backup and try your upgrade again. Do NOT try to increase the current drive size as that will not work and can only cause issues.

Steve

DCIM_Support · ‎2020-07-02

Hi Steven, Thanks for your solutions. The VM struxureware upgraded succesfully without any problems. Regards, Minh

DCIM_Support · ‎2020-07-02

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.