Search results
Create the page "Backup" on this wiki! See also the search results found.
- existing volume drivers, backup drivers, or target drivers (e.g. API) If you meet any of the following: Contributing a new volume, backup, target driver. My3 KB (358 words) - 22:35, 30 October 2020
- user requests a backup, the volume is cloned and then the clone is uploaded to the backup backend, and both steps can take a long time. Walt's solution is48 KB (7,960 words) - 22:47, 4 May 2021
- CinderVictoriaPTGSummary (section Backup Driver issues)Shatadru Well, one issue anyway. The issue is the container parameter for the backup drivers. It's handled differently depending on what driver you're using:32 KB (5,340 words) - 02:56, 10 June 2020
- Stop nova-compute on all hypervisors Stop MySQL on DB slaves. Make a full backup of the DB Run DB migration scripts Execute this command on the DB: update4 KB (656 words) - 05:20, 6 June 2018
- User Guide backup-db.rst 33: $ trove list 54: $ trove backup-create INSTANCE_ID backup1 79: $ trove backup-list :92: $ trove backup-show BACKUP_ID :126:43 KB (2,795 words) - 10:32, 4 May 2017
- aggregate aggrégat availability zone zone de disponibilité backend backend backup sauvegarde bare metal bare metal cache cache client client cluster4 KB (497 words) - 23:25, 3 March 2016
- extend API: https://review.opendev.org/c/openstack/cinder-specs/+/864020 New backup state: (A new spec will be proposed, old discussion at https://review.opendev5 KB (726 words) - 10:37, 1 September 2023
- Message Brokers on-demand Support Broker management operations such as Backup of Configuration, Scale Up, Scale Down Data plane API Multi-tenancy at6 KB (897 words) - 04:42, 1 October 2015
- number (US/Canada): 1-855-244-8681 Having trouble dialing in? Try these backup numbers: Call-in toll-free number (US/Canada): 1-855-244-8681 Call-in4 KB (542 words) - 23:29, 17 February 2013
- #secure_backup_and_recovery Chapter 9 - Secure Backup and Recovery Ensure only authenticated users and backup clients have access to the backup server14 KB (443 words) - 18:37, 10 January 2014
- for a very, very large backup job each night. While “The Issue” (as we were now calling it) didn’t happen exactly when the backup happened, it was close25 KB (3,989 words) - 13:41, 14 November 2017
- Day-to-day operation and administration of the OpenStack cloud including backup, disaster recovery, managing the infrastructure and platform services offered5 KB (233 words) - 20:47, 23 December 2015
- Basic administration includes performance tweaking, high availability, backup, recovery, and repairing. For more information, see a standard MySQL administration2 KB (259 words) - 19:56, 18 August 2017
- "max_user_connections": "100", "myisam-recover": "BACKUP", "open_files_limit": "512", "pid_file": "/var/run/mysqld/mysqld19 KB (1,688 words) - 08:01, 14 May 2015
- will be possible. If I want to replace a standard controller (for example, backup_schedules) with one of my own design, this will pave the way for that capability5 KB (697 words) - 23:31, 17 February 2013
- server available. After the controller rebuilds, restore any backups taken (see ops-backup-recovery). Also, in practice, the nova-compute services on the3 KB (510 words) - 19:45, 18 August 2017
- CinderUssuriPTGSummary (section Backup Service Testing)from the Train mid-cycle. The backup tests fail intermittently with timeouts. The situation now is that the cinder backup tests have been removed from36 KB (5,851 words) - 19:04, 4 December 2019
- Length/Range Data format AdminActionsController _create_backup() name Required NV backup_type Required NV rotation Required16 KB (732 words) - 08:40, 24 April 2014
- Volume Backups [tab] Backup create (same as Volume->Create Backup) and delete Backup Overview on clicking link Backups pagination Restore Backup Images13 KB (1,897 words) - 13:10, 26 January 2016
- failed builds. Feb 20, 2:46 PM A commit that added a test for cinder backup caused some tests to fail. These tests are not supported and has been added8 KB (51 words) - 18:12, 18 February 2015
