Tag Info

Hot answers tagged

5

Use gpg (GnuPG). You'll be able to generate multiple keys and encrypt a file for decryption with any key from chosen list. Also GPG keys are not symmetric — your server only need public keys for encryption. Private keys, used for decryption, might be securely stored somewhere else. You can for example print one private key as QRcode for your director and ...


4

I would advise seeing whether your backup software can initiate and manage SMTape backups from your secondary site. Even if it can't, you can use it through the Netapp CLI to back up the entire volume. If your backup software supports it, you could use it to do full and incremental backups which would include all snapshots visible on the snapmirror ...


2

gsutil has an rsync command (introduced starting in version 4). You can use that to synchronize data from your bucket to a local disk, or to S3.


2

I have good experience backing up using duplicity. If you are able to do a snapshot and mount it read only, then it's a very good option to have consistent incremental backup. Usually the problem is with backing up databases (MongoDB, ElasticSearch, MySQL, you name it) is consistency. The same things apply to backing common files, but with databases, the ...


1

You can use vSphere replication to replicate from one host to another. It is not only for cross-vSphere migrations. Veeam's Backup suite can do the same thing with a lot less complexity. So while the built-in vSphere replication product works, recovering from it is a bit of a pain. Veeam is very inexpensive for two hosts, so it's probably worth the ...


1

Your image shows quite the contrary, actually. As you can see under the RES column, tar memory consumption is quite low. You RAM usage appear to increase simply because Linux is actively caching the data read by the tar command. This, in turn, causes memory pressure and dirty page writeback (basically, the system flush its write cache to accommodate for the ...


1

You can run this script, but it depends on what you're looking for in safety. -azv means archive, compress, verbose --delete-after means you're deleting anything that gets rsync'd off the source server after it reaches the destination server. 20 servers to 1 server... is doable-ish. Assume the following: 20 x 2.5GB = 50GB (total amount of data that has ...


1

If we have 10000 Win2012 servers (usually enterprise has), solution you proposed to buy more LTO tapes is costly. Instead I would suggest to keep ready ONE clone of a machine with latest OS+Antivirus patches. If there is a need to bring up a crashed machine, just we need to bring up OS from clone, deploy application, restore application data. OS data is ...


1

Just to add one thing. Try to use bscan and you can "read" the Volumes again ( the copied ones) and import them into the Catalog of the other location. Than you can restore them in the second site also ;) thus avoiding the dependency on the first director, in case anything goes wrong. Hope it helps. Cheers Filipe


1

The data size has reached the point where this process takes too much disk space and the file can't be uploaded to S3 in one shot. Upload them each as their own separate files. It's probably not the case that you're doing some kind of fancy de-duplication, and if you are changing that to be reference-based would be helpful. So far backups have been ...


1

The scheme that is implemented in at least one commercial DBMS that I know uses two keys, let's call them the master key and the database key. The master key is used to encrypt the database key. The database key, which could be of a higher grade, is used to encrypt and decrypt the backup images. The master key can be safely rotated, because it only ...


1

Yes, the blog post you linked (from 2011) appears to contain obsolete information. From the docs: If the bucket is versioning-enabled (or versioning is suspended), the Expiration action logically deletes the current version by adding a delete maker as the new current version. The NoncurrentVersionExpiration action permanently removes the noncurrent ...


1

Assuming that you can use a lifecycle policy to delete and/or archive the old versions in a way that works for you, there's no need to give your script delete permissions at all. This approach works great for me in conjunction with the AWS CLI tools. Here's what my bucket policy looks like: { "Version": "2012-10-17", "Id": "IDHERE", ...



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