Skip to main content

· 6 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over October 2023.

There were four Comet software releases during October, all in the 23.9.x Voyager release series.

VMware support

Comet 23.9.7 adds support for backing up VMware virtual machines.

This has been a long-standing request on our Feature Voting page. After running a successful beta program over the last few months, we're very happy to be able to deliver this feature to partners in our Voyager track.

Comet's new VMware Protected Item type allows you to easily connect to your ESXi or vCenter server. You can pick individual VMs for backup across all datacenters, or choose "All VMs" to ensure all VMs are backed up with targeted exclusions.

The feature supports Changed Block Tracking. After completing an initial backup job, any future backup jobs will coordinate with the VMware host server to identify which ranges of the disk have changed since the previous backup job. These changed ranges from the VMware server are adapted into content-defined boundaries for Comet's deduplicating chunking engine. This results in an extremely efficient, incremental-forever backup.

As this is a new Protected Item type, it must be configured to run from an installed device that will perform the compression and encryption workload. Installing Comet Backup on a VM within the VMware server itself is recommended for reduced end-to-end latency. In this first released version in Comet 23.9.7, this feature requires the device to be running Windows x86_64.

We are excited to bring this new Protected Item type to our entire Comet Community, so look out for our upcoming quarterly software release at the end of this month. We'd love your feedback and are here to help if you need any assistance getting started, reach out via our support ticket system.

Comet Storage powered by Wasabi

It's official - Comet Storage is a new cloud storage offering from Comet, in partnership with Wasabi. We offer Wasabi's same great S3-compatible service, at no additional cost above their public pricing. The feature is fully integrated and managed from within your account.cometbackup.com account, giving you unified billing and reporting across both cloud storage and your backup software licenses.

Comet Backup will continue to support a wide range of cloud storage providers. However, the new all-in-one Comet Storage offering is both highly convenient and excellent value. If you are interested in migrating to Comet Storage from an existing Wasabi account or from another cloud provider, please contact us for migration assistance.

Comet Storage also supports S3 Object Lock, allowing the backed-up data to be marked as immutable. This is a complete defense against ransomware attacking the backup storage location itself, giving you a fixed number of days to identify and mitigate the issue. In the latest version of Comet, we've also made Object Lock easier to use for all supported Object Lock-compatible providers, by simplifying the configuration options for both Storage Vaults and Storage Templates.

For more information, please see the documentation, or check out our latest YouTube video:

New account.cometbackup.com user interface design

The next time you log in to the account.cometbackup.com system, you'll see a brand new user interface.

Every element on the page has been given a fresh coat of paint - from buttons to popups, from paying your bill to raising a support ticket. We've also grouped some pages together in a more logical way, so you'll find it simpler to make your way around the site.

Inspired by the similar change to the Comet Server web interface earlier this year, the new design has moved the main navigation bar from the top to the left-hand side. This change brings our branding more closely in line across these two interfaces. On devices with smaller screens, such as laptops and tablets, you can click the small arrow button to collapse the navigation bar and regain horizontal screen real estate.

Virtual disk restore

Comet supports backing up physical Disk Images, Hyper-V virtual machines, and VMware virtual machines. All of these different Protected Item types result in virtual disk files. Comet supports granular restore for all three types, allowing you to browse through partitions and supported filesystems, to restore individual files from within a full disk backup.

In the latest versions of Comet, we've significantly improved the speed of granular restores from Disk Image backups. Some particular use-cases seeing a large improvement are granular restores involving a large number of directories, or a large quantity of small files. We're committed to continuing to improve Comet's performance and this work has identified more opportunities for improvement across all three types, so watch this space!

We've also added a feature to restore Disk Image backup jobs as VMware vSphere-compatible virtual disks.

Both Disk Image and our new VMware Protected Item type generate virtual *.vmdk files inside Comet's deduplicated Storage Vault. However, the subformat of the files does differ slightly. Until now, users who are using Comet to perform a physical-to-virtual (P2V) migration from a physical disk to a VMware virtual machine have been required to perform an extra file format conversion after the restore, requiring extra time and temporary disk space. With the new option in Comet to restore the disk in VMware vSphere-compatible file format, the conversion takes place dynamically as part of the restore job, simplifying the process and helping meet your recovery time objective (RTO).

Audit logging

Earlier this year, we added Audit Logging support to the self-hosted Comet Server product, to help our partners meet their compliance obligations. Since then, we've expanded the list of audit properties, and added a helpful option to configure this feature directly from the Comet Server web interface from the Settings page on the "License & Access" tab.

The new controls should make it much more accessible to configure Audit Logging support for your Comet Server.

· 5 min read

We sat down for a chat with Natalie, Comet’s Marketing Manager, who has been with the company since July 2020. This piece has been lightly edited for length and clarity.

How did you first develop your love of tech?

I grew up in Silicon Valley, where having a passion for emerging technologies was instilled in me from a young age. I started my career at Apple and then worked for a few different companies, including a large MSP on California’s Central Coast.

I saved up and traveled the world for a year, then moved to New Zealand. I’ve lived in Christchurch for five years and absolutely love the culture here.

What attracted you to Comet?

What initially attracted me to working here was the team. Everyone gets to be themselves at Comet. I've worked in companies before where you show up and you're professional, but you don't necessarily get to bring your full self to work. At Comet, you get to show up and be your authentic self, which is much more fulfilling.

What do you love about the team and the culture?

We've had some really fun companywide homegrown initiatives. For instance, one of our developers, Ben Frengley, was really into growing spicy chili peppers. He gave seedlings to anyone who was interested. A number of us planted them in our gardens. We take pictures and share updates on them occasionally which has been fun.

Other team members have carpooled for ski trips or gone hiking together. We do company barbecues and potlucks from time to time. There’s a very natural cohesion in the way that the team comes together and rallies around things.

You’ve recently returned from parental leave. How was your transition back into the office?

When I was on maternity leave, I missed the team. The fact that we only hire really nice, good people makes the experience of coming to work so enjoyable. The team has been really supportive. There are a couple of us in the office who work part time: one of our team members is passionate about doing volunteer work, and I’ve transitioned back into work at a pace that makes sense for my family right now.

Tell me about Comet’s approach to work life balance.

We have great work life balance, better than at any other company I’ve worked for. That’s something a lot of workplaces say they offer, but at Comet we really do have that flexibility. For example, if I miss an hour in the morning because I need to take my daughter to an appointment, it’s easy for me to make up the time later in the evening after she goes to sleep so I don’t miss those precious family dinnertime moments.

Some people prefer to start work early in the morning, and finish earlier in the day to go surfing or pick up their kids. We also have the option to work from home two days a week. It’s great to have everyone’s lifestyles and schedules supported.

What are your favorite things about working at Comet?

I've bounced back and forth between large corporates and small companies. Ultimately I prefer the outsized impact my contribution makes at a rapidly growing company. You get to have autonomy and take ownership of your work in a meaningful way. There’s no red tape or bureaucracy, if you have a great idea, you get to run with it.

Because we’re constantly experimenting at Comet, there isn’t a culture of blame. A couple years ago, I recommended we go all in on a big podcast sponsorship. Halfway through I realized the campaign was failing and I decided to pull it. When I told the leadership team what had happened, the response was, “What did you learn from that experience? Okay, what’s next? Let’s keep moving.”

What keeps you passionate and inspired working in this field?

Although on the surface, the idea of working in backup software might not be as sexy as working for a gaming company or in an industry that has a lot of cache, at the end of the day, what we do really matters. We’re helping people protect their businesses and their livelihoods. We’re not selling a consumer product that will end up in a landfill. We’re providing an essential service, which makes it a very rewarding industry to contribute to.

What have you learned while being at Comet?

Before working at Comet, I specialized in brand and event-based marketing. When I started here, I needed to level-up as a generalist. I had this amazing opportunity to rapidly grow and learn about all these other areas of marketing I had never touched before.

When you’re on a large corporate marketing team, there are entire teams dedicated to each area – campaigns, advertising, sponsorship, events. At Comet, there’s a huge variety to what you get to work on day to day, which keeps me interested and motivated.

How do you feel about working at Comet?

Working at Comet is my dream job. I spent the first decade of my career trying to find a company to work at where I would be this happy. Frankly, my early career was a rough and bumpy road at times. It took a while to get here but I’m deeply grateful to have finally arrived at a place where I’m so professionally fulfilled.

What do you like about living in Christchurch?

Christchurch is the perfect size city. You have all the big city amenities without any of the big city downsides, like traffic. There’s arts, events, festivals, hot pools, great places to eat and drink with friends. The outdoors is also very accessible – it’s only a 20 minute drive to beautiful beaches and you can escape to the mountains within 1-2 hours.

There are such good people here. We’ve made great friends and built a strong community, which has allowed us to settle and make Christchurch our home.

· 4 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over September 2023.

There were five Comet software releases during September - four releases in the 23.9.x Voyager release series, plus one for our quarterly 23.8.x Adrastea release series.

Remote Registration

We've been hard at work developing a new way to register devices you would like to protect, right from the Comet Server admin web interface.

With the new remote registration feature you can remotely register a device and assign it to a user profile, right from the Comet Server admin web interface when the device has been silently installed using the /LOBBY flag.

  • Command Prompt: install.exe /S /LOBBY
  • Powershell: Start-Process .\install.exe -ArgumentList "/S", "/LOBBY"

Adding a device to a user is now as easy as clicking the register button. If you'd like to know more please checkout our silent install documentation.

Connected Devices Page Refresh

We've renamed the Connected Devices page to the Devices page and made a number of improvements to this area.

You can now see all devices that have been connected to your Comet Server, not just online devices. This extra information will allow for easier troubleshooting of what state each of the devices connected to your server are in.

We have also added bulk actions to the Devices page. These bulk actions allow you to manage the devices connected to your server much faster than before.

As a final touch we have updated how clicking a device status on the "My Devices" widget works. If you click on "Online," this will take you to the Devices page and apply a filter so that only online devices are shown.

Gradient MSP aggregate usage by Account Name

We are excited to share that we've enhanced our Gradient MSP integration to aggregate usage using the Account Name field on a user's profile.

To use this new enhancement you just need to enable grouping by Account Name when editing a new or existing Gradient MSP PSA Connection.

Diagnosing Unexpected Running Jobs

We've added extra detail to every job log to identify if the backup job was triggered by a schedule, a missed backup job, or a device start-up.

This will help diagnose what caused the device to run the backup out of schedule. To see more about it check out our troubleshooting guide.

Stuck Running Jobs

In rare circumstances it is possible for a backup or restore job to be stuck in a running state. For example, this can occur if a device becomes damaged when running a backup job and never starts up again to report to the Comet Server. These jobs stay visible on the Comet Server and impact how easy it is to monitor other jobs that are actively running.

As a first step to provide you with the tools to manage stuck running jobs, we have added the ability to manually mark a stuck running job as abandoned from the admin web interface.

An abandoned job is a job that Comet has automatically determined is no longer running after communication with the client was lost, or one that has been manually marked as abandoned by an admin. We have updated our documentation to add clarity to what each of the job statuses mean.

Marking a job as abandoned has been added to the "cancel a job" workflow. To remove a stuck running job, simply attempt to cancel the job and the Comet Server will help you with the rest.

A job marked as abandoned will revive itself and show as running if the Comet Server ever receives an update about that job again.

· 7 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over August 2023.

There were six Comet software releases during August - five releases in the 23.6.x Voyager release series, plus one release for the launch of our new quarterly 23.8.x Adrastea release series.

New design for the Comet Backup desktop app

We're very pleased to announce a visual refresh for the Comet Backup desktop app:

This work followed on from the new design for the Comet Server web interface that was released earlier this year for the previous 23.5 quarterly series. This is the first major layout change to the desktop app in Comet's history; the current desktop app has had the same layout for the past six years.

Our goal for the new interface design was to make the product simpler for new users, while still keeping it familiar for existing users. The tabs, icons, buttons, fonts and colors have all been refreshed with a modern rounded style, but you are still greeted with your familiar Protected Items and charts on the home screen.

The most fundamental change was made to navigation within the app: the previous left-side navigation bar has been removed, meaning your Protected Items are always clearly visible, and we have refreshed the breadcrumb bar appearance to help orient you to this landmark interface element. The removed left-side navigation bar has been replaced with a top navigation bar which puts more emphasis on your branded company logo, and offers clearer, more distinctive focus on the calls-to-action for the key backup and restore functionality.

In the top-right corner, you will see a a dropdown overflow menu, using modern and intuitive UX iconography. Inside this menu, you can get quick access to detailed job history; creating recovery media for restoring Disk Image backups; and a new Settings dialog. The new Settings dialog contains Storage Vault management, account and login settings, email reporting settings, your devices, and the ability to import settings from other supported backup products.

If you had configured a custom Help webpage for embedded use, it will now appear as a button on the main screen.

VMware beta program

We've been hard at work developing the next Protected Item type for Comet, to add VMware support.

This has been a highly upvoted feature on our Feature Request page for some time. We've spent extra time and effort on making this Protected Item type as polished and performant as possible.

The details are subject to change before release, but we expect to be able to support major versions of VMware ESXi (6 / 7 / 8) and vCenter, using either free or paid licenses. Your backup jobs can be accelerated using changed block tracking (CBT) to produce synthetic full disk images that are deduplicated inside your Storage Vault. The new Protected Item type will work seamlessly with Comet's scheduling, deduplication, compression, encryption, job reporting, tenants, and granular restore of single files from supported virtual disk filesystems.

We're in the final stages of the beta program and are currently accepting new partners to help us ensure that this new Protected Item type is a good fit for your production VMware infrastructure. If you are interested in getting early access to this feature, please follow this link to register your interest - we would greatly appreciate any feedback you might be able to give us before the official launch later this year.

Price change notice for Backblaze B2

Comet has supported Backblaze B2 as a storage platform for over six years, since our 17.6.4 release back in July 2017. Over the years Backblaze B2 has proven to be a reliable, trustworthy, performant, and cost-effective solution. Together with Wasabi, these are the two most popular cloud storage providers amongst Comet users.

This month, Backblaze B2 have announced a price change. The base storage cost is increasing from $5 USD / TB to $6 USD / TB, but egress bandwidth costs are being reduced. For full details, please see their official announcement.

WebDAV

WebDAV is a storage protocol like FTP, SFTP, or the S3-compatible protocol, that can be used to store files in a remote location. It's based on HTTP technology and supports password based authentication, as well as transport layer security over HTTPS. The protocol has been around since 1996 and was standardized by the IETF in RFC 4918.

Accessing a remote WebDAV server is a built-in feature of Windows Explorer, as well as macOS Finder and the KDE and GNOME file managers.

Because the capability for accessing remote storage is built into the operating system, WebDAV is simple to use with a very low barrier to entry, helping it maintain a broad user base amongst enterprises, universities, and commercial service providers including Hetzner Storage Box, DreamHost, Yandex Disk, pCloud, and many others.

You can easily host your own WebDAV storage server as the protocol is built into NextCloud, OwnCloud, and the Apache and Microsoft IIS web servers. In particular, users of Synology NAS devices can install the WebDAV Server app from the Synology Package Center for a more reliable alternative than configuring SMB credentials.

WebDAV is available as a storage type for Storage Vaults and for Comet Server Storage Role in 23.6.9 and later.

Quick feedback

The next time you visit the account.cometbackup.com dashboard, you might notice a new "Feedback" tab on the right-hand side of the screen:

Clicking the "Feedback" text will open a short survey asking for any short thoughts you have about your impressions of Comet and how easy our product is to use. Our Customer Success team would really appreciate any answer you give. After submitting feedback, the tab will disappear, but you can submit more feedback at any time by clicking the "Give us Feedback" link in the page footer area.

If you have long feedback or any questions, we would appreciate this via the existing communication channels, such as a support ticket or an email.

23.8.0 Adrastea

Earlier this week, we put the finishing touches on our latest quarterly release, Comet 23.8.0 Adrastea. This is the the latest entry in our quarterly rollup series, that branches off from our main rolling Voyager development into a fixed target for you to qualify and build your service offering upon.

As with all our recent quarterly release series, Adrastea is named after a moon of Jupiter, which in turn takes its name from an ancient Greek mythological figure. It is the second-closest moon to Jupiter and the smallest of the four inner moons, orbiting at the edge of Jupiter's main ring. It is thought to be the main contributor of material to the rings of Jupiter.

For users coming from the previous 23.5 Thebe quarterly release series, Adrastea adds 7 features and 24 enhancements, including the new Comet Backup desktop app design and WebDAV support mentioned above; single sign-on support with OpenID Connect (OIDC); Protected Items that can stay linked with the user's Policy; additional admin permission options; and many performance improvements.

The 23.8.0 series does remove support for some old versions of macOS. If you have users with old Mac machines that are not able to upgrade the OS, the previous 23.5.x Comet Backup client will remain capable and working when connected to a 23.8.x Comet Server.

The full set of changes can be found in the release notes.

Webinar announcement

If you'd prefer to watch rather than read, we're hosting a webinar next week to discuss this new quarterly release and all the new changes. Please register for a notification before we go live on September 5th (5pm EDT / 2pm PDT) to catch up on all the latest Comet news with me - and as usual, there will be time for a live question-and-answer session at the end of the presentation.

As well as that, we have many more videos available on our YouTube channel, including guides on getting started with Comet, individual features, demonstrations with our technology partners, and webinars for previous quarterly software releases.

· 7 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over July 2023.

There were five Comet software releases during July - one in our quarterly 23.5.x Thebe release series, plus four releases in the 23.6.x Voyager release series.

Single sign-on with Microsoft, Google, and OIDC

Comet Server is adding support for administrators to single sign-on (SSO) to the Comet Server web interface, using a supported OpenID Connect (OIDC) identity provider:

OIDC is a framework for authentication and authorization, based on the OAuth 2.0 standard. It's widely used by many providers for "Log in with..." buttons. This new feature extends our existing single sign-on support using the LDAP protocol.

The additional identity providers (IdPs) now supported are:

  • Microsoft Entra ID (formerly Azure AD)
  • Google (Google Cloud, Google Workspace, or personal)
  • Any other OIDC-compatible provider that uses a discovery document (usually at the .well-known/openid-configuration URL path).

You can configure a new OIDC provider from the Comet Server web interface > Settings screen > "Admin Accounts" tab > "External Authentication Sources" button:

To use this feature, you should first visit your IdP's settings page, register a new application credential within the IdP, and copy the credentials to this settings page. You will then need to copy Comet's generated "Redirect URI" field back into your IdP's settings page.

When the administrator user uses the new "Log in with..." button and performs a successful login operation via the IdP, a new Comet Server administrator account will be dynamically created for them on-demand. As with LDAP, you can specify which Comet Server permissions are granted to the newly generated account. This new account is marked as "Externally managed" within the "Admin Accounts" table, ensuring that valid IdP login is required to access this administrator account.

If your IdP enforces two-factor authentication (2FA), you can configure Comet Server to skip enforcing its own internal 2FA on the account, so that the user is not bothered twice.

You can request custom scopes, and enforce claim values against either custom scopes or standard OIDC scopes. This allows you to enforce that the only members of certain Microsoft, Google, or OIDC groups within your IdP are allowed to log in to the Comet Server.

This feature is available both for the top-level Comet Server administrator as well as individually for each tenant.

Price change notice for Comet Storage powered by Wasabi

Our Comet Storage service gives you the option to purchase Wasabi Cloud Storage directly from Comet, offering all-in-one billing and providing a more integrated experience. This month, we've passed along the latest price changes from Wasabi, to their new price of $6.99 / TB.

For more information, please see Wasabi's official announcement.

Improved job start performance

When backing up a Files and Folders-type Protected Item, one of the first steps is for Comet to enumerate all the selected files, in order to calculate their total size. The total size is used to enforce the "All Protected Items Quota" feature, as well as to properly determine the progress bar's expected upper bound. If you are running a headless device with no GUI to render the progress bar, and you are not using the "All Protected Items Quota" feature, then there's no remaining purpose for this scan phase, and so Comet will skip it to save time.

We heard mixed feedback about this - a discussion in our feature voting system uncovered some use-cases where the progress bar would still be desirable even on headless devices with no GUI. But also, there was competing feedback that spending time on file size measurement is still slow and undesirable even in some cases where the GUI was present.

In the latest version of Comet, we've come up with a new and better approach to this issue. If the "All Protected Items Quota" feature is used, then we require an accurate measurement up-front regardless. But if this feature is not used, then we can rapidly create an approximate progress bar size based on the previous backup job's size plus some small estimated buffer amount. This should provide a great speed improvement for GUI users, a reasonable progress bar for headless users, and at the same time, provide an accurate measurement for quota users. The reported size measurement will always be completely accurate after the backup job finishes.

Improved low-memory modes

For users using Comet on devices with low RAM, our software has long since offered the "Prefer temporary files instead of RAM (slower)" option for backup jobs, to toggle whether Comet stores the deduplication index either in-memory or on-disk in a temporary database file. Enabling this option can significantly reduce Comet's memory usage, allowing the backup job to complete on low-memory devices, at the expense of a longer backup job duration.

The latest version of Comet extends this option to also use a small in-memory bloom filter. This allows Comet to perform some of the deduplication operations in-memory with minimal overhead. This new combination technique can significantly improve the performance of this option for low-memory devices.

The deduplication index is needed for almost all operations involving the Storage Vault, not just backup operations. This month, we've also added an option to use temporary files instead of RAM during a restore, extending the possible use cases for Comet on low-memory devices.

Performance improvements for new servers

The performance improvements this month are not limited to the Comet app itself. We've also significantly improved the account.cometbackup.com system: downloading the large Self-Hosted Comet Server installer is now implemented via an Amazon CloudFront cache, improving download speeds between 2-6x in our testing.

We have also been able to significantly improve the speed of creating new Comet-Hosted Comet Server instances. The creation time has been reduced from 60-90 seconds down to 10-15 seconds, owing primarily to some changes in the default generated DNS names.

Configuration change notice for PKCS11 codesigning

Comet supports Authenticode codesigning for Windows using either an on-disk file (PKCS #12), or a hardware security module such as a USB device (PKCS #11), or a cloud HSM on Azure Key Vault. With the file-based approach no longer being supported for new Authenticode certificates, we are seeing increased use of the alternative PKCS #11 and Azure Key Vault options, as partner Authenticode certificates come up for renewal.

If you are using a physical USB device for Authenticode codesigning, we have updated the available settings options to improve compatibility with a wider range of devices. The new settings screen should be clearer and easier to use, but you may be required to update your configured settings, as depicted:

If your Comet Server is running in a cloud VM, it's not feasible to plug in a USB hardware device for codesigning. We would recommend Azure Key Vault as an excellent cloud-based solution to this issue, but we've also recently tested the compatibility of the third-party Virtualhere software for remotely forwarding a physical USB device to another PC, and we can confirm this solution works for PKCS#11 codesigning when running Comet Server on a cloud VM.

When using the Comet Server web interface, the quick search bar (using the Alt + Q keyboard shortcut) could previously search through usernames, Account Name field values, Protected Item and Storage Vault names, settings pages, and more. In the latest version of Comet, we have extended the search capabilities to also find users by their email address.

You can also now enter the ID of a Protected Item, Storage Vault, or even a backup job, and the quick search bar will try to match it with the corresponding user or job. This is particularly helpful for troubleshooting some situations.

That's all for this month - the blog will return next month with more news about all the latest changes to Comet.

· 7 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over June 2023.

There were six Comet software releases during June - two in our quarterly 23.5.x Thebe release series, plus four releases in the 23.6.x Voyager release series.

Policy-linked Protected Items

Comet has a comprehensive Policy system that allows you to apply rules to entire sets of customers at a time, such as restricting their ability to open the desktop app or restricting what features and settings can be used.

One of the existing Policy options allowed you to create a Protected Item that would be applied by default to all new devices that register in the account. However, it was limited to when the device was registered for the first time, it only defined the default settings, and after that the Protected Item could drift from what was configured in the policy. Having a default value that can then change is an important use case, but over time, we heard feedback that people would like these default Protected Items to remain tied to the policy version. In Comet 23.6.0, we made that possible.

You can choose whether the Policy Protected Item applies only for new devices, or if it remains linked to the policy after creation. This allows you to configure a Protected Item for a specific application, file-path, or integration target; apply it by default to all users of the Policy; and still be able to change those settings centrally for all users of that policy.

This was a highly popular request on our Feature Voting page. Thank you to all the partners who shared their support for this feature. If you haven't seen this system before, the Feature Voting system allows you to upvote existing requests, raise new requests, discuss features with other Comet partners, and get notified when a change happens in the product. We look at this system often to help guide the priority of new development.

Extended admin permission options

As an administrator, when configuring permissions for other administrator accounts, additional options are now available.

These new options allow you restrict the capabilities of other administrators. This is intended for the use case of tenant administrators, or limited-permission administrators of a shared Comet Server. The use cases are varied but are often from the perspective of restricting the visibility of the Comet branding for white-label purposes.

  • You can hide the Server History and Server Info widgets from the homepage, including Comet's version numbers and update information. This simplifies the main screen for the limited-permission administrators who would be unable to act upon this information;
  • You can enforce that the target administrator is unable to create new Storage Vaults via Storage Templates or via custom storage; and
  • You can filter and restrict which cloud storage providers are available for these limited-permission administrators to use.

This work was also inspired from our Feature Voting system. Thanks to everyone for your patience as we combined several separate requests to refine down the essential requirements for this use case.

These features are also available in the Comet Server API and in our latest SDK releases for PHP, Ruby, Javascript / Typescript, Go, and C# / .NET.

New minimum system requirements for macOS

From Comet Backup 23.6.3 onwards, your customers must have macOS 10.13 High Sierra (2017) or later to continue running new versions of Comet Backup.

If your customers are still using macOS 10.11 El Capitan (2015) or 10.12 Sierra (2016), the last releases that can be run on these older versions of macOS are the Comet 23.5.x Thebe series, or 23.6.2 Voyager. These versions of macOS are no longer receiving security updates and we would recommend that all end-users upgrade if possible.

There is no change to Comet Server's minimum OS requirements as we do not offer Comet Server on macOS. It is safe to use the bulk deployment system in Comet Server to continue deploying software updates to all macOS customers - the affected users will skip the install and remain on their currently installed version of Comet Backup.

We last upgraded the minimum macOS version back in September 2022. We expect to be able to keep the 10.13 baseline for a longer period of time.

"Run when PC starts" now includes Sleep

Comet has long supported a "Run when PC starts" option in the job schedule settings. This option is highly useful for laptops that are often offline or sleeping, where a regularly scheduled backup job is unlikely to occur at the odd moments when the device is online. By running a backup job immediately when the PC boots, the device is more likely to complete a successful backup job.

However, recent versions of Windows have expanded how widely "Fast Startup" is applied across different PCs, to the point that a Windows laptop will often not restart, but only simulate a restart via hibernation-related techniques. This has a negative effect on the "Run when PC starts" option as it was only triggered via a full restart, which is not the default behavior in current versions of Windows.

As a result, we have extended the "Run when PC starts" option to count waking up from sleep as "starting the PC". This is more in keeping with the behavior of current-generation laptop computers and it should make the option work as-expected in more cases. Compared to the old behavior, it is likely that additional backup jobs could be run unexpectedly, but our expectation is that this is not a bad thing, and the result will be more reliable overall.

Comet Server web interface enhancements

The 23.5 Thebe release last month included a major redesign of the Comet Server web interface. We've continued to build upon this throughout June in the 23.6.x Voyager series with many enhancements for server operators.

One area of focus was on ease-of-use. When configuring a Protected Item for Application Aware Writer, Hyper-V, or Microsoft Exchange, you can now use the top-right button to remotely browse the customer's PC to select items for backup. Compared to finding individual virtual machine IDs, this is a significant improvement to the ease-of-use of this feature.

Additionally, when saving changes in the Settings page, the page will now intelligently wait for settings to be applied, instead of leaving you at a web browser refresh screen. This makes for a much more intuitive and user-friendly experience. The Comet Server web interface will now also warn you more clearly about invalid bucket names for cloud storage.

There was also a particular focus on performance enhancements for the Comet Server web interface. Loading the web interface should be snappier and with fewer loading spinners, as the necessary information is able to be loaded in parallel, as well as reused from previous lookups. The Quick Search area is now faster and has a new design style. When remotely controlling a connected device to start a restore job, the restore job will reuse information known by the web interface instead of recalculating it, resulting in a restore job that starts faster and finishes faster.

A third area of focus throughout the month was on fixing known issues that have been reported. Thank you to all partners who reported issues - the latest 23.5.x and 23.6.x updates should have addressed all the web interface issues raised to this point.

CometCon 2023

Following on from last year's successful event, we hosted another week-long meetup with Comet team members from all over the country. With a strong focus on technical talks, networking, and a special coffee-tasting event, everyone had a great week! I'd like to extend a special thank you to our guest speakers!

That's all for this month - the blog will return next month with more news about all the latest changes to Comet.

· 7 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over May 2023.

There were four Comet software releases during May, all in the weekly 23.3.x Voyager release series. The work this month included a mix of core application development as well as projects in the surrounding ecosystem:

Learn about Chunking

Earlier in May, Mason gave a presentation of the history and overview of backup technologies, starting with simple file copies, through chain-based approaches, and culminating in the Content-Defined Chunking technology used by Comet.

Comet Server in Docker

The Self-Hosted Comet Server is now available as a Docker container:

Docker is a popular system for running applications in "containers". In the same way that freight shipping containers have a consistent size and shape, in order to fit within a larger shipping ecosystem, Docker containers also have some consistent behaviors in order to fit within a larger application runtime ecosystem: a "containerized" application has a standard way to start, stop, and log messages; how their storage and configuration is managed, how ingress and TLS termination works, and how sandboxing and permission restrictions are applied.

By offering Comet Server as a Docker (OCI) container, it should be easy for existing Docker users to get started with the Self-Hosted app and to manage it going forward. It also enables new functionality such as running multiple self-hosted Comet Servers on the same PC or VM. This does not replace the existing Self-Hosted installers, which will continue to be available.

There has been a long-standing open feature request for an official Docker container. Thank you to everyone who voted and commented on this feature, and a special thanks to "Hobadee" for providing an unofficial solution to the community so far.

C# .NET SDK and expanded API documentation

When you visit the the Comet Server web interface, your web browser loads and runs a "Single Page App" (SPA) locally inside your browser. This webapp speaks to the Comet Server backend solely using our public API. This API broadly covers every action you take within the Comet Server web interface, which means if you can do an action in the web interface, then it can be automated by a developer.

The Comet Server API is comprehensively documented, and during May we added many more comments and explainer notes to the constants, endpoints, and type definitions. Developers using the existing PHP SDK, Javascript / Typescript SDK, Ruby SDK, and Go (Golang) SDK will see these new comments appear in their IDEs during autocomplete.

During May, we put the finishing touches on the latest addition to this group - a new public .NET SDK. It's available as CometBackup.CometAPI.SDK on NuGet and is developed in C# for use with any compliant .NET Standard 2.0 runtime, including .NET Framework 4.6, .NET Core 2.0, .NET 5, or any later versions.

Getting started with the SDK should be straightforward:

using (var client = new CometAPI("http://127.0.0.1:8060", "admin-user", "admin-password")) {
var users = client.AdminListUsers();
foreach (var user in users) {
Console.WriteLine(user);
}
}

Every API method is also available as an Async() version to allow for concurrency.

Our SDK version numbers generally adhere to Semantic Versioning and any enthusiastic readers may have noticed this SDK uses a "version zero" version number at present. We don't necessarily expect to make breaking changes, but we are actively requesting feedback about this new SDK from existing C# users to ensure we've created something idiomatic. We'd love to hear any feedback about the SDK design or any bug reports before we commit to v1 compatibility, so if you are a C# developer then please reach out by ticket or on GitHub.

Audit logging

To help our partners meet their compliance obligations, we've added advanced audit logging capabilities into Comet Server. Almost every action - including login events for administrators and users, restoring data, changes to user and server settings, and more - can now be logged server-side into a secure file.

This work was based on expanding Comet Server's live event streaming features to cover a much more comprehensive set of data. If you are making use of the existing Webhook feature or the Websocket API feature, when upgrading to Comet Server 23.3.7 or later, you may start receiving a larger amount of data. You can control this by declaring a restriction on the streamable event types you want to receive.

In current versions of Comet, this feature must be configured by setting the AuditFileOptions property inside the cometd.cfg file. We expect to make it available via the Comet Server web interface soon!

Quality, performance, and memory enhancements

As we approached the quarterly release, we took a special focus on quality improvements to give us a solid foundation.

The fresh new design for the Comet Server web interface had its debut in 23.3.3, and since then throughout the 23.3.x Voyager release track, we have spent additional time and effort to ensure quality. In the latest versions of Comet Server you will see fewer cosmetic issues as this work has stabilised nicely.

We've also made significant performance improvements to key areas of the client application. Performing granular restore of single files from inside a Disk Image or Hyper-V backup may now be 3-8x faster while using 40% less memory. Comet also now uses less memory for loading files from S3-compatible Storage destinations like Wasabi, and when loading very large files from a Storage Vault.

The Office 365 Protected Item type in Comet has been a continued development focus this quarter, including a partial rewrite. Comet is now better able to handle incremental changes to mailboxes; the reported error messages are more detailed; and Office 365 backup jobs taken with the latest version of Comet should be more resilient against network errors and rate-limiting from the Microsoft Graph API. We would encourage all users to raise a support ticket if you experience any issues with Office 365 backups as we continue to improve the sync capabilities.

Comet 23.5 "Thebe"

On the 1st of June, we put the finishing touches on our latest quarterly release, Comet 23.5.0 "Thebe".

Thebe is the latest entry in our quarterly rollup series. It branches off from our main rolling Voyager development into a fixed target for you to qualify and build your service offering upon.

Like Comet's previous recent quarterly software releases, "Thebe" is named after a moon of Jupiter, which in turn takes its name from an ancient Greek mythological figure. It is a very small moon with only 0.004x Earth's gravity, meaning it is less likely to shape itself into a sphere - in fact a large impact crater covers around 40% of its surface area:

It was discovered by the Voyager 1 and 2 spacecraft in 1979, but owing to its small size and position, almost nothing more could be discovered until the next spacecraft Galileo visited two decades later. Scientists believe it contains frozen water.

As always for a new quarterly release, there are two changelogs for 23.5.0 "Thebe" depending on whether you are coming from the previous quarterly release or the previous Voyager release. You can see the full details in the release notes.

That's all for this month! Thanks for reading - there are some more great features currently under development that we're excited to be able to share with you soon. As always, please follow @CometBackup on Twitter and you can always contact us if you have any questions.

· 5 min read

Where are you originally from?

I'm from Stockholm, Sweden and I just celebrated 5 years in New Zealand! Times flies when you are having fun! Love, family and new adventures brought me to this lovely country.

What is the one thing about Sweden that you’d like non-Swedes to know about?

We have a useful word that I don’t think many other countries have – “lagom”. It means not too much, not too little, but just the right amount and it’s a very handy word to have in your vocabulary (I think).

Also, that there are no polar bears in Sweden. It’s funny how many times I get asked that question!

How long have you been working at Comet Backup?

This is my seventh week at Comet, but it feels longer than that (in a good way)!

Before Comet, after completing a master’s degree in IT engineering and a bachelor’s in business studies, I worked as a BI Consultant in Stockholm for 8 years. When I moved here, I started working as a Senior Product Owner and I did that for almost 5 years before joining Comet.

What attracted you to Comet?

The industry was completely new to me, and I wanted to try working in a younger business that was growing fast. Having the chance to be the first dedicated product person in the company was an exciting opportunity too!

How would you describe your role as Product Manager at Comet?

In short, my role is to work closely with all Comet teams to ensure we deliver a high-quality product with a great user experience, that meets the business goals and our customers’ needs!

But to expand a bit on that, I need to keep up with industry trends, understand the market needs, know the competitor landscape, and understand what our customer needs and their pain points.

Combining this information with the business strategy, product metrics, data analytics, and all the input from Comet’s teams, I can create a product roadmap that outlines how the product will be developed and what the teams will be focused on for the next while.

Basically, as a Product Manager, you are responsible for guiding the direction of the product and its development, making sure we’re working on the right things to ensure the continued success of our product and keep growing our market share.

What was your first day at Comet like?

It was great! Everyone was so friendly and welcoming, and I’ve always enjoyed working with smart, talented, and down-to-earth people, so that has been one of the highlights here at Comet so far.

What aspects of your role challenge and excite you?

It’s wonderful how much trust, support, and freedom Comet gives me – they trust me to do the job as I see fit. I just hope I can live up to their expectations and do my part to help continue making Comet the success story it already is!

Product Managers have to juggle a lot of activities and deadlines. What best practices would you recommend for organising one’s workload?

I think a simple to-do list does the trick, but you need to make sure to re-prioritize the items on the list regularly, based on their urgency and how important they are. When I get stuck, I refer back to the product vision or strategy to figure out what should be done first (or just take a break to clear my head).

You love being out and about. Would you recommend any running or biking trails in the Canterbury area?

I think it’s really nice running or biking up the Rapaki track and then going down Victoria Park and Bowenvale Valley – it’s such a peaceful area and the views up there are great too!

What’s the most memorable or most interesting thing that’s happened to you on a trip?

In 2019 I spent three months biking around South America - the whole trip was pretty memorable, but riding through coca plantations and getting stopped by a group of suspicious-looking characters to have a beer is probably up there.

Wait, what??

Yeah it was pretty scary - we were biking around South America and this truck comes with these five guys, and you can tell they’re working at the coca plantation. They were all drinking beer and seemed to be drunk, and they stopped where we were. They were speaking Spanish and we could only understand a couple of words. Then they offered us a drink and we couldn’t say no!

There is an ongoing debate at the Comet office on whether or not pineapple should be a pizza topping. Would you care to share your thoughts on this?

Ha! No, I don’t think pineapple should be a pizza topping - but if I can stick with my pepperoni pizzas, I don´t mind if others have pineapple on their pizzas.

· 7 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over April 2023.

There were five Comet software releases during April - four in the weekly 23.3.x Voyager release series, plus one minor patch update 23.2.2 for our quarterly "Leda" release track. We've also released a new YouTube tutorial for the new Object Lock feature!

There were some very large and exciting features released in Voyager during April:

New design for the Comet Server web interface

When upgrading to Comet Server 23.3.3, you'll be greeted with a new experience:

This is the first major Comet Server web interface upgrade in six years. We're very excited and proud of the new layout. The left-aligned navigation bar allows for faster navigation to pages without clicking through menus, and the quick search bar has been modernized. The new design has also expanded the set of colour customization options that are available: in addition to setting your custom brand colour, you can also set an accent colour for highlights.

The homepage has seen the most dramatic change, including new navigation buttons on the top-right and a rework of all the admin widgets. There are new widgets showing how many of each Protected Item type is being used; how much used/free space there is on your Storage Role data location; the status and last run time of your Server Self-Backup; a live real-time chart of replication progress; and more.

The policies page has also been redesigned. As we add more and more policy options in new versions of Comet, we split the long Policy section to use sub-tabs. This includes a summary page, and a new feature to suggest possible common file path exclusions. We're continuing to work on additional Policy features, and you can expect to see a highly-voted feature coming soon!

When looking at a user account, on the Protected Items tab, the new user interface design has also added a quick-access "Run Backup" button that can remotely command the device to start a backup job. Previously, this feature was available from the Connected Devices page or from the Devices tab - but adding it to the Protected Items tab is a significantly more convenient place, and demonstrates this functionality more clearly to new Comet administrators.

We would appreciate hearing your feedback on the new web interface design before it lands in the upcoming quarterly release!

Search restore from web

When restoring data, Comet prompts you for the Storage Vault to restore from; the backup snapshot to browse inside; and then the file (or all files), respectively. However if you're trying to restore a single file without knowing exactly when it was last available, or what folder it was inside, Comet's Search button can search through all backup job snapshots to find the right match.

The Search button has been available on the Restore dialog in the desktop app for a while. New in Comet 23.3.4 is the ability to remotely perform a file search for restore from the Comet Server web interface.

Test Connection for Storage Templates

Comet is highly flexible in the number of ways you can configure your storage. From the customer's device running Comet Backup, a Storage Vault could point to a local path; directly at a cloud storage provider; or to your Comet Server with Storage Role enabled - which could then receive the data and store it on a local RAID array or forward it to another cloud storage provider.

Storage Templates are the provisioning system for new Storage Vaults. If you set up a Storage Template for Wasabi or Backblaze, you gain the ability to provision private, per-customer cloud buckets and access credentials with a single click. If you enable Storage Role for receiving data into your Comet Server (or another clustered Comet Server), using a Storage Template can help to very easily provision new Storage Role buckets for each customer.

Comet has long supported a Test Connection button on the Storage Vault page, to check that your custom entered credentials are valid. But when setting up a Storage Template for the first time, the only way to verify that everything was functioning was to attempt to provision a new Storage Vault for a test customer.

In Comet 23.3.5, a new Test Connection button was added to the Storage Template configuration popup in the Comet Server web interface. This allows you to quickly verify that your template is working as expected.

Self-Backup

Comet Backup requires a connection to a Comet Server to safely store its configuration. But if you are self-hosting the Comet Server application, the Comet Server also should be backed up to mitigate against the risk of data loss. However, you can't really use Comet Backup for this purpose, since this creates a circular dependency during recovery.

As a solution, Comet Server includes the Server Self-Backup feature. This creates a consistent snapshot of Comet's configuration files, and allows you to store it encrypted on any supported storage location, including cloud storage. Multiple targets, custom scheduling, and data retention policies are all supported. The files are simple zip files to ensure that any eventual necessary restore is an easy and low-stress process.

The latest version of Comet Server made improvements to the Server Self-Backup feature. The generated filenames now clearly show the date and time of the backup job, instead of solely an epoch timestamp. Any automatic SSL certificate files provisioned by Let's Encrypt are now included in the archive, ensuring that it is not required to reissue the certificate. This helps avoid any issues with rate limits on the Let's Encrypt service, which could otherwise prolong your service outage.

We've also added a new option to include server log files in the Self-Backup archive. These log files are not generally required, but for completeness or for an investigation, they can provide an additional view into the circumstances behind the event.

Codesigned uninstallers

Microsoft, along with third-party security vendors, continue to harden the security posture of the Windows operating system. Comet Backup's client installer is codesigned - either by our company, or if you are using custom branding, then possibly with your own custom codesigning certificate. However over time, the security hardening has increased, and we've recently heard reports that the uninstaller for Comet Backup could trigger alerts in some security products. As a result, the latest versions of Comet Server apply Authenticode codesigning to the uninstaller to help avoid this issue.

The 23.5 Quarterly release is coming soon

At Comet, we release our software under two tracks - the "Voyager" release track approximately weekly, with all of our very latest changes; and the quarterly release track, where we bundle up three months' worth of development into a new fixed point for you to qualify, offer, and build upon, in order to provide a consistent experience for your own customers. Depending on your market position or your requirements, you may find either one of these tracks better suits your needs. As per our regular release schedule, you can expect a 23.5.0 quarterly release towards the end of this month, which will bring all of the exciting features to the quarterly track and also for Comet-Hosted users.

That's all for this month! Thanks for reading - there are some more great features currently under development that we're excited to be able to share with you soon. As always, please follow @CometBackup on Twitter and you can always contact us if you have any questions.

· 7 min read

"What's New?" is a series of blog posts covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over March 2023.

There were just three Comet software releases during March - two in the 23.3.x Voyager release series, plus one minor patch update 23.2.1 for our quarterly "Leda" release track.

We've landed a few large and exciting features this March:

S3 Object Lock

Comet 23.3.1 adds support for Object Lock on S3. This feature allows Comet to "lock" an object inside a S3-compatible bucket, preventing it from being deleted or modified for a fixed period of time.

This is a fantastic new capability for Comet and it is a key defense against ransomware. Comet generally requires the capability to add and delete files within your Storage location; deleting files is necessary for applying retention passes, updating index files, and coordinating locking across multiple devices. However, if malware is running on your PC and manages to intercept Comet's storage credentials, the malware would also be able to delete files, causing much wider havoc.

Comet uses S3 "Compliance Mode" to lock individual objects within the storage location. This ensures that there is no way for the object to be deleted for the specified time, not using Comet's storage credentials, nor even if your administrator S3 keys are leaked or exposed.

For a visual overview of the process, please see our usage guide and also the simplified explanation.

This feature is available for Amazon S3, Wasabi, IDrive (excluding Storage Template provisioning), and other S3-compatible providers including Minio-based providers. Please check with your S3-compatible provider's documentation to see if Object Lock is available.

Object Lock is an opt-in feature, both in Comet and with cloud storage providers. It also relies on S3 bucket versioning. These properties generally must be set when the S3 bucket is created for the first time. It is not generally possible to enable Object Lock on an existing S3 bucket. To use Object Lock with an existing S3-based Storage Vault, you would have to create a new S3 bucket with Object Lock enabled; migrate the data; and update Comet's Storage Vault settings to point to the updated bucket.

Comparison to Backblaze B2

Regular users of Comet may be aware of the existing "Hide files rather than deleting them" option for Backblaze B2. Backblaze B2 supports both a native API and also an S3-compatible layer over the native API. Comet Backup integrates with the native API, so the new S3 Object Lock feature is not available for use with Backblaze B2. However, the existing "Hide files instead of deleting them" option can be used to provide the same protection against ransomware.

Codesigning with Azure Key Vault

If you are customizing the branding of the Comet Backup desktop app, then we would recommend setting up codesigning certificates. Having a codesigning certificate means that installing Comet Backup proceeds more smoothly through Smartscreen and Antivirus popup warnings on Windows, and through Gatekeeper on macOS.

The Windows codesigning programme, "Authenticode", is currently in a period of disruption as new rules are being put in place. Owing to the high number of events where developer codesigning certificate files were leaked or lost, new requirements are being enforced from June 1st 2023 that newly issued codesigning certificates must no longer be stored as plain files on disk, but instead must be stored in a Hardware Security Module ("HSM") or equivalent isolated device. Comet has long supported Authenticode certificates using either certificate files ("PKCS #12"), or via plug-in HSM devices that are compatible with the "PKCS #11" standard.

There are two tiers of Authenticode available. The Extended Validation ("EV") service performs a deeper level of business-level and legal checks of the target organization before issuing the certificate. The extra vetting comes with a higher purchase cost, but it also results in a higher level of initial reputation for the resulting codesigned .exe file. An EV certificate was always required to be stored on an HSM.

However, it's common to install Comet Server on a cloud VM or VPS, where plugging in a USB dongle or smartcard hardware device is not physically possible. This difficulty also discouraged many MSPs from using the higher-quality Extended Validation service. With the impending phaseout of the file-based method for newly issued certificates, neither existing option is suitable, so another option had to be found.

Comet 23.3.0 adds support for codesigning using Azure Key Vault. This is a cloud service from Microsoft to manage the secure provisioning of security keys and certificates, including for Authenticode codesigning. There are various services and pricing tiers available; in particular, it's possible to purchase a managed cloud HSM, which meets the new June 1st 2023 Authenticode requirements.

At the time of writing, we would recommend GlobalSign or TrustZone for issuing new Authenticode certificates. There is no carry-over reputation with Authenticode, so replacement certificates can be issued from any provider. These particular providers were prepared early for the new requirements and have a secure vetting process to prove your use of an HSM, such as an Azure Key Vault managed HSM, before issuing your certificate. The private key never leaves the managed cloud HSM device, and Comet Server only uses an Azure application ID to remotely perform the signing steps.

Comet Server can perform Authenticode codesigning for Windows, regardless of whether Comet Server is installed on a Windows or Linux host OS. This is achieved by using a cross-platform signing toolchain. To support the new Azure Key Vault feature, we replaced our existing bundled codesigning toolchain from osslsigncode with a new jsign version. Comet ships these third-party utilities as a courtesy in compliance with their redistribution license.

For most existing users of codesigning with a PKCS#12 file-based certificate on disk, there will be no noticeable difference and Comet will continue to work without any configuration changes. However, some users may experience breaking changes:

  • The new jsign program takes different parameters for hardware devices using the PKCS#11 standard, which could not be automatically converted. Users of hardware devices may need to revisit their settings.
  • If Comet Server is installed on ARM64 Linux, the version of jsign distributed by Comet is not compatible with the musl C runtime generally used for static binary distribution. A glibc-based Linux distribution is now required to run the codesigning toolchain on ARM64 Linux. The issue does not apply to x86_64 Linux. We may be able to resolve this issue in a future version of Comet.

For more information, see the full Authenticode codesigning documentation.

New web interface features

Looking beyond these headline features, there have been many more improvements to Comet this month, particularly in the Comet Server web interface.

It's now possible to select custom snapshots for deletion from the web restore dialog. This builds upon last month's feature to add this in the Comet Backup desktop app. To use this feature, enable "Advanced Options" from the top-right user menu, and then click the new Actions button in the Restore wizard dialog.

You can now see an online device's software version, OS platform, and IP address directly on the User Detail page in the Comet Server web interface. This was a minor feature request on our Feature Voting page. To view these new columns, click the "View" button to configure which columns are displayed. Your custom column selection is preserved for this browser throughout multiple page views, but your custom column selection will be reset when a new version of Comet Server is released.

If your Comet Server is configured to show software downloads to logged-out users, the login screen has expanded the number of download options from three (Windows, macOS, and Linux) to four with the new Synology download button. This fixes a minor inconsistency with the web interface as this fourth platform should be shown in the same context as the other three platforms.

There have been many cosmetic improvements to the Comet Server web interface too, including better spacing and padding when configuring an Office 365 Protected Item or a Windows System Backup Protected Item. We regularly make small improvements like this, but this month, we've also been working on a much more major cosmetic change for the Comet Server web interface. We will be able to share more information about that soon.