Relax `backup_name` naming rules

[sangheee]

Hi, I would like to ask about the current restriction on backup_name when creating a backup.

When creating a backup, the backup_name allowing only letters, numbers, and underscores (_)

Currently, backup_name appears to follow the same naming restrictions as Milvus naming rules(https://milvus.io/docs/limitations.md#Naming-rules), which only allow letters, numbers, and underscores (_).

milvus-backup/core/backup/func.go

Lines 35 to 37 in 4b60c9d

	if validate.HasSpecialChar(name) {
	return errors.New("backup name should only contain numbers, letters and underscores")
	}

However, in my use case, I want to generate a backup_name by combining milvus database name, collection name, and timestamp.

For example:

${db_name}-${collection_name}-${timestamp}

Allowing characters like the hyphen (-) would make it much easier to create a readable and structured backup_name.
But since backup_name is limited to only letters, numbers, and underscores (_), using such delimiters is currently not possible.

So I’d like to know, is this strict rule intentionally aligned with Milvus resource naming conventions?

Since backup_name eventually represents a storage path, would it be acceptable to allow a broader character set?

Would the project consider relaxing this constraint?

If this direction makes sense, I’d be happy to help contribute a PR to support it.
Thanks for your great work on this project!

[sangheee]

I also tried to pass a deeper directory as the backup_root_path in the create backup request so that I could derive the milvus db and collection names from the directory depth.
But since the /list operation does not recursively traverse the configured rootPath, any backup created under a root path with depth greater than 1 does not appear in the list.

[wyqzos]

Hi @sangheee , thanks for the suggestion! I'm Valerie from the Zilliz Product team. Along with @huanghaoyuanhhy, we are aligned on this—allowing hyphens in backup names is a solid improvement for structuring storage paths.
The updated naming rule will be: 'Backup name can contain only letters, numbers, underscores("_"), and hyphens("-"), and cannot start with a number or a hyphen'. Please feel free to submit a PR, and @huanghaoyuanhhy will take point on the technical review. Looking forward to your contribution!

[huanghaoyuanhhy]

Hi @sangheee

Regarding multi-level directories: recursive traversal adds notable complexity and edge cases. The current design assumes backups are created directly under a fixed root directory. I’m also not entirely clear on the practical need for placing backups in deeper hierarchies.

[sangheee]

Thanks for the thoughtful feedback.

I agree with assuming a fixed rootdir for backups as you mentioned.
I would be happy to submit a PR regarding the changes to the backup name shortly.

Thank you again for taking the time to review this!