What is the recommended backup strategy for an organization / Employee Network? It looks like the only way to backup is to export the app items to Excel, one app at a time, and then you lose the conversation (comments).
Is there a way to use the API to loop through all apps in a company and export the data on a nightly basis? Has anyone written sharable code for this, or what do you suggest for an automated backup solution?
We Love Podio, thanks!!
I totally agree with Darren. I guess I just don't get it, Gustav. I can't understand how you guys don't think this is a priority. It also blows my mind that Chat gets launched but this is ignored...
Maybe you should re-read Steven Revere's post from Feb 28th, 2013, above to understand how important this sort of issue is.
In case it helps!!
I was looking around for a way to have a backup strtegy and found this. I haven't tried it but apparently not only works but is also very easy.
Count me in for a good backup and export strategy. A brilliant online tool like PODIO isn't fully grown-up without.
Maybe a two steps strategy could be followed:
Make an export function which includes all the belonging content for (a) workspace(s). I know a very well known projectmanagement tool which has an excellent feature to export your project to html(as a zip, including all data and files). Unzip local and the whole workspace is duplicated and functional including files and comments. This is ideal for a backup of your workspace and/or ending the project and hand over the data to the client. Also when for some reason Podio can't be reached we have at least our local html for critical purposes.
In the meantime work on the super backup strategy including import app data. We all understand this is far more difficult to establish.
This is just my two cents.
Make that 4 cents Ron, because I'm throwing in my 2 as well. Although I already did that above, so I don't know if it's too late. Thanks for the shout out by the way Jason.
Another 2 cents -
Chat makes Podio LESS useful as it makes users LESS productive. Chat sucks up time. It throws in your face conversations that would normally have been set aside for when the time is right to deal with them. It's not like I didn't have a million other ways to communicate immediately with my team through text message, phone, skype and dozens of other programs.
Podio was better because it was different. Before people had to put THOUGHT into their Podio messages, and I could check in on them when I felt like it. That made me more productive. You've now managed to add something that I could already do a dozen other ways. Now they're all chatting with me and I have to LOGOUT of Podio so people don't expect immediate responses and distract me from getting my work done.
Where is the thread with dozens of people requesting Chat in Podio? Doesn't exist, does it?
Next request: how do I turn Chat OFF in Podio, like I've already done on my Facebook? And can I do it for my entire organization somehow?
Again, it's 'cause I love Podio so much that I'm so hard on you guys. Please remember that when I go on my rants. :-)
The thread for chat is here: https://help.podio.com/entries/21703423-Chat-in-Podio
Please keep this discussion related to back-up strategy :)
Chat conversations is just like Podio messages, you can't turn it off. Internally in Podio we used Skype to chat, it makes it a whole lot more efficient that we don't have to use another tool but can stay in Podio.
//Sara - Podio
I thought I wanted a backup feature but if Podio has the right support in place to backup their system and recover in the event of a disaster - I'm happy with that. What I need to know is what is Podio's back-up and DR system like? I'm assuming it is really good, but I'd like to know for sure.
What I really NEED is the ability to DUPLICATE a Workspace in my Podio Organisation.
I do a lot of co-creation with customers on Podio (very very happy user) but I have no way to give them their "stuff" when we finish building their software together. I'd like to be able to:
A) Duplicate their entire workspace.
B) Advise them to take ownership of it by DELETING me as a member of the Workspace. They can now keep using Podio with their team confidentially. If they want to get the info out of Podio into an alternative system - that is entirely an issue for them to manage.
C) Once I know they have their copy of the Workspace I delete them from the original workspace (so they don't continue to have access to the workspace after we finish working together - just to avoid them accidentally deleting stuff I might need later). I can keep this workspace as a copy of our work for future reference.
Thanks for listening!
meli I am also curious as to how Podio handle their backups and your other suggestions are also interesting but this thread is about the backup feature.
The reason a lot of us are requesting it is not due to our lack of trust in the Podio teams ability to perform backups, but rather so we will not lose years of work worth millions of dollars if Podio suffers a disaster or runs out of business in a few years. There are endless risks to not being able to handle your backups inhouse.
The saying "trust but verify" feels quite right here, we are only asking to have our destinies in our own hands.
Archive, Backup and Disaster Recovery are different issues.
My needs are, by priority:
ARCHIVE: to export each workspace on demand, in order to migrate all my data outside Podio and to keep my own snapshots of a project / workspace. One strong driver for this is that I cannot risk to be forever bound to an external provider platform. This is part of an exit strategy any business must have when chooses to adopt a support platform.
BACKUP: to restore a snapshot of the environment, or a snapshot of an "app" (table) or a version of a single record, in case of operating errors. I think an history of max 4 weeks should be convenient for most context. The conversations attached to each record is not so relevant to me, but I understand that for somebody it could be relevant to keep also the decision-making process or task solution history as an integral part of the record information.
DISASTER RECOVERY: I am confident that the disaster recovery system of amazon or whatever provider podio uses as storage is much reliable than mine, so the only request to Podio is to expose with transparency the policies and service levels Podio has signed with its providers and what SLA podio guarantees to its customers. The same SLA I will declare to my - very demanding on this topic - customers.
Again, thanks for sharing your input guys.
@Carl Johan, I have attached our security whitepaper. We back up your data hourly and Podio is hosted by Citrix Datacenter in Frankfurt and a part of Citrix (not likely that Citrix runs out of business). I hope this can help you.
//Sara - Podio
I think a multi point approach with a CDN (content data network) driven by sharefile around the globe could be a real advantage.
Especially building in some of the Sharefile features of multiple storage pools. Being able to specify where a Workspace is located in a sharefile storage pool would be AWESOME. Even splitting the data and docs into various storage pools would be SO POWERFUL in terms of distribution strategy for Podio. More integration with Sharefile would allow uploading to podio to be a major drawcard for then editing and document control.
With Citrix buying Podio the possibilities of integrating these products is pretty compelling...
As indicated before by other users (more than once) a first step would be a complete back-up or export version for all data without the need to import it again into Podio. This would make it a lot easier for Podio to develop. So it's possible, in case of an emergency, to migrate all data outside Podio. This as part of an exit strategy. Just like you can do with SalesForce ... I'm sure it would give us users a more comfortable feeling if this would be possible! Specifically for those who are trying to convince their clients to use Podio.
It's not really even an exit strategy I am worried about - I will keep using Podio forever - it is a way to back-up and pass over files to clients when the project is completed. They may not want to keep using podio (and I don't want an expired project (workspace) clogging my podio forever) and having to individually download each attached file for a year long project is just not worth thinking about! A way to hand over several excel spreadsheets (from the deluverables app or whatever) and a folder of files would be great.
I have been looking into Podio - really nice, easy and simple, just what I was looking for for a company who are keen on Sharepoint - but that is really overkill and not very friendly to work with.
Without a solid backup solution (made and maintained by Podio), Podio dosent even get on the table, and that is a shame - because I really love the concept.
To back-up your data we currently allow you to export all your app data into excel or use the API:
Also, all data are backed up nightly and copied to another off-site location. All your data are programmatically accessible via the Podio API: https://developers.podio.com/. If you can not use the API in house, we can advice on finding a developer to do it for you. Let us know here if you need additional assistance.
//Sara - Podio
I have just started testing Podio for my company. It comes as a considerable surprise to me that there is no ability to export an entire account including files, comments and tasks. This is absolutely necessary if a company like mine is to use Podio as a place for it's mission critical data. For example, if Podio doesn't take off and Citrix put a bullet in it, we need access to this data otherwise it is lost.
Your competitors allow this, eg
I want to use Podio because it has the best features, however it looks like I'll be choosing Basecamp because it gives me a local copy of my data.
I presume the reason you do not give access to this data is because you don't want us taking it over to a competitor's service. In my view this is a big mistake. You are presenting a massive barrier preventing new customers from signing up. Security of data is the most important feature of all.
Please escalate this issue to your CEO. It is a major strategic issue for the company. Thanks.
Our CTO, Phil Chambers, has been commenting on this thread on several occasions and is following the thread. Our CEO Tommy Ahlers is fully aware already :) We discuss requested features on a regular basis internally and understand the need for a back-up strategy. Thanks for adding your feedback.
//Sara - Podio
#1 need for my .org is to be able to archive all Project data (comments and all) prior to deleting that Project.
I'd then place this Podio archive into our local project folder for future reference. (For example - Q: Why were we late on delivery? A: Because you were two weeks late on providing approval.)
+1 for me and my team on needing short term and long term backup options.
+1 too for Stephen Revere's earlier comments regarding Chat. ("You've now managed to add something that I could already do a dozen other ways. Where is the thread with dozens of people requesting Chat in Podio? Doesn't exist, does it?)
any news on this. We do need a backup strategy. I know, I have read Phil's statement. Is there any schedule? Are you currently working on it? In my opinion, the backup strategy / feature is more important than any other fancy feature you are working on right now. Podio is fine how it is right now (of course there is alway something to improve), but this substantial part is missing.
So please let us know how fare your are, what your roadmap is and an idea when we can expect this functionality.
hi podio team
Me again- I'm sorry but you can keep replying saying phil is monitoring this tread but yet he clearly doesn't see it appropriate some how to participate and address these ever increasing requests of peoples needs for Podio.
I think every person that's contributed their valuable time and recommendations to this tread deserves at the very least to feel listened to an appreciated regardless of their point of view and the issues important for them.
I think there has been some very valuable input, ideas, recommendations, suggestions and even solutions from podio users but sadly no progress on a backup solution or even a roadmap in response from the Podio Team.
I understand the difficulties in adding such a vital feature to an application post release but this isn't about the task in hand that the Podio dev team have it's pure and simple an issue of communication, understanding and engagement with its users and recognising the need. i still get the impression the Podio team is resistant to the need for end user managed backup maybe because they just don't get it...
I'm sorry to say i'm highly bored of this now and will be seeking an alternative to Podio one which gives users better control & management over their data!
It's such a shame, a product with such potential has failed to see the obvious missing element
I believe that Podio's strongest feature — the interrelation of users, apps, workspaces and organizations is the very thing that will prohibit Podio from getting a native backup solution.
Having said that, I've focused my attention on a workaround using an internal process + using Podio's existing features.
Here's my approach:
• Create project folders on a shared server (ex: Box.com which is great for enterprise use and integrates natively with Podio) and store all project assets in that folder
• Create a Project in Podio which matches the name of the project folder on the shared server.
• Use the shared server's project folder as the repository for all development, support, and delivery files — connecting them within Podio as necessary.
• Manage our project (in our case, Project, Deliverables, Tasks, Teams, Workgroups, Users) using Podio.
• As Deliverables and Projects are completed, I print the Deliverable or Project to PDF and save the PDF to the project folder on our shared server. In this way I can have a record of all the comments, series of events, specs, etc. that have transpired over the course of the project for future reference. And because, as an order of our internal procedure, we have placed all files associated with that project in the shared server's project folder first. Therefore we have, by default, all those files already there and do not need to back them up FROM Podio.
• Then we simply archive the project folder from the shared server — files and records in one place for future use. Plus this conforms to our company's archive policy.
Bellyaching to Podio probably won't be effective. So if you think Podio's pros outweigh it missing a native backup feature, maybe you could also figure out your own workaround.
Please sign in to leave a comment.