New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Clear caché still works, it is just another command. I do not remember exactly why. That is not related to my issue, mine is related to "ownership", meaning that backups will be "owned" by a folder, if you move it to another folder it will just not work.
I'm in similar situation on location 2 as I manage to broke my Jetbackup that way to move accounts manually to the folder
I found the command
jetcli backup -vfR reindex
But after every account it say
DONE - 0 snapshots found for every account in location 2
paths are correct and follow the structure after the strangely named folder as in my location 1
where backups are
DONE - 15 snapshots found
Happened to me in one of the upgrades as well, submit a ticket..
The backup structure and db isnt the same. Open a ticket, they will fix it for you.
Had to get them to do this for over 8TB data...
Hi,
Just bumping in to clarify a few things
JetBackup 4 introduced a new core in which we had to change the concept of how we deal with our files in the backup destinations.
Basically the main idea is working with meta index files, rather then "running through" the entire backup destination.
This change allowed us to dramatically improve the speed of the backup indexing as well as improve the reliability of the backups.
So whats this have to do with reliability ?
We've seen so many cases where users are using the same backup folder for multiple jobs... and even worse, the same backup folder for multiple servers.
Let's focus on the "multiple jobs to the same folder":
For example -
Daily job runs every day, saves 14 retentions
Monthly job runs 1st of the month and saves 2 retentions.
Daliy job will be executed every day, retentions will slowly gather up to 14. So far so good.
Once the 1st of the month reaches, monthly jobs runs.
How many retentions do we save for the monthly job ? 3
How many do we currently have inside the backup destination ? 14 (reminder - we are sharing the same folder)
How many snaps will the monthly job delete ? 11
Next day, daily job will keep pushing incremental backups, and the reneton rate will grow up +1, at this point it will be 4 and so on.
The new "Multi scheduling" feature we added inside JetBackup 4 eliminates this headache, and everything is calculated in the background. Even better, the monthly job doesn't even have to be actually executed, we simply "flag" a snap shot as "monthly" once he reaches a proper age.
When using ssh / local backup destinations, It is very convenient that backups are saved in the "cpmove" structure and even better that we can manually reach these files, not related to JetBackup.
We do understand the need for the "clear cache" function when doing maintenance / moving accounts. We have an open internal case about it, so it should be taken care of
Thanks,
Clark
Thanks, and please, something like "Import backup from other JetBackup destination" or something like that
I didn't really have a whole lot of problems initially with R1Soft, aside from it being slow. Then I ran into an issue that every time KernelCare would update the kernel, the server would have to be rebooted every single time, or R1Soft would fail. Kinda defeats the purpose. R1Soft finally admitted it was a bug, but working as designed, and they refused to fix the issue. All that along with shitty support and the massive price increase? Yeah...R1Soft can suck it.
Went to Clusterlogics and never looked back. Was incredibly easy to set up and it's reasonably fast as well. I had a couple questions and their support team was excellent and very responsive.