Tag Info

New answers tagged

0

MIRROR TO is not supported with backup to URL: https://msdn.microsoft.com/en-us/library/dn435916.aspx#limitations Specifically under the "Support for Backup Arguments" section, you'll see "Mirror To" has a "-" for not supported.


0

You can use pgAdmin to perform pg_dump operation and choose what exactly should be in backup file(tables, schemas). Moreover you can choose backup settings such as backup file format. It's very easy to use, if database is big You just wait until process will finish. To start backup after connecting to PostgreSQL just right click on database and choose ...


3

Just run pg_dump. The documentation says: pg_dump is a utility for backing up a PostgreSQL database. It makes consistent backups even if the database is being used concurrently. pg_dump does not block other users accessing the database (readers or writers). In turn, the state of the database that you see on the slave is also consistent. If ...


0

For the purpose of not leaving this question open and in hopes that it helps someone in the future, I wanted to detail the steps I followed to solve my problem. In following the advice given about running a trace around the time the Recovery model is changed, I found that there was indeed a task that was shrinking the log. Summary Using SQL Server ...


0

If you want to recover by filetype, please note the following structure in MySql database file system: A MySQL table is the combination of three files: The FRM file is the table definition. The MYD file is where the actual data is stored. The MYI file is where the indexes created on the table are stored. Source: [1] ...


0

do a manual full backup and then it will run. Why is this? This is because any database you create with full recovery model is always in pseudo simple recovery mode until you take a full database backup and this is where a log backup chain can be establish successfully. You can easily check if a database is in pseudo simple recovery mode using DBCC ...


0

Below is the answer to my Service Request related to the same problem from the Oracle Support. "This is a known problem, MySQL Server 5.7 is not in GA yet and currently MEB is not supporting 5.7 versions. Developers are working on it".


5

This will be tough to do with the built-in schedule UI, unless you want to create 12 different schedules, but you can easily build this into your job step. Assuming it runs every night: IF DAY(GETDATE()) <= 8 OR DAY(GETDATE()) >= 28 BEGIN -- do backups END On other days (9th -> 27th), the job will still run, but everything inside the IF ...


2

If the full backup just grows by a few MB but your DIFF is 200MB then you're probably doing a lot of UPDATES which change the page, thus forcing the page to get copied to disk. However, full backup size won't change much as it copies all the pages anyways. This is ignoring the transaction log which in the comments you've already specified has very little ...


0

in order to release the space you first need to change the recovery model from full to simple, then you can release the space as you have mentioned.After it is finished you can revert from simple to full anyway this is a temporary fix.. the log will eventually grow again sooner or later..



Top 50 recent answers are included