Mojave is the fifteenth installment of the Mac OS series released by Apple. It was first released on September 24th 2018. It was the successor to that of the macOS High Sierra. The main things that Mojave brought along with its release was the introduction of some of the apps of the mobile iOS system to the desktop operating system. When it comes to the storage on Mojave OS you might have noticed a section in the breakdown called ‘Other Storage’ which can take up a majority of the storage. Today we are going to tell you how to clear other storage on Mac OS Mojave giving your system more available storage that can be allocated to more important items. This other storage can consist of a diverse range of miscellaneous types of files so it is key to know where to look for these to delete them.
First things first you’re going to want to have a look at your storage breakdown to see just how much storage is being taken up by the other storage. To do this firstly click ‘Finder’ which you will be able to find on your dock of applications. Next go to the top left of the screen and click the Apple Menu logo. At the top of the drop down list you’ll see the option ‘About This Mac’. You’ll nee to go ahead and select that.
When the new window has opened you’ll see different tabs within this window. The third one along is ‘Storage’ and that’s the one we’re going to select. Now it will show you the breakdown in storage for both the hard disk drive and an external storage device if you have one selected. If you hover your cursor over the colored sections on this break down it will show you how much storage is being taken up by things such as Movies, Apps, Photos, Backups and most importantly, Other.
It is vital that you keep on top of your storage when it comes to responsibly managing it and clearly unneeded storage. It may not seem the most important task, however as your disk starts to fill up and you have less and less storage free, this ultimately means that you Mac will start to progressively run slower and slower which can be inconvenient and frustrating. We are going to run through the steps of how to clear other storage on macOS Mojave.
Firstly we are going to want to clear the cache on Mac OS Mojave. Simply put your cache is a type of memory that is stored temporary to make access to frequently used applications such as CPU applications or browsers also have a cache reserve for quick access to frequently accessed website. To delete the cache on Mojave, open “Finder”, click “Go” and select “Go to folder”, you’ll want to go to “~/Library/Cache” and delete the contents of these folders but NOT the folders themselves.
Next to delete the DNS cache, to do this open up terminal and type the following: dscacheutil -flushcache sudo killall -HUP mDNSResponder Press enter and the commands will run and clear your DNS cache.
There are a few different folders you’ll want to delete the contents of in order to clear the amount of storage that ‘Other’ is taking up. There are: ~/Documents/Logs ~/Library/Logs ~/Library/Screen Savers /Library/Caches (without ~) ~/Users/User/Library/Application Support/ ~/Library/Application Support/MobileSync/Backup Browse to each of these folders through your Finder and delete the contents of each but NOT the folders themselves as they need to be kept to store items in future.
Next is to delete any unneeded files from your Downloads folder on your Mac OS. To do this firstly go to your finder and go to users and then select your users and find the ‘Downloads’ folder. In here select and delete any files that you no longer need.
Then empty your trash and this will have feed the space up for future downloads. Make sure that you definitely don’t need these downloads before emptying them from the trash however as then they will be permanently removed. If you don’t want them taking space on your disk but would rather move them to external storage device click ‘Show in Finder’ and drag the files over to the external storage, this means you’ll still have the files but they won’t actively be taking up disk space .
The fourth step in resolving this issue involves deleting any old iOS backups you may not need anymore. These surprisingly can take up a lot of storage so if there’s no need for them to be there we need to get them deleted. To see how much storage they are taking up as before go to Finder > Apple Menu and select About This Mac. Now to the storage tab, you’ll be able to see a colour coded chunk comprised solely of iOS files.
Next click the Manage button and select iOS files from the menu on the left to see the backups you have there. For the ones you no longer need firstly click to highlight them and then press delete to confirm the deletion of this file. Alternatively if you want to move them to an external storage device instead click ‘Show in Finder’ and then drag them onto the external disk.
CleanMyMac X on macOS Mojave
This is an application that monitors and scans your Mac OS Mojave system and recommends data that can be deleted. Firstly to get a scan underway lick the scan button for it to start looking for cache, unused apps, attachments, temporary memory and much more that can be deleted and is of no essential need to the every day running of the system. This application also has a malware scanner that will also scan for any files that may be deemed as malicious or any viruses. To make the application even more user friendly there is a personal assistant that helps you out during scans offering suggestions as to what junk you might want to consider deleting next.
If all of these steps are followed correctly you will have cleared all the other storage and other files that weren’t needed anymore. Not only does this free up space to be used by future applications and downloads but you’ll also see an improvement in the performance and speed of your Mac OS system as the disk has more memory to work with now. This complete guide on how to delete other storage on Mac OS Mojave is designed to be as user friendly as possibly taking you through the process step-by-step. Also be sure to never delete the folders themselves but rather the contents of the folders as it is essential these folders exist for future items to be saved into.
Yesterday I received a call asking for assistance on a VM that was in an inoperative state in a ESX 3.5 environment. There was an active task to create a snapshot which was almost a day old and could not be cancelled. Any attempt to invoke a new task or change the power state resulted in “another task is already in progress”.
The good news here is that VMware has some very good KB articles that do a great job of detailing some of the options here. They have a KB article for ESX with the Service Console and another KB article for ESXi environments.
If you are in an ESX (Service Console) environment you also need to know how to use SSH (you can also use the physical server console or DRAC/ILO/KVM, but I prefer SSH). I use PuTTY which is available here. In an ESXi environment you can use the Remote CLI (which you will want to install on your workstation) to issue the commands as detailed in the ESXi KB article.
Now there may also be times where it is necessary to kill the task (i.e. creating or closing a snapshot) without affecting the VM state. You can follow the procedures in this KB article to restart the management agents on the ESX host or you can play the video below. Just keep in mind that this resets the connection between the host and vCenter and that some tasks (such as closing snaps) can take a long time and in some cases even exceed the timeout in vCenter even though the ESX host is still performing the task. Restarting the agents does not impact what the ESX host is doing (including hosting VMs) beyond resetting the connection with vCenter.
VMware's vCenter Server database acts as VMware's storage repository. In vCenter, dozens of tables store information on resources, clusters, VMware Distributed Resource Scheduler, snapshots, VMware ESX hosts, virtual machines (VMs), alarms, performance statistics, tasks and events, and more.
The problem is that if you have many VMware host servers and VMs in your environment, the database can grow quite large. But this growth comes largely from a few tables that contain task, event and historical statistics (see the descriptions below). Deleting extraneous task and event files from vCenter Server database can save space, boost system performance, speed backup and minimize the chance of database corruption. In this article, we outline how to use Microsoft's SQL Server to delete unneeded information from a vCenter database.
Navigating vCenter table data
But before you can purge files, you should understand vCenter Server's table data. Here is a brief rundown of the kind of information stored in these tables.
Task information. This table contains information on all the tasks performed in vCenter Server
VPX_TASK
Event information – These tables contain information on all the events that occur on vCenter Server. For every event, there is one row in the VPX_EVENT table, which is linked to one or more rows in the VPX_EVENT_ARG by the EVENT_ID field.
VPX_EVENT
VPX_EVENT_ARG
Historical statistics.These tables contain statistical counter information for the hosts and VMs that vCenter Server manages. For vCenter Server 2.0.x servers, this information was stored in a single VPX_HIST_STAT table. But in vCenter Server 2.5, this method has been changed: Daily statistics are now stored in VPX_HIST_STAT1, rolled into VPX_HIST_STAT2 for weekly stats, rolled into VPX_HIST_STAT3 for monthly stats and, finally, into VPX_HIST_STAT4 for yearly stats. Additionally, there are four sample time tables used that correspond to the historical statistic tables.
VPX_HIST_STAT (VC 2.0.x)
VPX_HIST_STAT1 (VC 2.5)
VPX_HIST_STAT2 (VC 2.5)
VPX_HIST_STAT3 (VC 2.5)
VPX_HIST_STAT4 (VC 2.5)
VPX_SAMPLE_TIME1 (VC 2.5)
VPX_SAMPLE_TIME3 (VC 2.5)
VPX_SAMPLE_TIME3 (VC 2.5)
VPX_SAMPLE_TIME4 (VC 2.5)
Click to enlarge.
Purging data with vCenter Server
By changing the statistic interval configuration, you can indirectly purge this data with vCenter Server. When you change a particular interval, only the data for that interval is purged. If you change the weekly interval only, for example, weekly data is purged, but not daily, monthly and yearly data. You can also change the intervals so less data is collected, or disable intervals, which reduces the size of your VPX_HIST_STAT tables.
There are several reasons to delete this data. The first is simply to reduce the amount of space used on the database server. In large environments, such a database can easily be more than 20 GB in size and while this may not be a big deal on a SQL Server running on large local disk, it can be an issue on a database server that uses valuable storage area network (SAN) disk space.
The second reason is performance. The bigger the database, the more time it takes to search for data and to complete database operations such as updating indexes. Finally, the less data you have, the more efficient the database will be and the less likely you are to experience database corruption. It will also take less time to back up the database.
The bottom line is that you should ask yourself whether you really need an extensive history of task and event data. Will you ever review performance data from a year ago? Having old performance data is valuable on occasion for spotting trends. But if you don't need it, get rid of it. Also, consider not collecting this data in the first place. You might just collect the daily and weekly data to use for troubleshooting purposes and disable the longer-term monthly and yearly data.
Checking table size
With SQL commands, you can check the size of your tables. For Oracle databases, use the following SQL commands after you log in to the database with SQL*Plus or another SQL client.
select count (*) from VPX_EVENT This command shows the number of rows (or records) in a table. For the other tables, change the table name.
select num_rows * avg_row_len from user_tables where table_name = 'VPX_EVENT' This command shows the amount of disk space the table is using in bytes, not including free table space.
select bytes from user_segments where segment_name = 'VPX_EVENT' This command shows the amount of disk space the table uses in bytes, including free space.
Click to enlarge.
For SQL Servers, you can use the SQL Query Analyzer tool that is installed as part of SQL server by using the following commands.
In the Query window, type
use <VC database name>
Then type:
EXEC sp_spaceused <table name>
Next, click the Execute Query icon or press F5. This runs the sp_spaceused stored procedure (essentially a SQL server script), which returns information about the table, including the number of rows in use, the amount of disk space in kilobytes that is reserved for the table and the amount of table space that the data takes up. To see the same information for other tables, just repeat these commands with the names of the other tables.
Click to enlarge.
Now that we know about tables and how to determine their size, we can begin purging data from them. In the next part of this tip series, we'll cover how to use the VMware-provided SQL scripts to purge data. Stay tuned.
ABOUT THE AUTHOR:Eric Siebert is a 25-year IT veteran who specializes in Windows and VMware system administration. He is a guru-status moderator on the VMware community VMTN forums and maintains VMware-land.com, a VI3 information site. He is also the author of an upcoming book titled VI3 Implementation and Administration due out in June 2009 from Pearson Publishing and is a regular on VMware's weekly VMTN Roundtable podcast.
For my first article of the year I have chosen a subject that has not been much discussed, however greatly empower VMware View administrators.
VMware View 4.5 allows administrators to configure an external Microsoft SQL Server or Oracle database to record all VMware View events. Prior to View 4.5 the events database was integrated with the local ADAM database, not allowing for external Business Intelligence software integration.
With the events database being external it is now possible to use reporting engines such as Crystal Reports, Cognos, MicroStrategy, and Oracle Enterprise Performance Management to access and analyse the data; it is also possible to create triggers to alert monitoring tools such as SCOM and Nagios.
The events logged are:
End-user actions such as logging in and starting a desktop session.
Administrator actions such as adding entitlements and creating desktop pools.
Alerts that report system failures and errors.
Statistical sampling such as recording the maximum number of users over a 24-hour period.
There are 3 modules to be known and therefore analysed: Admin, Agent and Broker.
Admin – As the name says the Admin module is responsible for reporting the administrative tasks that happen thought the UI, but also include automated tasks such as provision of a new desktop.
Agent – Agent module is responsible for reporting the state of a desktop. This information is provided by the View agent running inside each desktop.
Broker – The broker module provides events and reporting for all brokering related actions, including security, vCenter connectivity amongst others.
The table below determine the breakdown of the 3 modules:
The Events database is ruled by two main data tables (EVTevent and EVTevent_data), two historical tables (EVTevent_historical and EVTevent_data_historical) and one additional support table. Data from the main data tables are purged and moved into the historical data tables based on the settings defined in the UI.
Some of the additional event information found in the EVTevent table include the severity of the event (AUDIT_FAIL, AUDIT_SUCESS, ERROR, INFO), Acknowledgement status, DesktopID etc.
Sizing Events Database
The size of the Events database is dependent on number of users, amount of login/logoff, number and frequency of refresh and recompose operations etc. Fundamentally any action or task in VMware View Manager that happened either through manual intervention or automated process will be logged and recorded.
Star wars separatist frigate. VMware has not published sizing information for the Events database, therefore any numbers I demonstrate here are purely based on my tests and experience deploying VMware View.
On average, during my tests, each desktop consumed 2.5MB of database storage per month. Although it is possible to specify the amount of time to show the events in View Administrator, the data in the historical databases are never deleted and will always be available for external queries.
When sizing the Events database be sure to accommodate requirements for 2 or 3 years of historical data. The math is rather simple: 250 users x 2.5MB x 36 months = 21GB
MS SQL Configuration
Few administrators have had issues when configuring MSSQL for View Events database. There are few steps to be follow in order to get it working correctly. The example below assumes use of MS SQL Server 2005 Express edition; same used by vCenter Server.
MS SQL server uses port 1433 as Default for communication; however VMware has mention to port 1083 for the Events database in some documentation. It will work either way.
Start > All Programs > Microsoft SQL Server 2005 > SQL Server Management Studio Express
Right Click the Server (vCenterSQLEXP_VIM) > Properties
Security > SQL Server and Windows Authentication mode
Connections > Allow remote connections to this server
How To Clear Task And Events In Vmware Windows 10
Create a new Event DB
Within SQL Server Management Studio Express
Right Click Databases > enter a Database name (ViewEvents)
Create a new login
DIN Rail Mounting Hardware are available at Mouser Electronics. Mouser offers inventory, pricing, & datasheets for DIN Rail Mounting Hardware. Fitlet2 vesa mount. UP Core AL Housing include VESA/Din Rear Mount Material: Aluminum Dimension: 77. 69. 70.6 mm Finish: Painting in Matt Black. Optional accessory: DIN-RAIL mounting clip.
Within SQL Server Management Studio Express
Select SQL Server Authentication
Provide Password
Change Default database to the new Event DB (ViewEvents)
Set User Mapping for Event DB (ViewEvents)
Set Default Schema: dbo
Set Database role membership: db_owner & public
Set Status
Grant permission to connect
Enable Login
Check or configure the TCP/IP port used by SQL Server
Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager
SQL Server 2005 Network Configuration > Protocols for SQLEXP_VIM
TCP/IP > Properties
TCP Dynamic Ports
Configure View Manager Event Database
Login to the View Manager Console > https://view-server/admin
May 25, 2017 Last Seed is a primary needs, wellness, and disease overhaul mod. The Last Seed Prologue is an early look at the mod, and an opportunity for you to provide feedback as it is developed. Help steer the course of its development week-by-week. This is also, in a way, a return to form for me. Jun 02, 2017 In today's video we take a look at Last Seed, the primary needs, wellness and disease overhaul from Chesko. Last Seed is one of 5 mods that make up the Skyrim Survival series of mods.
Last Seed is a needs, wellness, and disease survival mod for Skyrim. On the surface, Last Seed presents a streamlined, intuitive primary needs system. Each need is coupled tightly with a primary attribute. Hunger influences, and is influenced by, health and combat actions; thirst, by stamina and acts of exertion; and fatigue. May 25, 2017 Speaking of potions, Last Seed would be superb if it incorporated Chase The Dragon, that one mod that treats potions like 'drugs' and you can't drink them too much unless you want an addiction. Both mods work perfectly together. Last Seed is a primary needs, wellness, and disease overhaul mod. The Last Seed Prologue is an early look at the mod, and an opportunity for you to provide feedback as it is developed. Help steer the course of its development week-by-week.