Hot answers tagged

4

So Microsoft claims that "you cannot use a network shared folder as a backup target for a system state backup" That is (or was) a restriction on the original version of Windows Backup, that came on older OSes (Vista RTM and Server 2008 RTM - this may or may not have been addressed in service packs or updates to those OSes). Windows 7+/Server 2008 R2+ ...


4

You are right about backup files being hard links and it is safe to just delete the backup directory. Hard links are just pointers, so if a file have two hard links then the space occupied by this file will only be reclaimed by OS when both links are deleted.


3

The system state backup (when done on a Domain Controller) includes AD schema/data. See here for more details.


2

I think the problem with your -nv approach was that intermediate filesystems are not created when receiving with -n, and therefore it will fail every time, while it works without the no-op flag (but expanding the complete filesystems may take a long time). Unfortunately, most documentation/blogs online do not use this flag, therefore they never experience ...


2

According to the mailing list you will have to manually exclude it .. it holds your backup chains index files (table of contents of the backup repository). Caching them locally accelerates options like status and incremental backup and others. These operations need to know what is already backed up to work. If they are cached they do not ...


2

You will frequently find advice about backing up and restoring domain controllers that boils down to "don't backup your DC". This is unfortunately bad advice. You should be backing up all of your domain controllers, because you never know which one will be corrupt. The problem isn't so much the backing up of domain controllers, it's restoring them that is ...


2

No, you cannot "copy" a snapshot. Creating a snapshot on a VM simply adds another "virtual disk" file. The hypervisor stops writing to the original "disk" file and from the creation of the snapshot on, it writes to the new "disk" file. Reverting to a snapshot just deletes the added "disk" file. In your case, you have to do a new OVA export. A snapshot ...


2

You should be able to use the SEPDIR config parameter. It will create separate directories for each database, with an own file inside of it. From the Ubuntu manpage (but should work on CentOS just the same): SEPDIR=yes Separate backup directory and file for each DB? (yes or no) Alternatively, it's very simple to write up a bash script yourself that ...


2

At 100% CPU on the VM, the hypervisor is going to have a devil of a time writing those snapshots in. You can see all the snapshots by going to the datastore and looking for all snapshots: cd /vmfs/volumes/ then run ls -alR | grep -I *.*delta | less This will display all snapshots in each VM. You could go into the specific VM's directory to see just ...


2

Preface: Backups should always be offsite offline/read-only redundant. If you just use an external hard disk connected eg. via USB, you dramatically reduce the amount of protection your backup can offer against catastrophic damage like theft, fire, flooding etc. user and or software error leading to deleted data on connected drives, inlcuding your ...


1

The service provider will have more to do with uptime than the technology its running on. I'm gong to avoid recommending any one provider but generally speaking you get what you pay for. That $5 or $10/mo VPS is almost certainly running on oversold/allocated hardware. With a more expensive VPS the server will less likely be oversold and probably managed ...


1

Replacing the tapes was probably a bad idea. Back in the days where I was administrating LTO-4 drives it was entirely normal for brand new tapes to be covered in a tiny amount of debris left over from the manufacturing process. The dirt entering the drives through these new tapes may have been the final blow to your drives. I have seen that happen hundreds ...



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