I am a Kiwi, but I was born in Cairns, Australia. I only spent six weeks there, don't judge me for that! Then growing up, I lived all over New Zealand. I have mostly lived in Christchurch, but I've also lived in Oamaru, Wanaka and spent my twenties in Wellington. On the brink of New Zealand's first Covid lockdown in 2020, I returned to Oamaru to look after my Mum during the lockdown. That brought me back to the South Island, and then I was naturally drawn into the nearest city, Christchurch, and also I have a lot of friends still here from when I lived here before.
Nearly two years. I joined an excellent support team, now I lead a very different - still excellent - support team.
What attracted you to Comet and the Customer Support role?
I was shoulder tapped for the position by someone in the leadership team here at Comet Backup. I was looking for work after moving to Christchurch. I had the right IT experience and qualifications. And I'm also a "grammar pedant" and British comedy fan, so I fit within the culture!
What is the scope of the Customer Support role at Comet?
I'm the Customer Support Lead here at Comet Backup. The primary role is answering support tickets and taking support calls with customers.
I also provide technical support for onboarding customers. Sometimes onboarding is an extended enquiry, sometimes it is essentially a support call, i.e., "I'm trying to set up my server in a specific configuration". I also look after Tier One Support based in Europe. I'm essentially 2.5-level support; I end up with escalated tickets. I also report on support tickets in general, volume and any trends of note to management.
The role does have the freedom to expand into other areas; for example, sometimes, I also work on special projects like testing specific use cases with Comet, and recently did some work on the IAM side.
What was it that appealed to you about Comet's culture?
I figured that since I knew someone who worked here, and I knew that that person would not put up with a bad environment – then it must be a good place to work. So, I had that indirect recommendation/validation.
How have you found your manager's style of managing you?
I really like how my manager manages me. He is really hands-off, he doesn't micromanage me, but he does watch from afar. He's very proactive at flagging possible issues I might want to consider. He also listens to my views and opinion on important matters.
What advice would you have for someone following in your footsteps in the customer support area?
Do what interests you, but also try to do a bit of everything. It's great to specialize, but it's also helpful to have a wide array of systems you have experience with; you don't know what you're going to encounter. For example, I was the only person in my course, possibly even in the history of my network engineering course, that opted for the Linux server admin (RHCSA) course instead of the Windows server admin (MCSA) course. I did that because I already had a job where I was administering Windows servers, so I thought it was a good opportunity to learn more about Linux.
If you want to learn a new skill and you don't know how to use Linux, I would recommend installing command line only Debian Linux on your personal computer's primary operating system and seeing how far you can get. If you get stuck, just Google it… from the Lynx browser. That's how I learned!
When there is an opportunity to work on interesting customer problems in the tickets. Friendly customers with stories, for example, when they were a video games developer in the 90s. Yeah, so interesting problems and interesting people make for a great day at Comet for me.
Don't be afraid of Linux. Certainly, if you don't know how to use Linux, don't put everything on it in production because it's cheap. That is how you lose everything. Definitely use the system you're most comfortable with diagnosing in an emergency. Linux can be a great option as it's much more cost-effective than some other options in the marketplace.
It seems that you perform a very important function at Comet Backup of feeding back to the Development team on the user experience. Can you tell me a little more about that?
Yes, that comes from my team always showing customers how to do something. Through the process of talking customers through the steps, we see how the interface performs first hand, which the Developers don't get as much exposure to. So, I am often giving feedback on UX/UI, how Comet could work best from the customer's point of view.
It also works with information going back the other way. I can translate how the feature works, and I think customers appreciate a more specific and candid response rather than a corporate, sanitized one.
If you could have any tech superpower, what would it be?
My superpower would be taking any feature or piece of software from a product and making it work seamlessly on another.
I'd replace the Windows 11 interface with KDE. I would take Nvidia features and put them on my AMD card. I would take nothing from macOS (laughs).
I'm a big fan of the Looking Glass project, which is kind of like a superpower. It takes a lot of configuring to work, but gaming in a Windows VM on Linux is very cool tech.
Comet is headquartered in Christchurch; what do you enjoy about living here?
Christchurch has great weather. Post-earthquake, there are fantastic restaurants in the city centre. If you're in the city, it is quite walkable and has a lot of cycleways, and I am avidly "anti-car” and I’m committed to never owning a car. I have driven a car twice in my life and I don't have a driver's license. I miss my friends in Wellington, but not the weather.
Why do you dislike cars? Is it just because you are an environmentalist?
I put off getting my driver's license for so long that I never acclimatized to the convenience of having one, which I think I a lot of people do. I think cars are inefficient as a transport method and they shouldn’t be required to get around. I have a reputation around the office for being the "anti-car" guy. I do wear it as a badge in a "Tyrion Lannister" sort of way; I laugh with the jokes and it can lead to great office debates.
Which restaurants in Christchurch would you recommend?
One of my favorites from pre-quake times is known as "AFG" or “the Afghan Restaurant" on Lincoln Road. There is a sign with the hours of opening that hasn't been put out in years because the owner just opens when he wants to. The only way to really know when they are open is to join the unofficial Facebook group called “Is AFG Open?” It's not vegetarian-friendly, there is one item on the menu, and when you walk in, he asks you, "How many?" As in how many servings are you ordering? (Laughs) It's spiced butter rice with two generous sized lamb and chicken kababs, a pot of tandoori chicken curry, and a salad. All for the grand sum of $20NZD. I make more than one meal out of it.
Like many foodies, you are also an avid home cook. What is your favorite dish at the moment?
That’s an exaggeration! I’m quite lazy with food but I can also get carried away when I find an elaborate recipe.
I bought a pressure cooker a while ago. One of my favorites to cook at home at the moment is Dakbokkeumtang, which is a spicy chicken stew.
I also make a lot of chili con carne. One of the developers grows chili plants at home and gave some of us some seedlings.
"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 February 2023.
There were just three Comet software releases during February - two in the 22.12.x Voyager release series, plus the launch of our latest quarterly series 23.3.0 "Leda".
February is a short month, and it was also a quiet month for new feature development as we focused on quality assurance ahead of the new quarterly software release. Most new feature development this month has been held back as a result, so you will see many more exciting new features land in the 23.3.x "Voyager" series when it reopens shortly next month in March.
The latest 22.12.x versions of Comet included improvements to the email reporting features that launched at the start of the 22.12.x series.
The Recent Activity email report template now includes a table legend in the email footer, helping to distinguish the color series from each other. By way of comparison, when you view Comet Server's Recent Activity page in a web browser, it's possible to hover the mouse over each color segment to display more detailed information about the breakdown of different job types. However, email is a more limited technology medium and an equivalent hover feature is not available. The legend is a simple solution that makes the Recent Activity email report more accessible to Comet Server operators who are not yet familiar with the colors.
The email feature has received more attention to detail, leading to us developing additional fixes for email report previews; for filtering the subset of customers; and for partial configuration of time boundaries.
Another one of our areas of focus this month has been the granular single-file restore system, that now shares some common core functionality across both the Disk Image and Hyper-V Protected Item types. Granular restore now supports more types of NTFS compressed file, including a fix for files that have been compressed with the LZNT1 algorithm. We also fixed an issue with reading single files from within NTFS partitions that have a highly fragmented MFT (Master File Table).
Additionally, we have fixed additional issues with the new Hyper-V single-file restore if a single Protected Item contains multiple virtual machines with multiple VHDX images, as well as fixing cosmetic issues when toggling between Protected Item types in the Comet Backup desktop app.
There have been improvements to the process of syncing Comet data with Gradient MSP. As a reminder, this is an external service that can correlate your Comet user accounts and storage usage with RMM invoices in systems such as Autotask, Syncro RMM, Connectwise, and many more.
The latest versions of Comet Server allow more fine-grained control of the connected feature set; the ability to toggle sending backup job failures to the RMM; optimizing the number of alerts that are sent; and providing clearer error messages if there is an error from Gradient's service.
All of our focus on bugfixes this month has been building up to one thing - a smooth and seamless release of our latest quarterly milestone software version. This time, it's named "Leda", and this rolls up the whole quarter's worth of 22.12.x enhancements into a new fixed point for you to build your business on.
Like Comet's previous recent quarterly software releases, "Leda" is named after a moon of Jupiter. Jupiter has a great number of moons and more are continuing to be discovered. When Leda was discovered as recently as 1974, it was one of Jupiter's 13 known moons. Today, Jupiter has 92 known moons, with the most recent discovered just this month in February 2023!
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.
"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 January 2023.
We've entered the second year of the "What's New" blog post series. There were seven releases during January - five in the Voyager release series, plus an additional two releases in the quarterly "Ananke" series.
The latest Voyager versions have an exciting new feature for the Hyper-V Protected Item type - when restoring a Hyper-V backup job, there's now an option to choose a granular restore of individual files inside the disk .vhdx file:
If you've used Comet's Disk Image Protected Item type, it's much the same - choose the "Restore files and folders" radio button option and click the "Next" button. When browsing the files to restore, the virtual machine's .vhdx file will appear as a folder instead of a file, allowing you to navigate inside the interior partitions and select files from supported filesystems.
It understands both GPT (Hyper-V Gen 2) and MBR/EBR (Hyper-V Gen 1) partition table layouts. The option to restore single files is available for older existing Hyper-V backup snapshots that you have taken with older versions of Comet Backup; it doesn't require you to take new backup snapshots.
There are some caveats to note. As with restoring single files from a Disk Image backup snapshot, this feature currently parses NTFS filesystems only. It doesn't yet support .avhdx differencing disks, only the .vhdx files within the backup snapshot - so if you are using Hyper-V checkpoints, and there are checkpoints present within the backed-up snapshot, then you'll only be able to perform a granular file restore from within the oldest base Hyper-V checkpoint.
This was a highly requested feature from our Feature Voting page. Just as a reminder - you can use this system to request features to be developed, add your votes for features requested by other users, and get notified when new features are available.
The 22.11.2 and 22.12.5 versions of Comet Server fix an important security issue related to administrator accounts. A malicious administrator with access to certain settings areas could achieve remote code execution on the Comet Server host operating system. If you share your Comet Server with untrusted tenant administrators or untrusted limited-permission administrator accounts, then we strongly recommend upgrading at the earliest possibility.
A separate notice has been sent to all self-hosted Comet Server users to encourage them to upgrade.
Last month, we added a new feature to Comet Server to send custom email reports based upon searching over your entire customer base. This can be used for sending an "all customers" report to your system administrators and staff technicians; or, it could be used to send a targeted email to specific groups of customers.
This month, we've extended the email system to include two new email report templates: the Recent Activity report and the Grouped Status report.
These two new template options are available for both individual users and as part of the new multi-customer email report system. When configuring an end-user's report, you can use the "Preview" button to quickly check your custom filters.
Another related feature for the email report system is the new guidelines for time boundaries. Previously when using the "Summary Table" report type, all jobs from all time would be included in the report. Users would have to configure a "Time since job start" is "greater than"... filter in order to restrict the results to show only recent jobs. To make this easier for users and for administrators, there's a new option in the configuration dialog that sets a default time boundary and makes it clear that it should be configured.
The Recent Activity report uses a fixed time-bound of the last 10 days, the same as the Recent Activity view in the web interface.
In Comet, you will eventually want to delete backup snapshots from your Storage Vault. The main use case is to free up space that is being consumed by very old backup jobs that are no longer required. For this use case, the Retention Policy system takes care of this automatically based on your configured retention rules.
Another use case for deleting snapshots is if you accidentally back up a large amount of data. For instance, maybe your Downloads directory was included in the Protected Item selection unexpectedly. For this use case, the Comet Backup desktop app allows you to delete specific backup snapshots by right-clicking them from the Restore wizard. You can delete single snapshots, or all snapshots for a selected Protected Item. You can also delete single files and folders from within a snapshot.
Every time you delete snapshots, the Comet Backup desktop app deletes the specific snapshot, and then, deletes any stored data that is no longer used by any snapshot. The first part is quite fast and the second part can take somewhat longer. If you have a large number of snapshots to delete, it's preferable to request to Comet that it deletes all your intended snapshots, and only then, runs the second "cleanup" phase.
To allow for this, the Comet Backup desktop app now has an advanced "Delete" option in the Restore dialog. When clicking this button, you'll see a new popup dialog with the option to make an arbitrary selection of snapshots. The internal ID of the snapshot is also displayed if you are acting on advice from your support contact.
Overall, this new dialog makes the process much more efficient as the cleanup pass only needs to run once for the entire set of deleted snapshots.
If you don't want to allow your customers to delete individual backup snapshots, you can prevent this by checking the "Prevent manually deleting backup snapshots from a Storage Vault" option in that user's Policy settings.
Remote browse for MySQL, Microsoft SQL Server and MongoDB
In the Comet Backup desktop app, when configuring a new database Protected Item for MySQL, Microsoft SQL Server, or MongoDB, you can use the "Items" tab to browse the content of the database server, to select individual databases for backup.
This feature has been available in the Comet Backup desktop app for a while. In the latest 22.12.x "Voyager" series, we've also made this available from the Comet Server web interface:
Use the new green folder icon to remote browse. If the device isn't currently online, you can still use the green plus icon to manually enter the names of databases to include and exclude from the backup job.
This feature works by remotely controlling a Comet Backup device that has an active live connection to the Comet Server. This allows you to remotely browse databases that are reachable only from the device's network position, such as the device's localhost or databases within the device's local area network (LAN).
As a related feature, we've upgraded the way that Comet Backup connects to a MongoDB database server. Comet no longer requires you to configure the "Mongo Shell" application, which was difficult to obtain for newer versions of MongoDB. This Protected Item type should now be a lot more reliable and easy-to-use.
There have been a few notable performance improvements throughout the 22.12.x "Voyager" series during January 2023. Retention passes use less peak memory, which can be a significant quality-of-life improvement for smaller laptops and NAS devices accessing a large Storage Vault.
Browsing a user's job history is now faster in more cases. If you are using the Job History API to search for the number of backup jobs meeting certain criteria, there is now a separate dedicated API to count jobs that can transfer a much smaller amount of data. There have also been speed improvements for Comet Servers that have a large number of tenants.
The Comet Backup desktop app has been streamlined, to show the "New Protected Item" dialog when using the app for the first time on a new device. If you're a "hands-off" service provider, this should make it easier for new users to get started backing up their files. We've also added new warnings when saving a Protected Item without actually selecting any files or databases for backup.
The account.cometbackup.com website has also had minor improvements. You will now see the filesize of uploaded ticket attachments, the country for Self-Hosted Comet Servers, and extended configuration for email forwarding for Comet-Hosted servers.
I am originally from the Philippines. I came to New Zealand in 2016. I decided to move to New Zealand because it has a high standard of living. And also, the Lord of the Rings was shot here, and I thought it was a beautiful country.
Since April – so just coming up to ten months now.
What attracted you to Comet and the Customer Success role?
Before joining Comet Backup, I was an Onboarding Executive at an online eCommerce retailer. I moved to the Technical Support team with that company just before I spotted the role at Comet backup. The job description looked really interesting, and I was attracted to the variety within the role. It sounded like no two days were going to be the same.
What is the scope of the Customer Success role at Comet?
To summarise the role in one sentence, I'm responsible for all non-technical customer communications and new customer enquires pricing inquiries. Facilitate the "next steps," getting them in touch with the Technical team, understanding their requirements for backup software and ensuring that's communicated to the wider team so that the rest of the team understands the potential customer's requirements.
What was it that appealed to you about Comet's culture?
When I interviewed with my now manager, one of the statements he made up front was that Comet doesn't hire jerks! They only employ nice people – I felt that was a big claim; it's hard to gauge a person's character before hiring. Comet isn't just interested in 'talent.' There is a focus on building a culture of cooperation and team building. I thought that sounded like a really promising company culture, and I wanted to be part of that. Also, it was made clear to me that I would be able to learn, explore and possibly make mistakes – that was all allowed at Comet Backup.
How have you found your manager's style of managing you?
I like that I'm given a lot of freedom to make decisions. It's a very challenging environment, and I like that. I feel like I'm trusted to make a call on some bigger issues, for example whether we should partner with a particular company for an integration to Comet Backup. I have the freedom to say, "this is what I think we should do," and my rationale behind my thinking. I think that's the best way to learn and see how it goes, within reason—being able to take calculated risks.
Do you feel it's contributing to your career growth in the direction you want to be going?
I'm definitely learning from getting to make my own decisions. I'm also learning a lot about the cybersecurity industry as I'm new to it. I am learning about the technology that is relevant our product. It's not a topic you can read up on; you have to absorb it through experience and application of that knowledge.
What advice would you have for someone following in your footsteps in the Customer Success area?
Understand your role and what you need to accomplish your goal. Next, identify what you need to know to do that role. And then seek help to learn. Don't be discouraged if you don't get it right away; it will stick eventually if you keep at it. There is a lot of jargon, but don't expect yourself to understand everything all at once. It will make sense eventually if you keep on asking questions. Make an effort to use the terms. Even if you misuse the term, people will correct you, and you'll learn! I was raised to believe that everything is learnable; you just have to put in the effort.
What makes a great day is when most of the team comes into the office. Ah, and if the taco truck turns up, a free coffee and a funny slack thread going about the memes or the latest Elon Musk shenanigans. [Laughs]
If you could have any tech superpower, what would it be?
I would like to have the superpower to make old technologies like Betamax, VHS, and the old family Nintendo work again. I'd bring them all back, make them work all the time, and never die!
Comet is headquartered in Christchurch; what do you enjoy about living here?
It's very flat, so it's very easy to walk around. Easy access to South Island and there are a lot of places in the South Island to explore, like Twizel for skiing, and if you want to go to the seaside you can go to Akaroa.
I know that you are a foodie. To the non-initiated, what is the must-try South East Asian or Filipino dish?
Oh, that's a good question. I would say because it's summertime, you have to try Filipino mangoes. They are soft and juicy and supper sweet. You get more flesh as the seed is relatively small.
What are your thoughts on the controversial South East Asian fruit, Durian?
I'm not a fan! Warning; only eat outdoors or with all the windows open! The taste of the flesh isn't too bad, but the skin is very smelly, it smells like garbage. It must be a protection mechanism for the fruit.
You are about to go back to the Philippines. How long are you going back for, where are you going, and who are you seeing?
The last time I was home was in 2019, so it's been about three years. I'm just visiting family, but that's a lot of people because I have a very big family and I want to spend some time with all of them. I'm going to Manilla, where they live. The highlight of my trip will be visiting Boracay, which is a really nice beach. I am going to relax, have a coffee or Mai Tai or Pina Colada… at 11 am… guilt free… [Laughs]
What are your thoughts about the new employee benefit that Comet have launched for staff – free health cover for the employee – including pre-existing conditions?
That was so generous of them, as health insurance is so expensive these days. It's a really good perk that not a lot of companies offer their employees. It was really thoughtful and caring of them. I'm a huge fan of having dental care cover included.
Professionally, I enjoy that the Management really wants to give you every opportunity to improve your skills. You're encouraged to make your own decisions; what I was saying before about I have their support to make my own informed decisions and learn from the experience, it's okay to make mistakes. I’ve found that's not as accepted in bigger companies, and they tend to be more adverse to risk. Also I’ve been encouraged to seek development and growth. They have invested in my development; for example, I'm currently completing the Certified Customer Success Manager programme, which is the most recognised Customer Success qualification.
Personally, I've enjoyed the fact that I've found that my manager was true to his word, and I have found that he's made every effort to hire people that can have different points of points view or opinions but not take that to a personal level and get the best outcome for the customer. We're not pitted against each other to compete.
"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 December 2022.
December was a quiet month for Comet development as we entered the holiday season. After the release of 22.11.0 "Ananke" in late November 2022, December saw the "Voyager" series reopen with two releases in this 22.12.x series, plus one point-release in the Ananke series for a total of three releases.
As a Comet Server administrator, it's now possible to configure a single email report covering multiple customers. You can use this new feature to receive a regular report of all your customers, or, you can create custom reports for groups of specific customers.
You can access this from the Comet Server web interface, on the Settings page > Email Reporting tab:
This settings page previously contained only email reporting configuration, such as your SMTP server and "From" display name. The page now contains additional email-related settings including your custom reports. You can use the "Add" and "Edit" buttons in the table to create a new report, using the same configuration options you are familiar with from the existing per-user email reports.
When creating a report, you can choose to include all customers and send the report to yourself; or, you can add a "Username" "equals" filter to find a specific group of multiple user accounts and send the report to their designated contact. Both the "Summary table" and "Immediate job notification" report types are available in this dialog.
A special thanks to all the Comet users who upvoted this feature in our Feature Voting system. We check this system regularly to help guide our priorities.
The Office 365 Protected Item type in Comet allows you to back up an Office 365 tenant from your Comet Backup device, including mail, contacts, calendars, OneDrive files, SharePoint sites and more. At the time of writing, using this Protected Item type comes with a "Booster" charge of $1.50 USD per Protected Account. When you select an Office 365 resource to back up, such as an employee's mailbox or a shared OneDrive drive, all Office 365 users within the tenant who can access that resource are tagged as "Protected" for the purposes of Comet billing.
This is a simple system that scales with the size of your Office 365 tenant. However, we heard feedback from MSPs that unexpected changes to their customers' Office 365 tenants were resulting in unexpected charges to their Comet balance. To help mitigate this, we've introduced a quota feature for the number of Protected Accounts covered by the Office 365 Protected Items in a Comet user account profile. If more mailboxes are added to the Office 365 tenant and are selected for backup, if the total number of Protected Accounts exceeds the configured quota limit, the backup job will not run to prevent any unintentional charges from being billed to your Comet account.
If a user has reached your expected limit of Protected Accounts, you can detect this from the "Quota Exceeded" job status. This job status is specially highlighted on the Comet Server home screen and can also be seen from the search and user pages. When detecting this case, you can raise the limit and also modify the invoices you send to your customers.
We're very pleased to announce the new Polski (Polish) translation in Comet 21.12.0 "Voyager". We'd like to extend a special Dziękuję bardzo! (Thank you very much!) to the very dedicated Comet partner from Poland, who supplied the initial version of this translation and worked back-and-forth with us to ensure a high quality result.
Warsaw Skyline / Skitterphoto (CC0)
As a reminder, if you're interested in correcting a translation in Comet or helping to translate Comet into a new language, then please check out the instructions on our GitHub page.
Microsoft will stop extended support for Windows 8.1 and stop ESU support for Windows 7 on January 10th 2023. From this date, no security updates will be available from Microsoft for either Windows 7 or Windows 8.1.
Comet Backup will continue to work and will continue to support Windows 7 and Windows 8.1 for the foreseeable future; however, your customers may be exposed to operating system security issues unless they upgrade to Windows 10, Windows 11, or Linux at their earliest opportunity.
"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 November 2022.
November was a more active month for Comet development. There were six "Voyager" releases in the 22.9.x series during November, plus the first release of our new 22.11.0 "Ananke" quarterly series. This exceeds our previous quiet release volumes in October and September. A large number of minor cosmetic improvements were added, as well as many small bugfixes, so we would recommend that all users of previous 22.9.x versions should continue to follow the latest updates for the best experience.
Comet 22.9.8 now includes a native Apple silicon version of Comet Backup for macOS. This will improve efficiency when running on recent Apple computers with M1 and M2 chips.
Your existing macOS users will likely be running the current, x86_64 version of Comet Backup for macOS on their M1 or M2 hardware. The x86_64 version does run well under Apple's high-performance Rosetta2 emulation layer included with macOS. In addition, the backup job speed is usually limited by network speed or disk I/O, not CPU speed, so running under emulation is not likely to significantly impact backup job runtimes. However, the native version for Apple silicon will be more CPU and battery-efficient. After upgrading to the native Apple silicon version, there will be no visible difference to the end-user, except for a snappier and longer-lasting computer.
When an existing macOS user, running a version of Comet prior to 22.9.8 on M1 or M2 hardware, is part of a Bulk Upgrade Campaign to upgrade their installed Comet Backup client app, they will first upgrade to the 22.9.8 x86_64 version under emulation. This version can detect that it is running under Rosetta2, and during the following software upgrade, it will upgrade to the ARM64 version instead of the x86_64 version. As a result, two upgrade cycles may be required for all macOS users to receive the full performance and efficiency benefits of this change.
Comet 22.9.6 added a built-in feature to integrate with Gradient MSP. Gradient MSP is an external service that allows you to sync user account data and backup job error alerts into many RMM/PSA systems including ConnectWise, Autotask, Kaseya, Syncro, Pulseway RMM, HaloPSA and more. There is no cost to connect one Comet Server to one PSA.
Check out our launch webinar below to see how to take advantage of this service to connect your Comet Backup user accounts to your PSA platform, perform billing and invoice reconciliation, and receive alerts about failed backup jobs.
The latest version of Comet Backup adds support for a quick access download button directly within the navigation bar. This is intended to help first-time users of the Comet Server app find this option more easily, as well as being a quick option for experienced users.
Long-time users of Comet Server might remember the original version of this feature - a download icon in the top navigation bar - that existed between Comet Server 17.3.2 and 18.5.0 "Phobos". It was removed in Phobos owing to the introduction of the download links on the login screen, and also the download button within the home-screen 2x2 button pad.
Change your root keys for Comet Storage Powered By Wasabi
During November we added support for regenerating the top-level root access keys for your Wasabi account. The top-level root access keys are needed by Comet Server for the Storage Templates feature, to automatically provision new direct-to-cloud Storage Vaults for your customer. Being able to rotate these keys and issue new replacements can be a crucial feature if anyone gains access to your Comet Server configuration.
For your convenience, if the old keys are in use on a Comet-Hosted server for a Wasabi Storage Template, or for Constellation, then the Comet-Hosted server will automatically have its settings changed to use the replacement keys.
It comes with built-in examples and is built for TypeScript first. The SDK also contains generated JSDoc typings, ESM and CommonJS bundles, making this suitable for both Node.js and browser users. We've also created a sample app using the Next.js framework that shows how you can use this framework to create a custom B2C signup form for Comet Server using the new SDK.
The Comet Server web interface is a "single-page app" (SPA) that uses the same Comet Server API for its entire feature set, ensuring that our Comet Server API is stable, reliable and well tested. For many years now, our own Comet Server web interface has been entirely developed using Typescript, using a private internal version of this same SDK. We're very pleased to be able to release this work publicly under the open-source MIT license, unlocking productivity for Node.js, TypeScript, and JavaScript programmers looking to integrate Comet Server more closely with their businesses.
The Comet Server API is JSON over HTTP and can of course still be used in programming languages that do not yet have an official SDK, and we have many code samples available for other programming languages in our documentation.
We've just put the finishing touches on our latest Quarterly release, 22.11.0 "Ananke". This rolls up the whole quarter of 22.9.x enhancements into a new fixed point for you to build your business on.
Like Comet's previous recent quarterly software releases, "Ananke" is named after a moon of Jupiter, discovered as recently as 1951. It's the largest moon of the "Ananke group", a set of seven of the moons of Jupiter that have similar orbits and are thought to have a common origin. The moon is named after the ancient Greek mythological goddess of inevitability and necessity.
If you prefer to watch and listen rather than read, I'm hosting a webinar next week to discuss the latest 22.11 "Ananke" software release. Please register for a notification before we go live on December 6th (PST) to catch up on all the latest Comet news with me - there will be a free live Q&A session after 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.
"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 2022.
October was a quiet month for Comet development. There were two "Voyager" releases in the 22.9.x series during October, matching our previous September release volume. A large number of minor bugs were fixed, so we would recommend that all users of previous 22.9.x versions should continue to follow the latest updates for the best experience.
In the Comet Server it's now possible to migrate a user account between Tenants. To do so, click the "Transfer user" option from the "Actions" menu on the user account page.
When you log in to the Comet Backup desktop app, the login is directed to the Auth Role server URL. Each Tenant in Comet Server generally has its own isolated Auth Role URL for the clients to log in to. When you use the "Transfer user" option, a signal will be sent to the online logged-in devices, to redirect them to log in again to the updated URL.
However, it's not possible to send this message to an offline device. If there are any offline devices, the Comet Server web interface will warn you about this situation - you'll have to manually reconfigure any such devices to use the new login URL, as they will not be able to log in at the previous URL. You can make this change from the Comet Backup desktop app at the login screen, or by using the 'Update Login URL' live action at any other time.
Our June 2022 recap blog post covered the new feature to allow custom SMTP servers at the Tenant level. One of the key limitations of this work was that the top-level administrator was required to configure these settings on behalf of the tenant. This is unfortunately an important restriction from a safety perspective, as it can help insulate the top-level administrator from any repercussions related to the IP reputation of their mail server.
The Comet-Hosted service is based on the Tenants feature, and correspondingly the responsibility for custom SMTP configuration falls on the account.cometbackup.com web application. We're pleased to announce that the IP reputation concerns have been addressed for this environment, and it is now possible for you to configure a custom SMTP server for your Comet-Hosted server via the 'My Servers' page:
Another change affecting the My Servers page on the account.cometbackup.com website, is that this page has received a design overhaul to now show your servers in a table view, instead of a card view.
When redesigning this page, our design goals were to make the page more intuitive for new users as well as more powerful for existing users. With the new design, the page is more scalable if you have a large number of Comet servers (either Self-Hosted or Comet-Hosted). It's more visually consistent with the design of the rest of the account.cometbackup.com site, and the ability to log in to a Comet-Hosted server is now clearer and much more obvious.
The Credit Usage report at account.cometbackup.com shows you a detailed history of all deductions to your Comet account balance. It's an essential tool for partners, to ensure you are appropriately matching your Comet expenses to your customer invoices. For partners with a large number of installed devices, or a very long history, this page can become cumbersome. We introduced a search feature on this page some years ago, but advanced filtering was not yet available, unless you exported the whole result as CSV or XLSX for external processing.
We're pleased to announce that it's now possible to filter your Credit Usage history by date, via the fields on the 'View' dialog.
This feature was a long-time request from our Feature Voting system. The regular feedback for requesting this feature helped us prioritize the work - so if there's anything you want to see in Comet, please do make your voice heard in the feature voting system.
It's long been possible to "copy and paste" a Protected Item from the Comet Server web interface to duplicate it, however, this functionality was restricted to the web interface. As of Comet 22.9.4, you can now right-click a Protected Item in the desktop app to "Duplicate" it.
This is a welcome convenience feature for users of the Microsoft SQL Server, Office 365 and Hyper-V Protected Item types, which can in some cases benefit from having multiple Protected Items with slightly different settings. By duplicating a Protected Item and then making minor customizations, it can be much faster to configure these from the Comet Backup desktop app.
Throughout the COVID-19 pandemic, the Comet team have been fortunate to be able to keep working remotely, while still continuing to expand the team by hiring and training teams of developers all over New Zealand. As restrictions lift, we brought the NZ team together face to face for the first time for the inaugural "Cometcon", a week-long event of networking, professional development, training, and brainstorming about Comet development.
We're looking forward to bringing the remote team together more regularly in the future!
"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 2022.
September was another busy month for Comet, following on from August and our release of Comet 22.8.0 "Carme". The Carme release has been very well received, and we have not yet needed to release a patch update for it.
There were two "Voyager" releases in the 22.9.x series during September. We followed through with the removal of Windows Vista support, as discussed in our August blog post. This has reduced the filesize for downloading the Comet Backup installer by about half, which is a significant improvement and helps new users start using the app sooner. This change has also made it possible for us to perform a lot of technical cleanup internally to the software, removing edge-cases and upgrading libraries.
Comet 22.9.2 added support for direct streaming restore of Microsoft SQL Server backups, straight back to your database server, without any temporary spooling.
This follows from last month's support for streaming MySQL restore in 22.9.0.
When you use this option, the Microsoft SQL Server backed-up data will be streamed from Comet's Storage Vault into Microsoft SQL Server without needing to temporarily storing any .bak files and manually importing them via SQL Server Management Studio (SSMS).
You can configure the Microsoft SQL Server restore feature with all the same connection settings as for backup. The settings will be prefilled based on the current matching Protected Item, or they can be changed as required. This feature is available for restores performed in the desktop app, or remotely via the Comet Server web interface, or via the Comet Server API.
If your Microsoft SQL Server uses the "FULL" recovery mode, Comet Backup can take differential or log backups from the database. Generally we recommend always taking Full or Copy backups - Comet will chunk the whole database into an incremental-forever deduplication system, so that you don't need to worry about chains or full images or log truncation. However, in some very large databases, you may still wish to do this. To restore a differential or log backup in Comet, you should first restore the matching full backup with the "I want to keep restoring additional files (WITH NORECOVERY)" option set; and then, restore your target differential or log files with the "This is all I want to restore (WITH RECOVERY)" option set.
Following on from last month's redesign of the Comet Backup desktop app main screen, we've made some more minor changes. When creating a new Storage Vault using the 'Custom' option, the Comet Backup desktop app now shows this in a wizard.
This brings the behavior in line with creating new Protected Items in the Comet Backup desktop app: a wizard is used for initial creation, to help guide you through the process, but after initial creation a tabbed dialog is used, for quickly jumping to any setting.
We've also applied a cosmetic redesign of the Search dialog in the Comet Backup desktop app, to also use a wizard, allowing easier back and forward navigation. In particular, this is helpful if you want to change the set of search snapshots after having already entered a filename.
The restore dialog now lets you properly resize columns when selecting a Protected Item for restore.
There were also various fixes for viewing job reports from inside the desktop app. The 'View Log' button is now more responsive when first shown; long job report lines have better word-wrapping behavior, especially on macOS; and very long job reports will now load more quickly.
Webhooks and Websockets are two features of Comet Server, for external partners to receive live notifications of changes inside the Comet Server. These features are used by third-party apps and services to ensure their synced data is fully up to date and responsive to the latest changes.
In Comet Server, the Tenants (formerly "Organizations") feature allows you to create a private, isolated zone of user accounts. The top-level administrator has visibility over all tenants, both in the Comet Server web interface and in the API. In Comet 22.9.1 we've ensured that Webhook and Websocket events for the top-level administrator will now include events from sub-tenants, fixing a consistency gap.
We've also added the option to filter which types of live event messages you would like to receive when constructing a Websocket, by using query parameters (e.g. ?allowList=4100). This brings the websocket support more in line with the Webhook support, which allows any choice of event messages.
Now that the Webhook and Websocket features are more aligned in terms of feature support, the choice of tool is primarily driven by whether you prefer the "push" or "pull" model for events. This comes down to practical decisions about network firewalls, connection establishment, message ordering, deliverability guarantees and observability.
One last thing to point out about Webhooks is that in the Comet Server web interface, we've renamed this tab to "Integrations" - for reasons that will become clear next week!
Thanks for reading - there are some great new features in the development pipeline, that we're excited to be able to share with you soon in the upcoming 22.9.x Voyager series.
"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 2022.
This month at Comet we've been busy with behind-the-scenes changes. We've been lucky to continue to welcome many more new staff members that have joined the development team. Throughout August, there were three "Voyager" releases across the 22.6.x series; the launch of the new 22.8 "Carme" quarterly release track; and the slightly early reopening of Voyager for the 22.9.0 release.
Carme is the latest entry in our quarterly rollup series. It branches off from our main rolling Voyager development, into a fixed target for our partners to qualify and build upon.
Comet 22.8 "Carme" takes its name from another moon of Jupiter. It was discovered along with our previous Comet release "Lysithea" by Seth Barnes Nicholson in 1938, and both discoveries were reported in the very same publication. Jupiter's moons are classified into groups, and despite sharing a discovery event, Lysithea and Carme come from different groups of moons and have very different orbital properties. The moon itself is named after the Cretan goddess Carme, one of Zeus' lovers.
Carme brings 7 features and 14 enhancements, including IDrive e2 support, presigned clients, the ability to spread out peak job load across a random period, custom SMTP servers for Tenants, support for fallback domain controllers, more restore options, and improved performance.
For this last month of August, there have been very few features landing in the Voyager release track, with mostly a focus on fixing issues. This has resulted in a trouble-free release process and a great release that we have confidence in. It does mean that there are only a few new features and enhancements to cover, as all the larger changes were held back for the 22.9 "Voyager" release.
In early versions of Comet, macOS codesigning required Comet Server to SSH into a real Mac machine somewhere on your network in order to run the official XCode toolchain. We were very proud to integrate rcodesign as a native, built-in alternative in Comet 22.3.3; the bundling of pre-signed clients in Comet 22.6.2; and now, no longer requiring the third-party iTMSTransporter application as of Comet 22.6.9.
In our company we use the Go programming language extensively, so it's perhaps a little unusual that we didn't have a public Go SDK until this point. That's largely because PHP and Ruby produced the largest demand from external developers looking to integrate Comet with their web sites and ecommerce platforms; and in our in-house Go development environment, we can use the type definitions directly from Go without any SDK at all. However, having a public Go SDK definitely makes it easier to write and develop auxiliary tools, and we've already seen several utilities being ported to this great and efficient programming language.
Announcement about legacy operating system support
The 22.8.0 "Carme" release is the culmination of everything up through the previous 22.6.x "Voyager" release cycle. From this point, we're planning to make some bigger changes.
During the 22.9.x timeframe, we expect to remove support for running the Comet Backup desktop application on Windows Vista, Windows Server 2008, and macOS 10.10 "Yosemite".
If you have end-users running these operating systems, you should either
(A) stay with the 22.8 "Carme" release cycle, or
(B) install the 22.8 "Carme" Comet Backup desktop app and use it along with an upgraded version of Comet Server, or
(C) arrange for your end-users to upgrade to Windows 7, Windows Server 2008 R2, macOS 10.11 "El Capitan", or newer.
⚠ No longer supported in 22.9.x, please continue to use 22.8.x
⚠ No longer supported in 21.12.x, please continue to use 21.11.x
Windows Server 2008 R2 (NT 6.1 / Windows 7-based)
✅ Still supported
✅ Still supported
We don't take this removal lightly, but it's clear that in the present day, Windows Vista is not widely used or relevant, and we expect minimal issues as a result of this deprecation.
Although the Vista-based Windows Server 2008 and the Windows 7-based Windows Server 2008 R2 have the same extended support lifecycle, the underlying technology of the R2 update is significantly more advanced than the Vista-based RTM edition, and correspondingly easier for us to develop for. It's likely that Windows 7 and Server 2008 R2 will remain supported by Comet for a much longer period of time.
In Comet 22.9.0 "Voyager", we've put a new coat of paint on the Comet Backup desktop app. A picture says a thousand words:
The desktop app now shows you a summary of your Protected Items, Storage Vaults, and recent job history at a single glance. We're very happy to have struck a balance between information density, visual identity, and efficient performance as the charts remain using an optimized native-code renderer. We are excited to continue improving the UI going forward and we expect to make tweaks over the 22.9 "Voyager" series in response to your feedback before this lands in the next quarterly release.
This dashboard screen is divided into five main areas:
The Storage Vaults chart at the top left shows up to three Storage Vaults. If the Storage Vault has a quota, the sawtooth segment will be split into two colors showing the partial usage percentage of your Storage Vault quota. If you have more than three Storage Vaults, three are chosen for display based on whether they have Quota limits in place, and also whether they have been recently used on this device. Further details about your Storage Vaults remain available on the Settings tab.
The Currently Protecting chart at the top right shows a breakdown of your Protected Item size, across this device and across other devices in your account. If your Comet user account has a limit on the number of total devices allowed to be registered, or a limit on the total Protected Item size, these figures will be displayed here.
The Storage Vault size chart at the lower left looks at the past 10 days' of job history to build a visualization of how your Storage Vaults have grown or shrunk in that time. Comet measures the size of a Storage Vault during backup operations, so this chart is most effective if there are recent backup jobs for your Storage Vaults. A maximum of three Storage Vaults are shown, and as long as the necessary data points are available, the same choices and colors will be used as per the Storage Vaults chart at the top left.
The Transfer chart in the lower right looks at the past 10 days' of job history as well, to show the upload and download size for your jobs, including both backup and restore operations. These figures correspond to the Uploaded and Downloaded job report columns and at a technical level they reflect the transfer size to- and from- the Storage Vault. Notably this means that Upload/Download sizes may be reported even for Local Path storage vaults, and, Upload/Download transfer amounts for over-the-network Protected Item types (such as remote MySQL and MongoDB servers, or Office 365 tenants) are not currently reported here.
The news widget at the bottom shows bulletin messages created by the Comet Server system administrator. It's useful for contact details, notices of recent service changes, or promotional messages. Any news messages you create in Comet Server are shown immediately in the desktop app. If you have no news entries, this bottom section is hidden entirely.
We're excited to announce a partnership with Storj.io, a decentralized cloud storage provider. It's been possible to use the Storj service with Comet's S3-compatible option, but in Comet 22.9.0 "Voyager" it's now possible to connect directly to the Storj P2P network without involving the centralized gateway. This allows for faster performance during download operations and lower latency without the centralized bottleneck.
At the time of writing, Storj coordinate a network of over 13,000 storage nodes worldwide and can offer great low-latency to nearby storage nodes at an industry-leading price of $4 / TB and a generous free tier of 150GB.
Please note that when using Storj in this way, Comet performs client-side erasure coding to distribute data redundantly throughout the Storj network. The file upload size reported in Comet reflects the amount of data delivered to Storj, but the upload size experienced over the network may be higher as a result of client-side redundancy.
A key aspect of the Storj integration is the ability to configure Storj as a Storage Template provider:
Storage Template providers (formerly known as Requestable Storage providers) allow your Comet Server to automatically provision new, private Storage Vaults for each of your customers, with isolated credentials - including Constellation Role support for automatically cleaning up Storj buckets that are no longer used by any Comet user account.
As with all of our supported storage platforms, the new Storj integration is also available as a backend for Comet Server Storage Role, if you would prefer all customer data to flow through your Comet Server.
Comet supports backing up MySQL using our dedicated Protected Item type. This was one of the original Protected Item types included with the very first Beta versions of Comet, and is available at no additional charge. It works by streaming the output of mysqldump directly into our chunking deduplication engine, without requiring any spool space or temporary files.
In Comet 22.9.0 "Voyager" we've introduced corresponding support for streaming MySQL restores:
The data will be streamed from Comet's Storage Vault into the MySQL server without needing to temporarily store any .sql files and without needing to manually import them.
You can configure the MySQL restore feature with all the same connection settings as for backup. The settings will be prefilled based on the current matching Protected Item, or they can be changed as required. This feature is available for restores performed in the desktop app, or remotely via the Comet Server web interface, or via the Comet Server API.
This is a great feature that simplifies the restore process for this highly popular database. We expect to announce a similar feature for another popular database very soon, so keep an eye on our release notes for the latest news.
Configure webhooks from the Comet Server settings page
Webhooks are a feature to send live events from Comet Server to your other systems. They are largely of interest to developers who want real-time information to flow from Comet Server into other systems, such as CRM and ERP systems.
Comet Server has supported webhooks since 20.6.1, with major enhancements happening for custom header support in Comet 21.9.2. However, they've largely been hidden and confined to users who read the documentation and can make manual changes to the cometd.cfg file. In Comet 22.9.0 "Voyager", we're improving the discoverability of this feature by allowing you to view, edit and manage your current webhooks from the settings page in the Comet Server web interface.
This feature is available for webhooks both at the top-level, and for individual Tenants, including Comet-Hosted users.
As a top-level administrator, you can control permission to access this feature via the admin permission checkbox or via the AllowEditWebhooks API field.
Constellation Role has previously been restricted only to the top-level administrator. In Comet 22.9.0, it is now available at the Tenant level as well:
A "Bucket Users" report generated by a tenant Constellation is entirely independent of the top-level Constellation. The tenant also has an independent choice for the "Data deletion" setting.
Access to this feature can be controlled by a top-level administrator. If your Tenant administrator has all settings features enabled, this feature is included. If your Tenant administrator has been configured to have no- or limited- settings available, the Constellation Role feature is enabled by default. This is because Constellation Role is an essential partner of the Storage Template feature, to clean up disk space or cloud bucket space that was used by since-deleted user accounts.
Misuse of the Constellation Role feature can cause data loss, so please take care when configuring this setting. Our documented advice is that you should have exactly one Constellation Role for your Comet Server cluster; when running multiple Constellation reports on a per-tenant basis, the key advice is likewise to not overlap Constellation responsibilities - one set of user accounts and one set of buckets (local, Cloud Storage, Storage Role or otherwise) should be managed by one Constellation Role configuration only.
If you are using Constellation at the top-level of the Comet Server with top-level credentials, then it is able to see Tenant user accounts and deallocate their buckets as required. However, if you are in the situation of not using Constellation at the top level, or if you are not in control of which remote Storage Templates are used by your Tenants, then this new feature is especially useful to enable data cleanup.
If you prefer to watch and listen rather than read, I'm hosting a webinar next week to discuss the latest 22.8 "Carme" software release. Please register for a notification before we go live on September 6th (PST) to catch up on all the latest Comet news with me - there will a free live Q&A session after 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, and webinars for previous quarterly software releases.
"What's New?" is a new blog series covering recent changes to Comet in more detail. This article covers the latest changes in Comet Voyager over July 2022.
It's been a busy month for Comet, and we've been lucky to welcome many new staff members that have joined the development team. This month, the 22.6.x "Voyager" release track has seen five minor updates. We've also released two minor updates for our 22.5.x "Lysithea" quarterly release track. There were many interesting improvements:
We're pleased to announce that IDrive e2 are now available as a built-in option in the Storage Vault selection type. This direct integration uses the IDrive e2 API to automatically determine the target bucket hostname, reducing the number of configuration steps compared to the S3-compatible option.
As well as using IDrive e2 directly, you can also add them as a Storage Template provider (previously known as "Requestable" Storage provider) in the Comet Server settings area. If you enter your top-level credentials in this field, Comet Server can use them to provision private buckets with separate credentials for each user, allowing seamless direct-to-cloud backup without traversing through the Comet Server Storage Role.
A quick reminder - when using the Storage Templates feature, it's likely you'll want to configure cleanup for cloud buckets that are no longer being used by any user account. Comet's solution for this problem is called Constellation Role, and it's available from the settings page of your Self-Hosted Comet Server. In Constellation, you can enter the same IDrive e2 top-level credentials for it to search through. When a Constellation report runs, it finds all your buckets; checks all the user accounts; cross-references the user's Storage Vaults with the available buckets; and deletes any discovered buckets that are not in use by any user account.
Constellation is designed to scale up to clusters of multiple Comet Servers, with any mix of server replication, Storage Role, or direct-to-cloud buckets created by the Storage Template feature. You should have precisely one Constellation Role server amongst your entire cluster of Comet Servers.
In Comet Server 22.6.6, Constellation now has an extra safety guard to prevent deleting any data if no Auth Role server is configured. This feature can help prevent accidental misconfiguration. This feature joins the many other safety features in Constellation, such as the ability to turn off deleting buckets until you are satisfied with the discoveries it makes.
Amazon AWS first launched their ground-breaking S3 service ("Simple Storage Service") back in 2006. In the 16 years since then, the S3 protocol has evolved and grown, adding support for V4 signing, path-vs-subdomain bucket addressing, multiple regions, batch processing, streaming processing, and many more features. As "S3-compatible" has become the de-facto standard cloud protocol for object storage, there are many varied implementations of the protocol and many different providers require different quirks for compatibility.
Comet has an extensive set of auto-detection for various S3-compatible cloud storage providers, which all require slightly different configuration. We've recently encountered several S3-compatible providers all needing the same type of custom configuration, related to the region field. For providers that we officially support and partner with, such as Wasabi and Storadera, we were able to specify the necessary fields internally, but it wasn't an available configuration option for any custom S3-compatible provider. This is now available in Comet 22.6.7.
For example, configuring a custom S3-compatible Region field helps Comet connect to Scaleway Object Storage in their Paris, Amsterdam, or Warsaw regions with the latest V4 signing mode instead of requiring legacy V2 signing. We're happy to improve support for Scaleway as a well-established European cloud provider offering 6+3 data redundancy (6 data drives plus three parity drives).
Last month, we launched the Job Execution Delay feature, to pseudo-randomly delay a backup job schedule by a different amount each time. If you apply this random job execution delay across your entire customer base, it can spread out the load on your storage infrastructure, reducing the peak spike of CPU usage that happens when many jobs all start simultaneously.
This month in Comet we've expanded our support for this feature. In Comet Server 22.6.3 you are able to enforce this setting at the Policy level and also at the whole-server level, where it will override any user or policy settings.
In the Comet Server web interface, when looking at a user's Protected Item or Storage Vault, a "Test Connection" button is available that uses Comet's code to reach out to the target and ensure the device is able to reach it successfully. Because Protected Items are private for each device in a user account, it's clear that we should send this live-connected signal to the correct device, but for a Storage Vault, any device in the account could potentially respond with this information for us. Up until now, Comet Server has picked a random device in the account for the connection.
For Storage Vaults, the situation can be a little different. In the case of shared Storage Vaults in the cloud, it's likely that any device can reach them. However, there are various situations where only some devices in an account might be able to access a Storage Vault. For example, a Local Path vault for an external harddrive; or troubleshooting if one specific device is unable to reach the target network. To help in these situations, the "Test Connection" button now shows a dropdown if multiple device connections could be used for the test.
We also fixed a security issue related to the Test Connections button in the web interface in Comet 22.5.2 and 22.6.4. If you are running an older version of Comet Server, please upgrade at your earliest convenience, or avoid using the web interface button.
For the programmers in the audience - the AdminDispatcherListActive API that underpins the live-connection selection here was also extended to support choosing the target username. This change is available now also in the latest updates to our PHP and Ruby SDKs on GitHub - and watch this space for more programming language SDKs coming very soon.
This month we've upgraded the main compression library used by Comet Backup - the industry-leading Zstandard - to its latest 1.5.2 release. This brings with it a major improvement in compression performance. The practical impact will be limited - backup jobs are almost always bottlenecked by the speed of reading files from the local disk, or by the network speed of uploading them to the Storage Vault - but even in that case, a more efficient compression system should result in lowered CPU usage during backup jobs.
There is a second compression-related story to discuss this month - I'd like to thank everyone who reported a recent issue with the RPM installer for Comet Server. In last month's "What's New" report, we described the new option for pre-built clients. Bundling these pre-built clients with Comet Server resulted in a large size increase for the Comet Server installer. To compensate for this, we adjusted the compression settings used by the Comet Server installer to use a larger window size, so that the pre-built clients would compress effectively with the piecemeal client components that are used with custom branding. This was highly effective, and the pre-built client feature ultimately had a negligible effect on Comet Server install sizes.
However, this compression change caused issues with some RPM-based Linux distros. After some research and testing, we were not able to resolve the issue while still maintaining the optimized file size of the RPM installers - so apologies to RPM users, the Comet Server installer for 22.6 "Voyager" has jumped from ~150MB to ~250MB. This is still a relatively small file size for the great functionality packed within, so we're sure you'll be happy to have the RPM installer functioning correctly again.
