Tag Info

Hot answers tagged

4

You can have sysadmins doing COPY_ONLY backups and DBA's doing regular FULL, DIFF and/or Transaction log backups. The key is COPY_ONLY backups for allowing ad-hoc backups. But they cannot be used for point in time recovery. Note that taking a random Transactional log backup (without using COPY_ONLY) will break the log chain and you wont be able to do a ...


3

Yes, it is possible, but it requires some agreement between both parties. If the "sysadmin" (it does not need to be a sysadmin by the way) wants his own backups, does he want all the transaction logs and differentials in addition to a full backup? If the "sysadmin" only needs full backups, he can do his own backups WITH COPY_ONLY and use them without ...


3

Maybe those files are not cataloged by RMAN? I would CATALOG them and then DELETE OBSOLETE once again.


3

Whenever I make a change to a table, does it get written to both the database file AND the transaction log file? It is written to both, but it is written differently to each. The changes are made to the data pages in memory and are eventually flushed to disk via the checkpoint process. the changes are sent to a log buffer and hardened to disk at some ...


2

No you cannot have two sets of backups otherwise you mess up the backup chain. Think of this occuring: Day one 1. Person A does a full backup Day two 2. Person B does a full backup 3. Then an hour later Person A does a diff backup That diff backup that Person A does will be based off the Full backup that Person B just did, not the Full backup that Person ...


2

Converting my comment to answer (read the comments in the script) : if you are using the same backup file name (ICT.bak) every time you backup, its better to use INIT. This way the previous file gets overwritten. USE master -- here no need to use the name of the database that you are backing up. Other RDBMS like SybaseASE will thorw an error saying that ...


2

We had the same issue today. It turned out to be a permissions issue, as illustrated in some of the other answers. The difference is that the account we needed to add was NT SERVICE\MSSQLSERVER. I identified the account by comparing the permissions of the default SQL Backup folder permissions to the folder containing the backup file. Adding the service ...


1

The wal files are archived when they are no longer needed in the pg_xlog directory (usually when there are 16 segments and another one is needed - the one that is rolled over and reused is first archived). You can force the system to archive some files to verify manually if you want - to do this run the following: select ...


1

What you need is partial backups. innodb_file_per_table=ON is a prerequisite to make it work. In your case procedure would be like following: Take a partial backup from the production server innobackupex --databases="mydatabase" /path/to/backup On the destination server prepare the backup copy for export: innobackupex --apply-log --export ...


1

SQL Server supports piecemeal restores. From that link: Piecemeal restore works with all recovery models, but is more flexible for the full and bulk-logged models than for the simple model. So you should be OK with the FULL recovery model. I'd suggest you partition your tables. The log tables especially should be amenable to partitioning by write ...



Only top voted, non community-wiki answers of a minimum length are eligible