![]() ![]() It may be based on your description above. You may want to go through the backup wizard using the legacy format and review the options to see which is best for your particular need. But for some customers, that format is preferred based on their needs. You keep backups using two options in the new backup format: Use the Keep Backups For option to determine how long you keep backups on disk (say 90 days) and use the GFS options to determine how many weekly, monthly, and / or annual backups you want to keep for short-term and longer-term retention.Īs I mentioned, the legacy backup format for files is version based and is incremental forever, but you lose many of the newer features. ![]() But if you're not using a cloud with synthetic backup support, we'll need to run a new full, which is not something you'll probably want to happen - hence my question at the top of this post. As long as you're on a supported cloud for synthetic full backups, we ll run a synthetic full and create a new backup set and then the incremental backups will continue for another month. Run the full backup once a month if that works for you. ↪Art Vandelay What cloud are you using for your backup target?Įvery incremental will contain all the new files / changes. Do I need to schedule them so they don't clash? (There was no warning given.) Will both plans run together, or will one be blocked from running until the other finishes? Since, the 1st backup plan, the recurring incremental, runs periodically every day that appears to be a scheduling conflict. (This is one of the thing that looks very different from online examples I've found.) So what is going to happen, is the backup plan going to do both, or does the full backup setting override the incremental? I'm looking at also adding periodic monthly full backups and unless I'm missing something it looks like that has to be done by scheduling a second backup plan.įirst point of confusion is that when scheduling it is necessary to check off "Recurring (incremental)", only then is it possible to select "Execute full backup (synthetic if possible)". So far I have recurring incremental backups running every day that started with an initial full backup and has built up a few weeks worth of incrementals now. There are a lot of confusing options, and part of the confusion is that examples found by searching online are apparently for earlier versions of Cloudberry and the options have changed, in some cases substantially. I'm new to Cloudberry backup and am configuring backup of a Windows server. The following command creates a backup plan and specifies just about every option available. cbb changePlanState -n "plan's name" -s on/off To enable or disable scheduling, execute the following command. cbb addRestorelan -a "My S3 account" -n "Documents" -f "/users/robert/Documents" -every day -recurrencePeriod 10 -worktime "00:00-23:59" The following command creates a restore plan that is scheduled to execute every 10 minutes. ![]() greater levels of forecast accuracy and enhanced daily pricing optimization for the SAii. cbb addRestorePlan -a "My S3 account" -n "Documents" -f "/users/robert/Documents" -every dayofmonth -day 1 -repeatEvery 1 -repeatFrom "" -at "02:00" CloudBerry Backup is a leading cross-platform cloud backup and. The following command creates a restore plan that is scheduled to execute on the first day of every month at 6 a.m. cbb addRestorePlan -a "My S3 account" -n "Documents" -f "/users/robert/Documents" -every week -weekday "mo, we, fr" -at "02:00" The following command creates a restore plan that is scheduled to execute every Monday, Wednesday, and Friday at 2 a.m. cbb addRestorePlan -a "My S3 account" -n "Documents" -f "/users/robert/Documents" -every day -at "21:00" The following command creates a restore plan that is scheduled to execute daily at 9 p.m. cbb addRestorePlan -a "S3" -n "Documents" -f "/users/robert/Documents" -at " 23:00" Specifies the start date for monthly restorationįor example, the following command creates a restore plan entitled Documents that restore data from Amazon S3 one time on Maat 23:00. Recurrence period for monthly restoration Specifies the week in which a monthly restoration should be executedįirst / Second / Third / Fourth / Penultimate / Last The following macros are available for subject: %COMPUTER_NAME%, %RESULT%, %PLAN_NAME% Specifies the subject for email notifications. Indicates if email notifications should be sent upon restore execution / failure User S3 Transfer Acceleration (Amazon only)Įxpedited, Standard, Bulk, Skip (don't restore from Glacier) The version that was the latest at the specified date will be restored. You can get the account names of your target storage by executing the following command. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |