[gpfsug-discuss] Snapshots for backups
Uwe Falke
UWEFALKE at de.ibm.com
Tue May 8 18:20:49 BST 2018
One thought:
file A is created and synched out.
it is changed bit later (say a few days).
You have the original version in one snapshot, and the modified in the
eternal fs (unless changed again).
At some day you will need to delete the snapshot with the initial version
since you can keep only a finite number. The initial version is gone then
forever.
Mit freundlichen Grüßen / Kind regards
Dr. Uwe Falke
IT Specialist
High Performance Computing Services / Integrated Technology Services /
Data Center Services
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland
Rathausstr. 7
09111 Chemnitz
Phone: +49 371 6978 2165
Mobile: +49 175 575 2877
E-Mail: uwefalke at de.ibm.com
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland Business & Technology Services GmbH / Geschäftsführung:
Thomas Wolter, Sven Schooß
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,
HRB 17122
From: "Fosburgh,Jonathan" <jfosburg at mdanderson.org>
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: 08/05/2018 15:44
Subject: [gpfsug-discuss] Snapshots for backups
Sent by: gpfsug-discuss-bounces at spectrumscale.org
We are looking at standing up some new filesystems and management would
like us to investigate alternative options to Scale+Protect. In
particular, they are interested in the following:
Replicate to a remote filesystem (I assume this is best done via AFM).
Take periodic (probably daily) snapshots at the remote site.
The thought here is that this gives us the ability to restore data more
quickly than we could with tape and also gives us a DR system in the event
of a failure at the primary site. Does anyone have experience with this
kind of setup? I know this is a solution that will require a fair amount
of scripting and some cron jobs, both of which will introduce a level of
human error. Are there any other gotchas we should be aware of?
The information contained in this e-mail message may be privileged,
confidential, and/or protected from disclosure. This e-mail message may
contain protected health information (PHI); dissemination of PHI should
comply with applicable federal and state laws. If you are not the intended
recipient, or an authorized representative of the intended recipient, any
further review, disclosure, use, dissemination, distribution, or copying
of this message or any attachment (or the information contained therein)
is strictly prohibited. If you think that you have received this e-mail
message in error, please notify the sender by return e-mail and delete all
references to it and its contents from your systems.
_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss
More information about the gpfsug-discuss
mailing list