is there a way to restore the backup from the backpack backup manager?
I have check the https://github.com/Laravel-Backpack/BackupManager but i can not see an option to perform this action.
That package is just an interface for creating backups using spatie/laravel-backup. It provides no interface for restoring backups - you'll have to do that manually, I'm afraid.
Related
I'm currently working on a project that we are using Prisma 2 and postgreSQL as database support. From my understanding, whenever I made changes to the schema.prisma file and I want to migrate the changes to the database, I run prisma migrate dev locally. Then I will push the auto created migration files under migration folder to Github, and then our repo will run prisma migrate deploy to the staging or production server.
So, my concern is, each time I run prisma migrate dev, a new migration file will be created in migrations folder. So, there will be a lot of migration files under the migration folder with the development of the project. Is that what supposed to happen? Or is there a better way?
Thank you for your help. I'm pretty new to Prisma 2 and still trying to find the correct way to work with it. BTW I think Prisma 1 was easier to use :)
I’d recommend using prisma db push while developing locally and generating the migration with prisma migrate dev only when you think the schema changes are good to go. More at https://www.prisma.io/docs/guides/database/prototyping-schema-db-push
So, there will be a lot of migration files under the migration folder
with the development of the project. Is that what supposed to happen?
Yes, this is exactly what's supposed to happen. The migration file contains the history of all changess to your Prisma schema (and underlying database tables/configuration), so they all need to be retained.
I'm not sure if you could go around this somehow, but it's certainly not the recommended way to be using migrate.
You can find a list of best practices regarding migration in the Prisma migrate article in the docs.
It's been a very long time since the question is asked, but i want to warn about something:
As you may notice a table named _prisma_migrations is created by prisma automaticly and every time you add a new migration you are able to see the new migration's data over there. So any manual change made in migrations folder can cause problems since it breaks the relations between folder names and _prisma_migrations table.
Also docs for "squashing migrations": https://www.prisma.io/docs/guides/database/developing-with-prisma-migrate/squashing-migrations
I am asking for the actions needed to be taken to clone Dynamics CRM on-premise from the production environment to test environment.
Is it just
open production SQL server,
Backup PROD_MSCRM Database
move the file to the test SQL server.
restore the backup file to Test_MSCRM DB
Can someone help me if this correct and if there any thing else I should do?
Yes, after restore you need to create a new Dynamics CRM instance. You do this using the management tooling. Create the organization and choose to import an existing database.
I'm trying to create a copy of a existing database in the AWS (RDS) Console with a snapshot of the database however the button for migrating the snapshot is disabled, what might be the reason for that?
Based on the comments, the solution to the issue was to use Restore option, instead of Migrate.
You want to choose the “Copy” option not the migrate.
I want to create one click deployment on azure pipelines to move Postgres Sql changes from dev to QA environment,similar to what we implement using SQL Server Database project where a Powershell script deploy the changes to the remote server.
I have tried pg_dump and psql commands which will create dump file and restore it on the remote server. It does not perform diffing ie(comparing database changes on source and destination , and only replicating the missing changes)
You've stumbled upon one of the features lacking in the Postgres ecosystem. One of the more elegant ways to solve migrations using Postgres' own tooling is to package up your migrations as a Postgres Extension. This requires you to generate the deployment scripts yourself, but it is a neat way of applying and packaging up the deployments.
There are a number of commercial tools that will assist in this process, such as Datical, Liquibase, and Flyway. Note, some of these still require you to generate the change statements yourself, some attempt to create them for you.
Generating change statements is a whole different animal and I recommend you look at schema diffing tools for Postgres to find what best suites your needs.
Using v. 2.2.12 Enterprise.
I'm testing backup functionality with Studio Backup Management as explained in https://www.youtube.com/watch?v=hU2UkWiDjNM.
Backup is working, I've got backups in specified folder, but not events at all. So I cannot restore.
What's wrong?