Tag Info

New answers tagged

0

If your big tables are innodb, you can use --single-transaction to not lock the table. Other possibility is Percona XtraBackup Or pt-archiver (again Percona)


2

This is explained here, it boils down to that you have to have a full backup of the databases as well as a backup of the read-only filegroups: A piecemeal restore sequence restores and recovers a database in stages at the filegroup level, beginning with the primary and all read/write, secondary filegroups. In this example, a database named adb, ...


3

One of the considerations implementing multiple databases is different RTP/RPO requirements. It seems this is the case in your situation because the RPO is different. Consider creating a separate databases for the ETL tables and historical data. Backup the historical data database as needed to meet your RPO. The ETL database can be backed up ...


1

I don't understand why you're asking this question. If you're buying in a service, then backups should be part of the SLA and not your responsibility. If it's not part of the service, then why are you using SaaS? On the other hand, if you need to be backing up something, why are you backing up every hour? Technically, if your application is running on a ...


1

First of all grab Ola Hallengren's scripts to do the backups (http://ola.hallengren.com) and drop the maintainance plans. Ola's scripts have much better retention settings and will allow you to set a mark in hours how long to store the backups and know how to take the backups of the secondaries. And for your questions: Set up a small script in SQL Server ...


1

performance_schema: Not necessary. It may contain performance metrics that are only good for the time you were using the instrumentation. It would serve no purpose to load collected metrics from the past into another MySQL instance or into the same MySQL instance at a much later time. mysql : BE VERY CAREFUL HERE !!! If you backup mysql, you can only reload ...


0

As sporri said Rman is really not that hard once you get your head around it but try with this Link


3

The DMV's themselves are the same between same builds of SQLServer and give you a snapshot or a cumulative counter of the status of your server at any given time. You cannot restore the database to a new server with the metadata from the old one. You can make snapshots of some of the performance metrics into a table but you cant restore the state of the ...


0

1) select your database and press right-click , then choose tasks then backup. 2) Then change the backup type to transaction log. 3)Then press Add and click on the box (...)enter image description here 4) write the database name.bak in the (File name) and don't forget to write this extension (.bak) 5)Finally write ok 3 times it should work fine


2

For Backup component, click Database. Either accept the default backup set name suggested in the Name text box, or enter a different name for the backup set. Optionally, in the Description text box, enter a description of the backup set. Choose the type of backup destination by clicking Disk, Tape or URL. To select the paths of up to 64 disk or tape drives ...


1

Shut down the database instance. Copy all files to backup location. Start up the database instance.


0

When dumping a schema with the mentioned command, as postgres user: pg_dump -f file.sql -F plain --inserts -n schemaname database it produces a file whose basic structure looks like: -- various SET commands CREATE SCHEMA schemaname; ALTER SCHEMA schemaname OWNER TO ownername; SET search_path = schemaname, pg_catalog; CREATE TABLE tablename(...) ... ...


1

Don't specify two conflicting FORMATs (you have one in the ALLOCATE CHANNEL command and one in the BACKUP command). If and when you need different FORMATs (e.g. one for database datafile backups, one for archivelog backups and one for controlfile backups) specify them explicitly with the BACKUP command. Eg: > rman target mydatabase shutdown; ...


2

I believe you cannot take a native backup of the databases if they are in Standby/Read Only mode. So backing up the secondary database would be not be a good go. Also, if LS DB is in "Read only mode" you can run DBCC CHECKDB , it will complete but it would not get into the boot page and hence not the check you expected it to be. Moreover even if it ...


3

On the old laptop run pg_dump to dump the data: pg_dump --username=your_pg_user_name --dbname=gxpgran --format=c --file=gxpgran.pgdump where your_pg_user_name is the name of the Postgres user you use to access your database. After installing Postgres on the new laptop and necessary Postgres user ("your_pg_user_name"), run pg_restore pg_restore ...


3

Is there any way to restore only the [PRIMARY] filegroup? That is what you have already done. The other filegroups exist only in metadata at this stage. Piecemeal restore allows you to restore filegroups in stages, or mark them defunct if they are no longer needed. There is no way to delete them from the system metadata though. After the restore ...


1

If you want to be able to view the exact backup history for longer time than those four weeks that you keep the backup files on disk, make sure that you set the cleanup task not to delete the backup history from the msdb database, you can then run the backup report from SSMS (right click database, select reports, standard reports, backup and restore events) ...


2

In my opinion it is not related to mklink or Windows issues. Per pg_basebackup docs, the main data directory will be placed in the target directory, but all other tablespaces will be placed in the same absolute path as they have on the server. -F format --format=format Selects the format for the output. format can be one of the following: p ...



Top 50 recent answers are included