How are you naming your backup repositories (or extents in SOBR) today?
I have at least for my primary and copy Backup repositories the prefix PRI_REPO_ and COPY_REPO in the names. And if there are “special” data in this repo for example RMAN oder something like this. I don’t like to search
Vendor Name + Conceptual name + Number in production.
Vendor Name + Conceptual name + Number in production.
Could you share an example, even if fictional?
Vendor Name + Conceptual name + Number in production.
Could you share an example, even if fictional?
Gondor_Wherewaswhenthewestfoldfell_2758
It depends, I have an own repo for the config in one environment. And this is the one where the naming schema I have described does not exist…
Mhh… CONF_REPO_ would be my spontaneous and uncreative idea for this….
Normally we use something like “HOSTNAME_PATH/DRIVELETTER(_STORAGE)(_TYPE)”. For example:
- MyServer_E
- MyServer2_G_Config
- MyServer2_G_SANLUN001
This mainly goes for Windows repos; Linux or other Storage Devices would be similar.
Normally we use something like “HOSTNAME_PATH/DRIVELETTER(_STORAGE)(_TYPE)”. For example:
- MyServer_E
- MyServer2_G_Config
- MyServer2_G_SANLUN001
This mainly goes for Windows repos; Linux or other Storage Devices would be similar.
normally I name the folder like the repository name
server name_ExtentNumber
svg1sbcka001_01
svg= project name
1 = number of Datacenter
s = host type = server
bck= role/type
a= network area
001= number of server
specific backup repo for configuration backup and RMAN => server name
In a large deploy, usually follow the
servername_typeofshare_typeofdisk_number
examples:
SYNOLOGY_NFS_HDD_01
SYNOLOGY_NFS_SSD_01
WS2016FS_SMB_HDD_01
in a small deploy, names are more easy to handle, so I usually use these examples
repo_backup_HDD_01
repo_backup_NAS_01
repo_replica_SSD_01
repo_replica_HDD_01
hopefully helps!
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.