Forum Post: A question about uploading documents directly into Rollbase and their subsequent...

Status
Not open for further replies.
R

RichardWalsh

Guest
Hello I have been pointed to Rollbase documentation where it states there there is a limit to the number of documents that are stored in a System Backup (currently equivalent to about 10MB) due to 'disk space limitations'. However there is no limit to the amount of relational data that is backed up. The advice seems to be to ensure you have these documents backed up elsewhere.... e.g. an Amazon Cloud Storage account. My feeling is that in practice this might be a nightmare. As an example, say I have 500 documents uploaded into my Rollbase database and each is 1MB in size. I presume that, as a fully managed service, Progress is taking care of the backup on a daily basis (i.e. relational data and ALL documents). If there is a problem in the Rollbase infrastructure then Progress should be able to recover all data. What happens however if on a particular day a Rollbase user accidentally deletes important data requiring a restore of the previous day's backup by Rollbase Support. Is it true that all the relational data is restored but just 10MB worth of documents - equivalent to 10 documents of my 500 in the above example ? If so that would leave me with 490 relational records without attached documents. Is the suggestion that we identify the 490 documents from Cloud Storage (or indeed local storage) and upload them all again , after identifying all the relational records from where they were missing. If my understanding is correct (and I hope it isn't) it all sounds very unmanageable (and worrying). I can perfectly understand the need to restrict the size of the System Backup Zip file but surely the uploaded documents could be made available by FTP access or similar. This would allow each Rollbase account to take separate Document backup in bulk. This would be restored in bulk (in my example 500mb) at the same time as the System Backup was restored and everything would then be OK. Has anyone else faced and solved this issue or is it really not an issue? The only thing I can think of is to store all documents in Cloud Storage only (i.e. NOT in Rollbase) and provide URL links from Rollbase.records to these documents. I'd be grateful for any suggestions or clarifications. Thanks. Richard

Continue reading...
 
Status
Not open for further replies.
Top